We recently started working on our Windows 10 1809 build & capture. The B&C was successful, but upon boot up we could not complete the Out of Box Experience. During the Network phase, we would come to the below error.

Something went wrong But you can try again. OOBEEULA

If you like to watch the spinny circle, you can click Try again. No luck though.

Another fun fact! There is very little information about this error online. One hit was all I could find at the time of my issue.

So what do you do with any sysprep issues? Check the logs! Time to jump into c:\windows\panther\UnattendGC\setupact.log.

The end of the log presents quite a few different errors, but nothing gives any indication of the root cause. Some network errors yes, but I already know it is failing at the Network pass.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] CommitKeyboards , locale keyboard : 0409 : 00000409 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] Failed to load oobe . xml file at C : \ WINDOWS \ system32 \ oobe \ info \ oobe . xml with hr = 0x80070003 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] Failed to load oobe . xml file at C : \ WINDOWS \ system32 \ oobe \ info \ default \ oobe . xml with hr = 0x80070003 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] Failed to load oobe . xml file at C : \ WINDOWS \ system32 \ oobe \ info \ 244 \ oobe . xml with hr = 0x80070003 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] Failed to load oobe . xml file at C : \ WINDOWS \ system32 \ oobe \ info \ default \ 1033 \ oobe . xml with hr = 0x80070003 2019 -01 -31 15 : 15 : 44 , Info [ CloudExperienceHostBroker . exe ] Failed to load oobe . xml file at C : \ WINDOWS \ system32 \ oobe \ info \ 244 \ 1033 \ oobe . xml with hr = 0x80070003 2019 -01 -31 15 : 15 : 45 , Info [ CloudExperienceHostBroker . exe ] Opting in to IncludeDriverSets 2019 -01 -31 15 : 15 : 45 , Info [ CloudExperienceHostBroker . exe ] CZDPTask setting OOBE_GLOBAL_SETTING_ZDPSTATUS ZDP_Scanning . 2019 -01 -31 15 : 15 : 45 , Info [ CloudExperienceHostBroker . exe ] ISearchCompletedCallback :: Invoke called 2019 -01 -31 15 : 15 : 45 , Info [ CloudExperienceHostBroker . exe ] Wait result from WU ZDP Search : 0X1 2019 -01 -31 15 : 15 : 45 , Error [ CloudExperienceHostBroker . exe ] Failed to end completed WU ZDP search [ hr = 0x8024500C ] 2019 -01 -31 15 : 15 : 45 , Info [ CloudExperienceHostBroker . exe ] CZDPTask setting OOBE_GLOBAL_SETTING_ZDPSTATUS ZDP_Finished . 2019 -01 -31 15 : 15 : 56 , Info [ CloudExperienceHostBroker . exe ] FeatureUpdateTask setting OOBE_GLOBAL_SETTING_FEATUREUPDATESTATUS OobeFeatureUpdateStatus_Scanning . 2019 -01 -31 15 : 15 : 56 , Info [ CloudExperienceHostBroker . exe ] ISearchCompletedCallback :: Invoke called 2019 -01 -31 15 : 15 : 56 , Info [ CloudExperienceHostBroker . exe ] Wait result from WU feature update search : 0X1 2019 -01 -31 15 : 15 : 56 , Error [ CloudExperienceHostBroker . exe ] FeatureUpdateTask setting OOBE_GLOBAL_SETTING_FEATUREUPDATESTATUS OobeFeatureUpdateStatus_ScanFailed .

Next try? Let’s look for all errors in the log. Using the handy-dandy CMtrace.exe we filter on , error since the Panther logs do not use the exact formatting CMtrace is looking for. We cannot just filter on the Source field.

1 2 3 4 5 6 2019 -01 -30 21 : 43 : 47 , Error [ Shell Unattend ] ComputerName : failed to get the current computername ( 0x80070002 ) [ gle = 0x00000002 ] 2019 -01 -31 18 : 13 : 00 , Error [ msoobe . exe ] Failed to get EULA file with hr = 0x800704EC 2019 -01 -31 18 : 13 : 00 , Error [ msoobe . exe ] Failed to get EULA file with hr = 0x800704EC 2019 -01 -31 18 : 13 : 03 , Error [ msoobe . exe ] COMMIT : failed for plugin LocalUser Plugin with hr = 0x80070490 2019 -01 -31 15 : 15 : 45 , Error [ CloudExperienceHostBroker . exe ] Failed to end completed WU ZDP search [ hr = 0x8024500C ] 2019 -01 -31 15 : 15 : 56 , Error [ CloudExperienceHostBroker . exe ] FeatureUpdateTask setting OOBE_GLOBAL_SETTING_FEATUREUPDATESTATUS OobeFeatureUpdateStatus_ScanFailed .

Hmm, so it seems to be trying to get some updates from Windows Update, but not sure which.

At this point we opened a case with Microsoft, worked with a pretty amazing engineer, and found two settings in our B&C that were preventing OOBE from contacting Windows Update to look for updates during this step.

1 2 3 4 5 # Store - Turn off automatic download % windir % \ system32 \ reg . exe add "HKLM\Software\Policies\Microsoft\WindowsStore" / v "AutoDownload" / t REG_DWORD / d 2 / f # Store - Turn off offer to latest Windows % windir % \ system32 \ reg . exe add "HKLM\Software\Policies\Microsoft\WindowsStore" / v "DisableOSUpgrade" / t REG_DWORD / d 1 / f

We had added these settings just a few weeks before to help prevent Feature Upgrades from being installed on some of our VM templates. This was at the guidance of Microsoft, but none the less, was causing this issue. We disabled these two steps in our B&C, re-ran it, and upon boot up successfully made it passed the OOBEEULA error. Good times.

Edit 1/24/2020:

A great suggestion from djedail in the comments: