OSD progress hidden behind a “Just a moment” screen Windows 10 1709 -> Fix
I noticed an issue when deploying Windows 10 1709 via Task-Sequence-> after the first reboot during the step “Setup Windows and Configuration Manager” the machine came back with “Just a moment” and the progress bar was hidden. My task-sequence had no unattend file applied during the capture. I found the solution by creating an unattend file that hide’s Wifi Setup and disabled user and computer OOBE. The step was added during the step “Apply Operating System”:
The XML-File includes the following:
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <NetworkLocation>Work</NetworkLocation> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/mount/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
This is the same fix for 1703 right? Nice to know it works OK for 1709.
Thanks 😀
LikeLike
Right – I skipped 1703 🙂
LikeLike
Also when you like to add a startmenu script with a non conform xml file 😉
LikeLike
your screenshot shows unattend.txt meanwhile it should be unattend.xml
LikeLike
I can confirm that true does the trick even though it’s supposedly deprecated.
Adding a restart after Setup Windows and Config Mgr also works but this sometimes causes issues with application installation where it cannot find a source. Package based software isn’t affected by the restart.
LikeLike