Windows Registry: Disabling FSO for Lower Input Lag

Fullscreen Optimizations act as a hybrid between “Fullscreen Exclusive” and “Windowed” modes. While this allows for faster Alt-Tabbing and volume overlays, it forces the game frame through the Windows compositor, adding a buffering layer that can delay input-to-pixel response. By modifying the GameConfigStore and GameDVR flags in the registry, we can force the OS to respect true “Exclusive Fullscreen” calls from the game engine, bypass the DWM flip-model latency, and stabilize frame pacing in DX11 and DX12 titles.

File Path

Windows Registry modifications are handled via the native Registry Editor. To apply these changes, you must navigate to the following subkeys:

HKEY_CURRENT_USER\System\GameConfigStore

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GameDVR

Technical Note: Always export a backup of your current key (Right-click > Export) before applying manual DWORD modifications to ensure system stability.

Registry Optimization Block

To globally disable Fullscreen Optimizations and ensure true exclusive mode, apply or create the following DWORD (32-bit) values:

Subkey Path	Value Name	Value Data	Purpose
HKCU\System\GameConfigStore	GameDVR_FSEBehavior	2	0 = Enabled, 2 = Disabled. Globally tells Windows to ignore FSO flags.
HKCU\System\GameConfigStore	GameDVR_FSEBehaviorMode	2	Forces the specific FSE (Full Screen Exclusive) behavior profile.
HKCU\System\GameConfigStore	GameDVR_HonorUserFSEBehaviorMode	1	Forces the OS to prioritize user-defined FSE settings over game defaults.
HKCU\System\GameConfigStore	GameDVR_DXGIHonorFSEWindowsCompatible	1	Ensures DXGI swapchains respect exclusive mode compatibility.

Technical Breakdown and Performance Analysis

Disabling FSO changes how the Windows Display Driver Model (WDDM) handles the “Swap Chain”:

• DWM Bypass: When FSO is disabled, the game can achieve “Independent Flip,” allowing it to present frames directly to the display controller without the Desktop Windows Manager process intervening.
• Latency Reduction: Measurements in 2026 gaming environments show a reduction of approximately $5ms$ to $12ms$ in end-to-end latency in titles like Counter-Strike 2 and Valorant when FSO is successfully bypassed.
• Overlay Compatibility: Note that disabling FSO will also disable the Windows Volume Overlay and Xbox Game Bar overlays during gameplay, which is the primary indicator that the tweak is active.
• DX12 Exception: Some modern DirectX 12 titles use a “Flip Model” that mimics exclusive fullscreen even with FSO enabled. For these games, registry tweaks may have diminishing returns, but they still provide a fallback for driver-level stability.

HowTo: Universal Global FSO Disable

Follow these steps for a system-wide latency reduction on GameEngineer.net:

1. Open Regedit: Press Win + R, type regedit, and hit Enter with Administrator privileges.
2. Navigate to GameConfigStore: Go to HKEY_CURRENT_USER\System\GameConfigStore.
3. Apply FSEBehavior: Double-click GameDVR_FSEBehavior and set it to 2. If it doesn’t exist, create a New DWORD (32-bit) Value.
4. Policy Override: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\ApplicationManagement\AllowGameDVR. Set the value to 0 to ensure GameDVR (which powers FSO) is fully suppressed.
5. Restart: You must sign out or restart your PC for the WDDM compositor to reload with the new flags.
6. Per-App Backup: For certain stubborn games (like Fortnite in DX12), you may still need to right-click the .exe > Properties > Compatibility and check “Disable fullscreen optimizations” manually, as some modern engines can override global registry flags.

Technical Explanation: Swap Chain Flip Model

The primary reason to disable FSO is to avoid the Composed Flip model. In a composed environment, the GPU writes the game frame to a back-buffer, which is then sent to the DWM to be “composed” with other windows (like a Discord notification or the taskbar) before reaching the screen. This adds exactly one frame of latency. By forcing Exclusive Fullscreen via registry hacks, you engage the Hardware Flip or Independent Flip path. Here, the GPU simply hands the entire screen buffer to the display hardware. By removing the “middleman” (DWM), you ensure that the very latest frame generated by your GPU is the one displayed on your monitor’s next refresh cycle.