DWM_E_REMOTING_NOT_SUPPORTED (0X80263002) — What It Means and How to Fix

You're sitting in a Remote Desktop session or maybe inside a Hyper-V virtual machine, working on a Windows 10 or 11 system, and suddenly your app window goes black or you see a crash dialog with 0X80263002 and the string DWM_E_REMOTING_NOT_SUPPORTED. It doesn't happen in every app — usually it's something that uses DirectX or hardware acceleration, like Photoshop, a game, or even File Explorer if you've got GPU-accelerated window effects turned on.

What's actually happening here is the Desktop Window Manager (DWM) is trying to composite that window into a remote-rendering pipeline (the one used by Remote Desktop or a VM's enhanced session). DWM has a special remoting path that's supposed to let it send frames efficiently over the network. But for some windows — often ones that rely on custom rendering or older DirectX APIs — DWM says "nope, I can't remote-render this" and bails out with this error. The window might fall back to software rendering or just stop responding.

The root cause is almost always one of three things: an outdated graphics driver that doesn't support the remoting features DWM expects, a missing or corrupt DWM shader cache, or a group policy that's blocking the remoting protocol for that specific app. The reason step 3 works so often is because clearing the DWM cache forces it to rebuild its rendering state from scratch, which resets any corrupted remoting tables.

Fix 1: Update or Roll Back Your Graphics Driver

This is the first thing to try because misbehaving drivers cause the majority of DWM remoting failures. Head to your GPU vendor's site — NVIDIA, AMD, or Intel — and grab the latest driver for your model and Windows version. Don't use Windows Update for this; it's usually behind. Install it fresh, reboot, and test.

If the error started after a recent driver update, roll back instead. Go to Device Manager, find your display adapter, open Properties, go to the Driver tab, and click Roll Back Driver. The reason this sometimes works is that newer drivers might drop support for legacy DWM remoting features that your specific app depends on.

Fix 2: Disable DWM Remoting for the Problematic App (Registry Hack)

If updating the driver doesn't help, you can tell DWM to skip the remoting path entirely for that specific window. This forces the app to render locally (on the remote machine) and then have its output sent as a bitmap over the RDP connection. It's a bit slower but stable.

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM. If the DWM key doesn't exist, right-click the Windows key, choose New > Key, and name it DWM.
3. Inside the DWM key, create a new DWORD (32-bit) value named DisableRemoting.
4. Set its value to 1 (default is 0). This tells DWM to disable remoting for all windows in your session. Be aware: this might make Remote Desktop feel sluggish for GPU-heavy apps because they'll fall back to software rendering.
5. Restart the DWM process. Open Task Manager, find Desktop Window Manager under Processes, right-click, and choose End Task. It'll restart automatically. Or just reboot.

If you want to target just one app instead of everything, you can use the ApplicationSpecific subkey under HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM. Create a new key named after the app's executable (e.g., photoshop.exe) and put a DisableRemoting DWORD inside set to 1. The reason step 3 works is that DWM reads this key on window creation and skips the remoting path for that process.

Fix 3: Clear the DWM Shader Cache

DWM caches compiled shaders in %AppData%\Local\Microsoft\Windows\DWM. If this cache gets corrupted — maybe from a partial driver update or a disk error — DWM can't build the correct rendering pipeline for remote sessions.

1. Close all apps, especially the one that crashes. Use Task Manager to force-close anything that won't shut down normally.
2. Press Win + R, type %AppData%\Local\Microsoft\Windows\DWM, and press Enter. This opens the DWM cache folder.
3. Delete everything inside that folder. Don't delete the folder itself — just the files. You might see files named *.blob and *.cached.
4. Restart the DWM process again (same as step 4 in Fix 2) or reboot.

I've seen this fix work on Windows 11 22H2 when the error popped up after a cumulative update. The reason step 3 works is that deleting the cache forces DWM to recompile all shaders from the driver-provided metadata, which clears any stale or corrupted remoting data structures.

What to Check If It Still Fails

If none of the above helps, you've got a deeper issue. First, verify that your Remote Desktop or VM is running in enhanced session mode — sometimes the error appears because the session isn't configured for remoting at all. In Hyper-V, check under the VM's connection settings that "Enhanced session mode policy" is enabled. For Remote Desktop, make sure the remote machine is on Windows 10/11 Pro or Enterprise; Home editions have crippled RDP features.

Also check Group Policy. Run gpedit.msc (Pro/Enterprise only) and go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment. Look for "Use hardware graphics adapters for all Remote Desktop Services sessions." If it's set to Disabled, DWM can't use hardware rendering remoting at all; set it to Enabled or Not Configured.

Finally, if you're on a Windows N edition (the ones without media features), you might be missing the DirectX components DWM needs for remoting. Install the Media Feature Pack from Microsoft's website and retest. That's a niche case, but it's bit me before.