Conversation
- apply the machine-wide OOBE policy before image capture - validate the policy value and DWORD type with Pester - leave non-ARM64 image behavior unchanged closes actions#14069
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Disclosure : This PR have been created with the help of AI (GPT 5.6 Sol) but reviewed by HB (Human Brain 😄)
Description
Bug fixing
Windows 11 ARM64 runners can display the "Choose privacy settings for your device" experience during first logon, taking focus away from applications and breaking automated GUI tests.
Sets the documented machine-wide
DisablePrivacyExperiencepolicy to DWORD1inConfigure-BaseImage.ps1, guarded byTest-IsWin11-Arm64. Both Windows 11 ARM64 image variants already execute this script before image capture, so the policy applies to newly created runner accounts rather than only the image-build account.Add a read-only Pester assertion in
WindowsFeatures.Tests.ps1that verifies the policy value and registry type. Run it immediately after configuration and through the existing full image test suite. The configuration and assertion are restricted to Windows 11 ARM64.Microsoft documents the policy here : https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-privacy#disableprivacyexperience
This change prevents the privacy experience from launching on subsequent eligible logons. It does not dismiss an already-open window or address the separate OneDrive and WSL prompts discussed in the issue. No process termination, UI automation, or background watcher is added (which are current workarounds).
Validation
Related issue :
Closes #14069
Check list