How to Disable the Out-of-Box Privacy Prompts in Windows 11

Quick fix: During Windows 11 OOBE (Out-of-Box Experience): you can’t fully skip privacy prompts; you can only pick “No” / “Required only” on each. To pre-configure for deployment: use answer file (unattend.xml) with privacy settings pre-set. For specific provisioning packs: Windows Configuration Designer. For Pro/Enterprise: Group Policy + Intune.

OOBE asks: location, diagnostic data, tailored experiences, advertising ID, find my device, ink & type. Each is a privacy decision. For fleet deployments: answer file or provisioning package pre-answers.

What causes this need

OOBE privacy prompts during initial setup of fresh / reset Windows 11. Issues:

• Time-consuming for fleet deployment.
• End users click through without reading.
• Want consistent default settings across PCs.
• Want privacy-maximal defaults (everything off).

Method 1: Click through with “No” to all

The simplest manual route.

1. During OOBE: for each privacy prompt, pick the most restrictive:
   • Location: No.
   • Find my device: No.
   • Diagnostic data: Required only.
   • Improve inking and typing: No.
   • Tailored experiences: No.
   • Advertising ID: No.
2. Click Accept (with all unchecked / restrictive).
3. Manual, but quick. ~30 seconds per prompt set.
4. For fleet: not scalable; use Method 2.

This is the manual route.

Method 2: Use Windows Configuration Designer

For deployment images.

1. Install Windows Configuration Designer from Microsoft Store.
2. Run. Create provisioning package.
3. Configure:
   • Set device name.
   • Set time zone.
   • Skip OOBE prompts.
   • Pre-set privacy values.
4. Export as .ppkg file.
5. For deployment: copy .ppkg to USB. During OOBE, plug in USB. Windows detects and applies.
6. For IT mass deployment: integrate with Configuration Manager, Intune, or MDT.
7. For Pro / Enterprise: provisioning packages support more options.
8. For Home: limited; some packages require Pro.

This is the deployment route.

Method 3: Use unattend.xml answer file

For advanced deployment.

1. Create unattend.xml with answer to OOBE prompts.
2. Microsoft documentation: learn.microsoft.com/windows-hardware/customize/desktop/unattend.
3. Example unattend.xml snippet for privacy:

   <OOBE>
       <HideEULAPage>true</HideEULAPage>
       <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
       <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
       <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
       <NetworkLocation>Work</NetworkLocation>
       <ProtectYourPC>3</ProtectYourPC>
       <SkipUserOOBE>true</SkipUserOOBE>
   </OOBE>

4. Place file on USB or include in image.
5. During boot, Windows reads unattend.xml.
6. OOBE prompts skipped where configured.
7. For corporate: Sysprep + image deployment includes unattend.xml.
8. For Microsoft Deployment Toolkit (MDT): full automation.

This is the unattended route.

How to verify the fix worked

• OOBE doesn’t show privacy prompts (with Method 2 or 3).
• Or all prompts answered “No” / “Required only” consistently.
• Settings → Privacy & security → verify settings match expected defaults.
• For deployment: same settings across all PCs.

If none of these work

If prompts persist: Different OOBE phase: some prompts shown after first sign-in. Configure those in post-OOBE settings. For Microsoft 365 / Microsoft Account: requires sign-in. Privacy prompts after sign-in. For specific build differences: Win11 22H2 vs 24H2 have different OOBE flows. Test with target build. For Insider builds: more changes. Stable better for unattend. For chronic privacy creep: post-install, Settings → Privacy & security → review and disable all unwanted features. For corporate Group Policy: apply after deployment for fine-tuned control. For chronic OOBE issues: vendor (Dell, HP) may add their own OOBE screens; not Microsoft. Customize via vendor tools.

Bottom line: Manual: click “No” / “Required only” on each prompt. For deployment: Windows Configuration Designer .ppkg or unattend.xml answer file. Use Group Policy / Intune for post-OOBE policy.