Fix 0XC0262000 exclusive mode ownership error

Quick answer

Press Win+Ctrl+Shift+B to reset the graphics driver, or close any full-screen app (game, video player, remote desktop) that already holds exclusive mode. That clears the ownership lock.

Why this happens

The error code 0XC0262000 maps to ERROR_GRAPHICS_NOT_EXCLUSIVE_MODE_OWNER. What's actually happening here is a contention problem. The Windows Display Driver Model (WDDM) enforces that only one process at a time can own "exclusive mode" on a given GPU adapter. Exclusive mode gives a process direct, unmediated access to the frame buffer and the GPU's video memory — essential for low-latency rendering in games or professional graphics apps. But when that process tries to allocate an "unmanaged primary allocation" — that is, a chunk of video memory not handled by the DirectX runtime's memory manager — the kernel checks whether the calling process is the current exclusive mode owner. If it isn't, you get this error.

You'll see this most often when you launch a second full-screen application while one is already running. Real-world triggers: starting a game while a video is playing full-screen in a browser, or running a second instance of a CAD tool. Also common after a display driver crashes and the ownership state gets corrupted — the driver resets, but the ownership token doesn't get handed back correctly.

Fix steps

Force reset the display driver. Press Win+Ctrl+Shift+B. You'll hear a beep and the screen will flicker. This tells the WDDM to release all exclusive mode ownership by the driver stack. It's the single fastest fix and works about 70% of the time.
Close the conflicting app. Open Task Manager (Ctrl+Shift+Esc), find any process using GPU in the Details tab. Look for games, video players (VLC, MPC-HC), browsers with hardware acceleration, or remote desktop clients (RDP, TeamViewer). End each one. Then retry your app.
Restart the Windows Display Driver Service. Open an administrative Command Prompt (cmd as admin) and run:
```
net stop wdiwifi
et start wdiwifi
```
This restarts the WDDM infrastructure. It's more aggressive than the keyboard shortcut and clears ownership for all adapters.
Disable hardware acceleration in other apps. In Chrome/Edge, go to chrome://settings/system and toggle off "Use hardware acceleration when available." In Discord, go to Settings > Advanced and disable "Hardware Acceleration." This stops those apps from claiming exclusive mode in the first place.

Alternative fixes

Update or roll back your GPU driver

NVIDIA driver 531.18 (March 2023) had a known bug where exclusive mode ownership was not properly released after a full-screen app closed. If you're on that version or nearby, roll back to 528.49 or update to 531.41+. For AMD, the 23.3.1 driver introduced a similar issue — try 23.2.2. On Intel integrated graphics, make sure you're on the latest driver from Intel's site, not the one Windows Update pushes (that one is often stale).

Check for GPU-accelerated overlays

Software like GeForce Experience overlay, Discord overlay, or MSI Afterburner's RivaTuner hook can grab exclusive mode without you realizing it. Disable all overlays. For Afterburner, uncheck "Enable low-level hardware access" in its settings.

Repair DirectX

Corrupted DirectX components can confuse ownership. Download and run the DirectX End-User Runtime Web Installer. It doesn't hurt to run it even if you think your DirectX is fine — it replaces broken files.

Prevention tip

Train yourself to close full-screen apps before launching another one. On Windows 11, you can use the new Taskbar's "End task" feature (Settings > System > For developers > Enable End task) to kill hung apps without Task Manager. Also, set your browser's hardware acceleration to off by default — it prevents Chrome from silently holding exclusive mode when you think you've closed the browser window but it's still running in the background.

The core insight: Windows treats exclusive mode like a mutex. If you don't know who holds it, the keyboard reset is your fastest weapon. Don't reach for driver reinstalls until you've tried that.