Anavem
Languagefr
How to Hide Gaming Features in Windows Settings Using Microsoft Intune

How to Hide Gaming Features in Windows Settings Using Microsoft Intune

Configure Microsoft Intune to hide gaming options in Windows Settings across corporate devices using three proven methods: Device Restrictions, Settings Catalog, and OMA-URI approaches.

Evan MaelEvan Mael
March 27, 2026 15 min
mediumintune 7 steps 15 min

Why Hide Gaming Features in Corporate Windows Environments?

Gaming features in Windows 10 and 11 can significantly impact productivity and system performance in corporate environments. The built-in Game Bar, Game DVR recording capabilities, and Game Mode can consume system resources, create security concerns, and distract employees from work tasks. Microsoft Intune provides enterprise administrators with powerful tools to restrict these features across managed devices.

What Gaming Features Can You Control Through Intune?

Windows includes several gaming-related features that can be managed through Intune policies. Game Bar allows users to take screenshots and record gameplay, Game DVR enables background recording that consumes CPU and memory resources, Game Mode prioritizes gaming applications over business software, and TruePlay provides anti-cheat functionality. Each of these features can be individually controlled or blocked entirely depending on your organization's requirements.

Which Method Should You Choose for Your Environment?

Microsoft Intune offers three distinct approaches for hiding gaming features, each with specific advantages and limitations. Device Restrictions provides the fastest implementation but affects notification settings on Windows 11 22H2 and later versions. Settings Catalog offers granular control and avoids the notification issue, making it the recommended approach for most organizations. Custom OMA-URI provides maximum flexibility for complex scenarios but requires deeper technical expertise and is more prone to configuration errors.

Implementation Guide

Full Procedure

01

Access Microsoft Intune Admin Center

Start by logging into the Microsoft Intune admin center where you'll configure the gaming restrictions.

Open your web browser and navigate to https://intune.microsoft.com. Sign in with your administrator credentials that have Intune management permissions.

Once logged in, you'll see the main dashboard. Navigate to Devices in the left sidebar, then select Windows from the submenu. Click on Configuration to access the policy management area.

Pro tip: Bookmark the Intune admin center URL and consider using a dedicated browser profile for administrative tasks to avoid session conflicts.

Verification: You should see the Configuration policies page with options to create new policies and manage existing ones.

02

Create Device Restrictions Profile (Method 1)

This is the quickest method but comes with a caveat for Windows 11 22H2+ devices.

Click + Create and select New Policy. Set the following configuration:

  • Platform: Windows 10 and later
  • Profile type: Templates > Device restrictions

On the Basics page, enter these details:

Name: Hide Gaming Features - Device Restrictions
Description: Blocks gaming section in Windows Settings app

Click Next to proceed to configuration settings.

Under Configuration settings, expand the Control Panel and Settings section. Locate the Gaming option and set it to Block.

Warning: On Windows 11 22H2 and later, this method also hides the Settings > System > Notifications area due to the policy adding ms-settings:quietmomentsgame to the PageVisibilityList CSP.

Click Next through the remaining pages, assign to your target device groups, and click Create.

Verification: After policy deployment (15-30 minutes), check a target device's Settings app - the Gaming section should be hidden.

03

Configure Settings Catalog Profile (Method 2 - Recommended)

This method provides granular control and avoids the notification settings issue on Windows 11 22H2+.

Create a new policy with these settings:

  • Platform: Windows 10 and later
  • Profile type: Settings Catalog

On the Basics page, configure:

Name: Hide Gaming Features - Settings Catalog
Description: Granular gaming restrictions without affecting notifications

Click Next to reach the Configuration settings page. Click + Add settings and search for PageVisibilityList.

Select Control Panel and Settings > Page Visibility List from the results. This will add the PageVisibilityList setting to your policy.

In the PageVisibilityList field, enter the gaming pages you want to hide:

