You set the game to Fullscreen, but Task Manager shows "Desktop Window Manager" (dwm.exe) still using 2% GPU. You are not in exclusive mode.
The Culprits:
The Litmus Test:
Load a game in "Fullscreen." Press Windows Key on your keyboard.
If your viewerframe is on Monitor A (144Hz) and Monitor B (60Hz) has a video playing, the DWM may force shared mode on both to sync composition timing.
Fix: For critical exclusive mode work, disconnect secondary monitors or set them to the same refresh rate. viewerframe mode exclusive
There are three critical reasons to force exclusive mode for your viewerframe.
Most modern applications run in Windowed or Borderless Fullscreen modes. In these states, the Windows DWM (Desktop Window Manager) still has its hands on the final frame. Your application renders, passes the image to the OS, the OS composites it with your taskbar, notifications, and other windows, and then sends it to the monitor.
Exclusive Mode cuts out the middleman.
When you enable viewerframe mode exclusive, the application takes direct ownership of the display output. The operating system steps aside. The GPU sends frames straight to the monitor without any compositing interference. You set the game to Fullscreen, but Task
You will rarely see a checkbox labeled "Exclusive Mode." Instead, you toggle this via:
Why would you fight to enable this mode? The benefits are tangible and measurable.
The most common implementation of viewerframe mode exclusive is VR Direct Mode (SteamVR/Oculus).
When you put on a VR headset, the headset displays are not treated as standard Windows monitors. The runtime (OpenXR) activates an exclusive mode pipeline. The left eye and right eye viewerframes are rendered and sent directly to the headset's display controller. If exclusive mode fails, the headset image appears as a distorted window on your desktop, inheriting 30-40ms of latency—enough to cause motion sickness. The Litmus Test: Load a game in "Fullscreen
Troubleshooting tip: If your VR headset shows "Compositor" errors, you are likely dropping out of viewerframe mode exclusive due to background applications polling the display.
Title: Unlocking True Fullscreen: Understanding viewerframe mode exclusive
Date: April 13, 2026 Category: Graphics & Performance Reading Time: 3 minutes
If you have ever tweaked a configuration file for a game engine, fiddled with a Unity build, or optimized a WebGL experience, you have likely stumbled upon the cryptic command: viewerframe mode exclusive.
At first glance, it looks like leftover debug code. In reality, it is the gatekeeper between "borderless window" performance and true, hardware-level fullscreen power.
Here is what it does, why it matters in 2026, and when you should (and shouldn’t) use it.