Managing the "Choose Privacy Settings for Your Device" Screen in Windows 11 If you've ever deployed or updated Windows 11 in an enterprise setting, you’ve probably come across the “Choose privacy settings for your device” screen. While it's helpful for end users in managed environments it can be disruptive, especially when you want consistency and compliance across devices. In this video, we'll walk through several ways to control or disable this sign-in privacy experience, From registry tweaks to PowerShell automation. Before we begin, be sure to subscribe to NinjaOne’s IT video hub and our YouTube channel for more tech content like this. Before diving in, make sure you've got a few prerequisites in place. Administrator access is required since these are system-level changes. Group Policy Editor access if you’re working on Windows 11 Pro, Enterprise, or Education editions. Registry Editor access. This is available on all editions, including Home. How to Configure “Choose Privacy Settings for Your Device” Method 1: Local Group Policy Editor for domain or work group environments where you want to standardize the sign-in experience, the Local Group Policy Editor is the most straightforward option. Here's how. Press Win + R, type gpedit.msc, and launch it with Ctrl + Shift + Enter. Navigate to this path. Open Don’t launch privacy settings experience on user logon. Set it to Enabled if you want to hide the screen, or Disabled/Not Configured to allow it. Apply the change, then update policies with gpupdate /force. This change applies only to the local machine. To deploy it across an organizational unit, replicate the setting using the Group Policy Management Console (GPMC). Method 2: Registry If you’re running Windows 11 Home or you just prefer registry-level control, this method works universally. Just remember to back up the registry before making changes. Press Win + R, type regedit, and run as administrator. Navigate to this path HKEY_LOCAL_MACHINE\SOFTWARE\Policies \Microsoft\Windows\OOBE If the OOBE key doesn’t exist, create it. Inside that key, create or edit a DWORD (32-bit) Value named DisablePrivacyExperience. Set the value to 1 to disable the privacy screen, or 0 to enable it. Optional Method: PowerShell Automation PowerShell can streamline this processby creating and managing the registry entry for you. It validates input, reduces human errors, and scales much better for multi-device deployments. Use New-Item to create the OOBE registry path if it doesn’t exist. Use New-ItemProperty to configure the DisablePrivacyExperience DWORD with a value of 1 to disable the screen. Or, remove the property if you want to restore default behavior. You’ll find the full, ready-to-use commands in our accompanying blog. You can also export them into a .ps1 script for deployment via external drives, network shares, or your endpoint management platform. Whether you use Group Policy for enterprise-wide deployments, Registry Editor for smaller setups, or PowerShell for scalable automation, Windows gives you the flexibility to enforce consistent privacy standards while reducing setup friction. For more information, check out our official blog post on How to configure the “Choose Privacy Settings for your Device” at sign-in for Windows 11, Linked in the description below.