Hiding the Privacy Settings over Scripted Action for Windows 11 24H2 (OOBE)

Last week, I used the Windows 11 24H2 Multi-Session Image from the Microsoft Gallery for the first time while working for a new client. Initially, I didn’t notice anything unusual since I only tested the login via Azure Virtual Desktop. However, when I had to log in locally as an administrator, the privacy settings screen appeared. At first, it was just a minor annoyance, but I quickly realized: This prompt needs to go! No administrator should have to go through these questions every time they need to troubleshoot under pressure.

So, I started looking for a way to bypass this prompt. I finally found a solution thanks to Rudy Ooms. He had already defined the necessary changes as a PowerShell script—for a different purpose, but it was exactly what I needed.

Since I typically apply such settings either directly in the Gold Image or during the creation of session hosts, I created a scripted action based on Rudy Ooms’ script that I can now seamlessly integrate into my processes.

Scripted Action

Below is the scripted action I integrated into Nerdio.

#name: Disable OOBE Steps
#description: Disables OOBE steps during the first logon
#execution mode: Combined
#tags: beckmann.ch

<# Notes:

Since Windows 11 24H2 Multi User the OOBE steps are shown during the first logon as an Administrator. Before I did not see them.

This script will disable the following OOBE setps during the first logon:
- "Let Microsoft and apps use your location"
- "Find my device"
- "Send diagnostic data to Microsoft"
- "Improve inking & typing"
- "Get tailored experiences with diagnostic data"
- "Let apps use advertising ID"
- "Let Microsoft and apps use your location"

The following blog post was the answer to the question how to disable the OOBE steps:
https://call4cloud.nl/autopilot-device-preparation-hide-privacy-settings/

#>


$registryPaths = @{
    "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE"            = @{
        "DisablePrivacyExperience" = 1
        "DisableVoice"             = 1
        "PrivacyConsentStatus"     = 1
        "Protectyourpc"            = 3
        "HideEULAPage"             = 1
    }
    "HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" = @{
        "EnableFirstLogonAnimation" = 1
    }
}

foreach ($path in $registryPaths.Keys) {
    foreach ($name in $registryPaths[$path].Keys) {
        New-ItemProperty -Path $path -Name $name -Value $registryPaths[$path][$name] -PropertyType DWord -Force
    }
}

#name: Disable OOBE Steps

#description: Disables OOBE steps during the first logon

#execution mode: Combined

#tags: beckmann.ch

<# Notes:

Since Windows 11 24H2 Multi User the OOBE steps are shown during the first logon as an Administrator. Before I did not see them.

This script will disable the following OOBE setps during the first logon:

- "Let Microsoft and apps use your location"

- "Find my device"

- "Send diagnostic data to Microsoft"

- "Improve inking & typing"

- "Get tailored experiences with diagnostic data"

- "Let apps use advertising ID"

- "Let Microsoft and apps use your location"

The following blog post was the answer to the question how to disable the OOBE steps:

https://call4cloud.nl/autopilot-device-preparation-hide-privacy-settings/

$registryPaths = @{

"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE" = @{

"DisablePrivacyExperience" = 1

"DisableVoice" = 1

"PrivacyConsentStatus" = 1

"Protectyourpc" = 3

"HideEULAPage" = 1

}

"HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies\System" = @{

"EnableFirstLogonAnimation" = 1

}

foreach ($path in $registryPaths.Keys) {

foreach ($name in $registryPaths[$path].Keys) {

New-ItemProperty -Path $path -Name $name -Value $registryPaths[$path][$name] -PropertyType DWord -Force

}

Apply

The scripted action can be used both when creating a session host and when preparing a Gold Image.

VM Deployment

For VM deployment, the script can be integrated as follows:

Desktop Image – Set as image

For the desktop image, I usually set up a scheduled task where I add the script at the appropriate step:

Thanks to this method, the change is already included in the Gold Image and does not need to be applied again during VM deployment.

Conclusion

I hope this script helps you and allows you to create your Gold Image or session hosts without the privacy settings prompt for administrators. A big thank you to Rudy – his work enabled me to solve this problem quickly!