gaming-gamebar;gaming-gamedvr;gaming-gamemode;gaming-trueplay;

This configuration hides Game Bar, Game DVR, Game Mode, and TruePlay while preserving access to notification settings.

Pro tip: You can hide all gaming features by using just gaming; or be selective by specifying individual gaming components as shown above.

Complete the policy creation by clicking Next, assigning to target groups, and clicking Create.

Verification: Use Get-ChildItem HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Settings in PowerShell on a target device to confirm the PageVisibilityList registry entry is applied.

04

Implement Custom OMA-URI Configuration (Method 3)

For maximum flexibility and direct CSP control, use the custom OMA-URI method.

Create a new policy with these parameters:

  • Platform: Windows 10 and later
  • Profile type: Custom

Configure the basics:

Name: Hide Gaming Features - OMA-URI
Description: Custom OMA-URI policy for gaming restrictions

On the Configuration settings page, click + Add to create a new OMA-URI setting with these values:

Name: Hide Gaming Pages
Description: Custom CSP configuration for gaming visibility
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Settings/PageVisibilityList
Data type: String
Value: hide:gaming-gamebar;gaming-gamedvr;gaming-gamemode;

This OMA-URI directly configures the PageVisibilityList Configuration Service Provider (CSP) to hide specific gaming features.

You can also use a more comprehensive value to hide all gaming features:

Value: hide:gaming;
Warning: Microsoft recommends Settings Catalog over OMA-URI because Settings Catalog receives more frequent updates and better validation. Use OMA-URI only when Settings Catalog doesn't provide the required granularity.

Complete the policy assignment and creation process.

Verification: Check the Windows Event Viewer on target devices for Event ID 814, which confirms the PageVisibilityList CSP has been applied successfully.

05

Assign Policies to Target Groups

Proper policy assignment ensures your gaming restrictions apply to the correct devices and users.

For any of the three methods above, during the policy creation process, you'll reach the Assignments page. Here you can configure:

Include groups: Select the Azure AD groups containing devices or users that should receive this policy. Common options include:

  • Corporate devices group
  • Specific department groups (HR, Finance, etc.)
  • All devices (for organization-wide restrictions)

Exclude groups: Optionally exclude specific groups, such as:

  • IT administrators group
  • Executive devices group
  • Test devices group

Example assignment configuration:

Include: "Corporate-Windows-Devices" group
Exclude: "IT-Admin-Devices" group
Pro tip: Start with a small test group before rolling out to your entire organization. Create a "Gaming-Policy-Test" group with 5-10 devices for initial validation.

Click Next to proceed to the review page, then Create to deploy the policy.

Verification: In the Intune admin center, navigate to Devices > Monitor > Device compliance to track policy deployment status across your target devices.

06

Monitor Policy Deployment and Compliance

Track the deployment status and ensure your gaming restrictions are working correctly across all target devices.

In the Microsoft Intune admin center, navigate to Devices > Monitor > Device compliance. Here you can view:

  • Policy deployment status
  • Devices that have successfully applied the policy
  • Any devices with policy conflicts or errors

For detailed monitoring, go to Devices > All devices and select a specific device. Click on Device compliance to see the status of your gaming restriction policy.

You can also use PowerShell on target devices to verify the policy application:

# Check if PageVisibilityList registry key exists
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Settings" -Name "PageVisibilityList" -ErrorAction SilentlyContinue

# View Windows Event Logs for policy application
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Where-Object {$_.Id -eq 814} | Select-Object TimeCreated, Message
Pro tip: Set up automated compliance reports by navigating to Reports > Device compliance and creating scheduled reports for gaming policy compliance across your organization.

Verification: On a target device, open Settings app and confirm the Gaming section is no longer visible. For Windows 11 22H2+ devices using Device Restrictions method, also verify that notification settings are still accessible if that's a requirement.

07

Troubleshoot Common Issues

Address the most common problems that occur when implementing gaming restrictions through Intune.

