unattended.xml causing BSOD post deployment

[Braydon Hooper]

Hello everyone,

In the past I've been successfully able to skip OOBE after deployment with the unattended.xml file below on Windows 10 x64 1709 EDU images. I'm attempting to do the same thing but this time with Windows 10 x64 20H2 but I am getting a BSOD while using the same unattended.xml file that worked for my 1709 deployments. If I deploy my 20H2 image without enabling the option for "Selected image was prepared using sysprep" it will deploy and successfully complete the the distribute disk image job but I still get presented with OOBE. Is anyone else having a similar issue when trying to skip OOBE? Any help or advice is greatly appreciated (: FYI- I'm currently running GSS 3.3 RU3

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%PROCTYPE%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>%COMPNAME%</ComputerName>
<ProductKey>6TP4R-GNPTD-KYYHQ-7B7DP-J447Y</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%PROCTYPE%" 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>
<HideEULAPage>true</HideEULAPage>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
</OOBE>
</component>
</settings>
</unattend>

[andykn101]

Try validating the answer file using Windows System Image Manager:

https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/wsim/best-practices-for-authoring-answer-files

You just need to remember to replace the %COMPNAME% and %PROCTYPE%. 

Might be some of your Hide items are deprecated. Can you PXE boot the PC and get log files from c:\windows\panther and c:\windows\sytem32\sysprep and the deployed unattend.xml?

------------------------------
Trusted Advisor, Infrastructure Engineer, United Kingdom.
------------------------------

[Braydon Hooper]

Hello Andy,

Thanks very much for your input, I tried validating the answer files using Windows SIM and immediately got the error about %PROCTYPE% I changed the value to amd64 and my barebones 20H2 image deployed successfully but did not work for my complete image :\ I tried altering / removing fields the answer file but had no luck getting it to deploy. My plan now is to build my image on an older revision of windows that is officially supported by GSS 3.3 RU3.

Thank you again for your help (:

[Andrew Pratt]

I've never had success reusing an answer file from a previous version of Windows.  Try recreating the same script using the current ADK for 20H2 (which is ADK for Windows 10 2004 since Microsoft did not release a newer version for 20H2).