Fix DWM_E_COMPOSITIONDISABLED (0X80263001) in 3 Steps

What the %$@# is DWM_E_COMPOSITIONDISABLED?

This error code (0X80263001) means Windows' Desktop Window Manager (DWM) has stopped composing your desktop. You'll see it when apps like Photoshop, OBS, or even the Snipping Tool try to grab screen content or apply effects. I've seen it happen right after a driver update or when a lightweight remote desktop tool (like TeamViewer) messes with DWM's service. The screen might flicker or go blank for a second, then you get this error. Annoying? Yes. But fixable.

30-Second Fix: Restart the DWM Service

This is the first thing I try when I see this error. It works about 40% of the time.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click More details at the bottom if you only see a small window.
3. Go to the Services tab.
4. Scroll down to DwmService (or Desktop Window Manager Session Manager).
5. Right-click it and choose Restart.

If you don't see it there, open a Command Prompt as admin and run:

net stop uxsms && net start uxsms

That's the same service under its internal name. Wait 10 seconds, then try whatever app was failing. If the error's gone, you're done. If not, move on.

5-Minute Fix: Check and Repair DWM Service Dependencies

DWM won't start if its dependencies are missing or stuck. I've seen this happen after a Windows Update or when third-party antivirus blocks certain services. Here's how to check:

1. Press Win + R, type services.msc, hit Enter.
2. Find Desktop Window Manager Session Manager in the list. Double-click it.
3. Make sure the Startup type is Automatic. If it's Disabled or Manual, change it to Automatic.
4. Click Start if the service isn't running. If it says "Access Denied," you're not admin—run services.msc as admin.
5. Now check its dependencies: click the Dependencies tab. You'll see a list of services DWM needs. The big one is Windows Event Log (it's almost always running) and CNG Key Isolation. If either is stopped, start it manually, then restart DWM.

Still broken? Let's get our hands dirty.

15+ Minute Fix: Registry Edit to Force Desktop Composition

When the GUI and service reset fails, the registry holds the real fix. I've used this on Windows 10 22H2 and Windows 11 23H2 with consistent results. Be careful—back up your registry first (File > Export before editing).

1. Press Win + R, type regedit, hit Enter.
2. Navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM

3. Look for a DWORD called Composition. If it doesn't exist, right-click in the right pane, choose New > DWORD (32-bit), name it Composition.
4. Double-click Composition and set its value to 0 (zero). This forces DWM to re-enable composition on the next boot or service restart.
5. Close Registry Editor.
6. Open Task Manager, go to the Services tab, restart DwmService again (or run net stop uxsms && net start uxsms in an admin command prompt).

After restarting the service, the error should vanish. If you're still seeing it, there's one more tweak: check the same key under HKEY_LOCAL_MACHINE. Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM

Repeat the same steps—create or edit the Composition DWORD, set it to 0. This machine-level override covers cases where a policy or software locked DWM off globally.

If None of That Worked

I've seen this error stubbornly persist in a few specific scenarios:

• Remote desktop tools: If you use RDP, TeamViewer, or AnyDesk, try disconnecting and reconnecting. They often toggle DWM off and forget to turn it back on.
• Graphics driver corruption: Run DDU (Display Driver Uninstaller) in Safe Mode, then install the latest driver from your GPU maker—Intel, AMD, or NVIDIA.
• Windows Store apps: App-specific overlays (like Xbox Game Bar) can trigger this. Disable Game Bar in Settings > Gaming > Game Bar.

If you've tried all three steps and still see 0X80263001, something deeper is wrong. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin command prompt. That fixes system file corruption that can mimic DWM issues.

When to Just Restart the PC

I know it's cliché, but sometimes the cleanest fix is a full reboot. DWM state can get wedged in memory after a long uptime. If you skipped step one and jumped to the registry, go back and restart your machine first. It saves you 15 minutes of registry hunting.

This error is a pain, but it's almost always fixable with these steps. Start simple, escalate only if needed—and you'll have your desktop composing again in no time.