Issue 1: Notification Settings Hidden (Windows 11 22H2+)

If you used the Device Restrictions method and users can't access notification settings, extract the policy string from Event Viewer:

# View the applied PageVisibilityList string
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Where-Object {$_.Id -eq 814 -and $_.Message -like "*PageVisibilityList*"} | Select-Object -First 1 | Format-List Message

Copy the string from the event message, remove quietmomentsgame; from it, and redeploy using Settings Catalog method.

Issue 2: Policy Not Applying

Force a manual sync on the target device:

# Trigger Intune policy sync
Invoke-Command -ScriptBlock {Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask}

Issue 3: Gaming Section Still Visible

Check policy assignment and device group membership:

# Verify device Azure AD group membership
dsregcmd /status
# Look for "AzureAdJoined : YES" and note the device ID
Warning: Policy changes can take up to 8 hours to fully propagate in some environments. Don't make multiple conflicting policies while troubleshooting - this can cause policy conflicts.

Verification: Use the Intune Troubleshooting blade (Troubleshooting + support) to diagnose specific device policy application issues and view detailed error messages.

Frequently Asked Questions

Does hiding gaming features through Intune affect Xbox app functionality on corporate devices?+
No, hiding gaming features in Windows Settings through Intune only removes the Gaming section from the Settings app. The Xbox app and other gaming applications will still function normally unless you implement additional app control policies. To restrict gaming applications entirely, you need to use App Control for Business or Managed Installers policies in addition to the Settings restrictions. The gaming restrictions only prevent users from accessing Game Bar, Game DVR, and Game Mode configuration options through the native Windows Settings interface.
Why does the Device Restrictions method hide notification settings on Windows 11 22H2?+
This occurs because the Device Restrictions gaming policy adds the 'ms-settings:quietmomentsgame' page to the PageVisibilityList CSP, which inadvertently blocks access to the notification settings area. Microsoft introduced this behavior change in Windows 11 version 22H2 and later versions. The quietmomentsgame setting controls gaming-related notification features, but its inclusion in the visibility list affects the broader notification settings section. To avoid this issue, use the Settings Catalog method instead, which allows you to exclude the quietmomentsgame parameter while still hiding other gaming features.
How long does it take for gaming restriction policies to apply to target devices?+
Intune policies typically sync to devices every 8 hours by default, but initial policy application usually occurs within 15-30 minutes for actively connected devices. You can force an immediate sync by opening the Company Portal app on the target device and selecting 'Check for updates' or by using PowerShell to trigger the PushLaunch scheduled task. The actual policy application depends on network connectivity, device power state, and current system load. For large deployments, consider staggering policy rollouts to avoid overwhelming your network infrastructure and to monitor for any unexpected issues.
Can users bypass gaming restrictions by using registry edits or group policy?+
Users with local administrator rights could potentially modify registry settings, but Intune policies are designed to override local configurations and reapply during regular sync cycles. The PageVisibilityList CSP that controls gaming feature visibility is managed at the device level and takes precedence over user-level modifications. However, if users have administrative access, they could temporarily restore gaming features until the next policy sync. To prevent this, ensure your devices follow the principle of least privilege, removing local administrator rights from standard users and implementing Windows Defender Application Control if needed.
What's the difference between Settings Catalog and OMA-URI methods for gaming restrictions?+
Settings Catalog is Microsoft's modern, recommended approach that provides a user-friendly interface with built-in validation and frequent updates. It automatically handles CSP syntax and offers better error checking during policy creation. OMA-URI is the legacy method that requires manual CSP configuration and deeper technical knowledge but offers maximum flexibility for complex scenarios. Settings Catalog policies are easier to maintain and less prone to configuration errors, while OMA-URI policies require manual syntax management and troubleshooting. Microsoft actively updates Settings Catalog with new Windows features, while OMA-URI configurations may require manual updates when Microsoft changes CSP behavior.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion