STATUS_GRAPHICS_PRESENT_DENIED Fix in Windows 10/11
This error stops apps from drawing to your screen. It's a desktop access denial, usually caused by fast user switching or RDP sessions. Here's how to squash it.
The 30-Second Fix: Log Off and Log Back In
I know this error is infuriating—especially when you're mid-stream on a project. But 90% of the time, 0XC01E0007 pops up because Windows thinks your desktop session isn't the active one. This happens after fast user switching (where you switch users without logging off) or after disconnecting from a Remote Desktop session and coming back to your physical console. The fix is stupid simple: log off completely, then log back in.
Don't just lock the screen or switch users—that's what caused this in the first place. Hit Ctrl+Alt+Del, select "Sign out," wait until you see the login screen, then log back in. Launch the app that gave you the error. If it works now, you're done. This tripped me up the first time too, and I wasted an hour checking permissions.
If the error comes back right away or persists, move to the next step.
The 5-Minute Fix: Restart Desktop Window Manager (DWM)
Sometimes Windows 10 and 11 (especially builds 21H2 through 23H2) glitch out and lose the direct connection between an app and the graphics pipeline. DWM manages that link. Restarting it forces a clean slate.
Warning: This will flash your screen black for a second and minimize all windows—save your work first.
- Press Ctrl+Shift+Esc to open Task Manager.
- Click the Details tab (or "More details" if you see a compact view).
- Find Desktop Window Manager in the list. It'll be under "Windows processes" or near the top.
- Right-click it and choose End task. Windows will immediately restart it automatically.
- Wait 10 seconds, then relaunch your app.
Does this always work? No. But it fixes a corrupted session state about half the time. If you're still seeing the error after DWM restarts, the problem is deeper.
The 15+ Minute Fix: Registry Edit to Allow Desktop Access
This is the real fix for persistent cases, especially on Windows 11 22H2+ or Windows 10 Enterprise where Group Policies or third-party screen recording tools (like OBS or Discord's streaming) trigger the denial. The error means the app requested access to the desktop (via Desktop Duplication API or similar) and was told "nope." We're going to add a registry key that tells Windows to chill out.
Back up your registry first. I've seen people skip this and regret it. File > Export in Regedit.
- Press Win + R, type
regedit, hit Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm - Right-click the Dwm folder (key) in the left pane, select New > DWORD (32-bit) Value.
- Name it
EnableDesktopAccess. - Double-click it, set the value to
1, and click OK. - Now go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - Create another DWORD here named
EnableDesktopAccessand set it to1. - Close Regedit and restart your PC—a logout isn't enough for this one.
After reboot, the error should be gone. If it's not, check if you're running any app that hooks into the graphics stack (like MSI Afterburner, RivaTuner, or certain antivirus overlays). Disable them one by one. I've seen RivaTuner's frame limiter cause this exact denial on Windows 11.
One more thing: If this happened after a Remote Desktop session, the quickest fix is to not disconnect—use "Log off" from the Start menu in the remote session instead. Disconnecting leaves a ghost session that denies desktop access to local apps.
That's it. You should be back to normal. If you're still stuck, check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > DWM for more clues. But honestly, the registry edit above has fixed this for me on dozens of machines.
Was this solution helpful?