This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 9%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETI%3C/text%3E%3C/svg%3E)
The Case of "Just a Moment..." (MEMCM OSD)
The machine hangs in the OOBE pass after OSD. It will sit at "just a moment" for ten minutes, then timeout and restart to "Why did my PC restart?" Clicking next will run it through OOBE again which will succeed. I'd like to know the different OOBE Monitor event codes and what they correspond to, as it appears something relating to event 103 is timing out.
Just a wild guess, but try to use as simple unattend.xml as possible. I suspect you might have something extra in xml which should not be there. Also, in SCCM OSD, you should not have OOBE visible, it should be silent.
Thank you for the reply. how do I make OOBE silent?
here is the unattend.xml,
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="wow64" 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>
<SkipMachineOOBE>true</SkipMachineOOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>%OSDInputLocale%</InputLocale>
<SystemLocale>%OSDSystemLocale%</SystemLocale>
<UILanguage>%OSDUILanguage%</UILanguage>
<UILanguageFallback>%OSDUILanguageFallback%</UILanguageFallback>
<UserLocale>%OSDUserLocale%</UserLocale>
</component>
</settings>
</unattend>
What build you have in Windows 10? I am pretty much done with my CM (moved totally to Intune), but if you absolutelly need help, I can dig up my unattend.xml and drop it here. I probably have 1909 and 20H2 in my lab, I can quickly test that I don't have same symptom and give you my xml. Or you can google around what are minimum values required for unattend,xml and go with that just a test. This also might be common/generic problem for most of organizations, because I saw somewhere else recently exact same problem.
remember to underline me like this @The Imaging Engineer that I will receive alert about this.
@Pavel yannara Mirochnitchenko - The prompt response is highly appreciated. Based on your feedback, I have removed settings of OOBE and trying to test.
Also, I would appreciate it if you could share the unattend.xml. We have the 20H2, June 2021 version.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" 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">;
<InputLocale>%OSDInputLocale%</InputLocale>
<SystemLocale>%OSDSystemLocale%</SystemLocale>
<UILanguage>%OSDUILanguage%</UILanguage>
<UILanguageFallback>%OSDUILanguageFallback%</UILanguageFallback>
<UserLocale>%OSDUserLocale%</UserLocale>
</component>
</settings>
</unattend>
@The Imaging Engineer for some reason your underline did not work and I was not alerted. I will probably work in my onprem lab this or next week, let me check on that. The only challenge is now only to remember this need :D ..(you can find me on a Facebook)
Remove these two lines. Both are deprecated and can have the effects you are experiencing
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
yes, I tried removing them as well, however to no avail
Can you check the unattend.xml that is downloaded to the disk while you are in WinPE while the TS is running and see what values you have for OOBE in there?
on the contrary, specifying those depreciated values makes the difference
Glad it helped, they indeed cause these issues. Their deprecation is documented in a couple places
https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/automate-oobe
https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image
The effects you see however are not formally documented from what I know, unless you experience it yourself or look around the forums.
@Colin Ford How did I make it work without using skipMachineOOBE and skipUserOOBE?
No, was just confirming what you found and the relevant documentation. Glad it's working :)
the issue still persists.
Sorry to hear that. Can you try with vanilla media? (assuming you are deploying at the moment a captured image)? If this works, can you check that you are not using those values in your capture unattend.xml?
thank you @Colin Ford for the input. It is a vanilla image. If I don't use those values, it restarts unexpectedly during OOBE
What version of ConfigMgr and ADK are you using?
2103 and 2004