Windows 10: OOBE sysprep answer file for Win10 version 1703

Hello. was looking for an answer file for just answering all of the oobe questions after running sysprep with oobe in the latest version of 10 with Cortana. I don't see steps to take for that anywhere online, only tutorials for copying a profile which would just skip having to create a new user. I've messed around with a few answer files I've found online, but they don't seem to do the trick. Appreciate any tips you could give me.

Thanks! -Tim

:)

 

Install Win 10 1073 using ADK. OOBE does not ask for product key.

Hi,

There was an OOBE update for Windows 10 Version 1703 released back in May 9, 2017. This update improves the Windows
10 Version 1703 OOBE process and will be available only at the time that OOBE updates are installed. Please click on the link below more information:

OOBE update for Windows 10 Version 1703: May 9, 2017.

 

Windows 10 Update breaks Sysprep?

I am attempting to image a Dell E7470 with Sysprep to upload to my WDS server.

When I run Sysprep /oobe / shutdown, it completes. However, without Generalize, I won't be able to upload it or deploy it.

When I run Sysprep /oobe /generalize / shutdown, it reports that a fatal error has occurred. The setupact.log lists that the Miracastview app cannot be removed.

I have attempted the Remove-appxpackage commands, but it states that it has been provisioned for the user but not all users. It says to attempt removal with Add / Remove Windows features, but it is not listed there.

I have tried the steps in

https://support.microsoft.com/en-us...w-cause-sysprep-error-windows-10-version-1709

but none of this has worked either.

I guess the answer is to not run any Windows updates before Sysprep and avoid 1709? It appears to be bad news.

Anybody else encounter this? Any other solutions available?

 

Hi Tim, welcome to the Ten Forums.

Here's a sample answer file that totally automates OOBE. Regional settings are for UK (040b:0000040b & EN-GB) and need to be changed according to your region and input settings. Two local accounts will be created, local administrator account Admin and standard user . These need to be changed, too:

Code: <?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>040b:0000040b</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-GB</UILanguageFallback> <UserLocale>en-GB</UserLocale> </component> <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> <HideEULAPage>true</HideEULAPage> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <ProtectYourPC>3</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Description>Main local admin account</Description> <DisplayName>Admin</DisplayName> <Group>Administrators</Group> <Name>Admin</Name> </LocalAccount> <LocalAccount wcm:action="add"> <Description>My daily standard account </Description> <DisplayName></DisplayName> <Group>Users</Group> <Name></Name> </LocalAccount> </LocalAccounts> </UserAccounts> <TimeZone>W. Europe Standard Time</TimeZone> <RegisteredOwner></RegisteredOwner> <RegisteredOrganization>Ten Forums</RegisteredOrganization> </component> </settings> <settings pass="specialize"> <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"> <OEMInformation> <Logo>C:\Windows\System32\oemlogo.bmp</Logo> <Manufacturer>Ten Forums</Manufacturer> <SupportHours>24/7</SupportHours> <SupportPhone>+44 123 456 789</SupportPhone> <SupportURL>Windows 10 Help Forums</SupportURL> </OEMInformation> <CopyProfile>true</CopyProfile> <OEMName>ACME Computers</OEMName> <RegisteredOrganization>Ten Forums</RegisteredOrganization> <RegisteredOwner></RegisteredOwner> <TimeZone>W. Europe Standard Time</TimeZone> </component> </settings> </unattend>[/quote]

 

Kari, you are the best! Was really searching for this, and I did not even find it after installing Windows SIM and using an install.wim file. I did have to enter a line to skip the networking question however:

<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>

One more question I have is the computer name, for some reason, this is not working:

<ComputerName>LAB10</ComputerName>

Does it need to be in a certain place in the answer file?
Thanks again buddy!
Tim

 

<ComputerName> must be in Specialize pass:

Code: <settings pass="specialize"> <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"> <ComputerName>AnyName</ComputerName> </component> </settings>[/quote]

 

Thanks again, the best part is that I don't have to delete a random user account after sysprep anymore! Here is my final answer file with settings for en-US:

Code: <?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>0409:00000409</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-US</UserLocale> </component> <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> <HideEULAPage>true</HideEULAPage> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Description>Main local admin account</Description> <DisplayName>Admin</DisplayName> <Group>Administrators</Group> <Name>Admin</Name> </LocalAccount> </LocalAccounts> </UserAccounts> </component> </settings> <settings pass="specialize"> <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"> <TimeZone>Central Standard Time</TimeZone> <ComputerName>LAB10</ComputerName> </component> </settings> </unattend>[/quote]
Tim

 

Oops, upon testing it again it still doesn't name the computer LAB10. Maybe I have something wrong?

Also, the time zone is not working. Does specialize have to be before oobe?

Tim

 

The order of settings passes in answer file is irrelevant; during Windows setup, system goes through all passes in specific order and when starting each pass, checks answer file; if it contains information for that specific pass, it will be applied regardless where in answer file it was found. Really, the order of passes in answer file is not important, that is not your issue.

I tested your modified answer file and it worked perfectly, time zone and computer name changed. Did you forget the /generalize switch from Sysprep command? The settings pass Specialize components will only be applied if /generalize switch is used with Sysprep as shown below:

%windir%\system32\sysprep\sysprep.exe /generalize /oobe

 

Thanks again, was curious why when you type the /generalize into the command line when the window comes up, it is not checked? Is it still applied, or is it necessary to also check the box, also could I skip typing it and just check the box instead?

-Tim