Windows Autopilot: existing devices show disabled OOBE screens with ConfigMgr Sysprep
Summary
During a Windows Autopilot for existing devices deployment, screens that are disabled in the Autopilot profile are still shown. Windows deletes AutopilotConfigurationFile.json when Sysprep.exe runs with /Generalize, which the Configuration Manager step Prepare Windows for Capture does. Microsoft documents a workaround.
Symptoms
Screens disabled in the Windows Autopilot profile, such as the Windows License Agreement screen, appear during the deployment.
Affected
- Windows Autopilot for existing devices
- Configuration Manager task sequences that use the Prepare Windows for Capture step (Sysprep.exe with /Generalize)
Workaround
- Edit the Configuration Manager task sequence.
- Disable the Prepare Windows for Capture step.
- Add a new Run command-line step that runs: C:\Windows\System32\sysprep\sysprep.exe /oobe /reboot
Fix
No fix announced; the documented task sequence change resolves the behaviour.
Recommendation
If you use Autopilot for existing devices with Configuration Manager, adjust the task sequence as described and test with a pilot device to confirm that disabled screens no longer appear.
Sources
- Windows Autopilot: known issues Vendor · learn.microsoft.com
- Task sequence steps: Prepare Windows for Capture Vendor · learn.microsoft.com
Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 18:25.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.
