Manage Windows Game Bar in Registry Editor
This article provides an overview of the exact Windows Registry keys used to control and configure the Windows Game Bar and its background recording (Game DVR) features. By modifying specific DWORD values within the Registry Editor, users and administrators can enable, disable, or fine-tune Game Bar functionality across user profiles or an entire system.
Primary Registry Keys for Windows Game Bar and Game DVR
The Windows Game Bar and its background recording functionality are primarily managed across two user-level registry keys and one system policy key:
1. User GameDVR Settings
- Path:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\GameDVR - Purpose: Manages user-specific preferences for capturing gameplay and background recording.
- Key Value:
AppCaptureEnabled(DWORD 32-bit):0= Disables background recording.1= Enables background recording.
2. Game Configuration Store
- Path:
HKEY_CURRENT_USER\System\GameConfigStore - Purpose: Controls the main toggle for the Game Bar overlay.
- Key Value:
GameDVR_Enabled(DWORD 32-bit):0= Disables the Game Bar entirely.1= Enables the Game Bar.
3. System-Wide Policy (All Users)
- Path:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GameDVR - Purpose: Used by administrators to enforce system-wide rules that override individual user preferences.
- Key Value:
AllowGameDVR(DWORD 32-bit):0= Completely blocks Game Bar and background recording for all users.1= Allows Game Bar usage.
How to Edit These Keys in Regedit
- Press Win + R, type
regedit, and press Enter to open the Registry Editor. - Navigate to the desired key path using the left sidebar or the top address bar.
- If the key or value does not exist:
- Right-click the folder/key, select New > Key, and name it accordingly.
- Inside the key, right-click an empty area, select
New > DWORD (32-bit) Value, and
name it (e.g.,
AppCaptureEnabledorGameDVR_Enabled).
- Double-click the DWORD value, set the Value data to
0(off) or1(on), and click OK. - Restart your computer or restart the
explorer.exeprocess for the changes to take effect.