Windows 10: Windows 10 - unable to build a sysprep image without OOBE

Discus and support Windows 10 - unable to build a sysprep image without OOBE in Windows 10 Installation and Upgrade to solve the problem; I am building a custom Windows 10 image version 1703. I want to create an image where I do not want an OOBE experience for new users. However, I am... Discussion in 'Windows 10 Installation and Upgrade' started by devanshu, Jun 27, 2017.

  1. devanshu Win User

    Windows 10 - unable to build a sysprep image without OOBE


    I am building a custom Windows 10 image version 1703.
    I want to create an image where I do not want an OOBE experience for new users.
    However, I am just not able to achieve that. I have run into multiple issues and have been digging around the issues for weeks now.
    I have followed your videos and some others as well, but nothing seems to work. I also have some scripts, which some guy had created a few years ago, but they fail to do the job (System goes into an infinite 'Just a moment' loop after restart from a sysprep).


    My sysprep xml file - planning to update all x86 to amd64
    Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipRearm>1</SkipRearm> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <CopyProfile>false</CopyProfile> <ShowWindowsLive>false</ShowWindowsLive> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>en-us</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-us</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value>QQBiAGMAZABlAGYAMQBAAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <Username>administrator</Username> </AutoLogon> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <AdministratorPassword> <Value>QQBiAGMAZABlAGYAMQBAAEEAZABtAGkAbgBpAHMAdAByAGEAdABvAHIAUABhAHMAcwB3AG8AcgBkAA==</Value> <PlainText>false</PlainText> </AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>QQBiAGMAZABlAGYAMQBAAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Name>Administrator</Name> <Group>Administrators</Group> <DisplayName>Administrator</DisplayName> <Description>Local Administrator</Description> </LocalAccount> </LocalAccounts> </UserAccounts> <RegisteredOrganization>Washington University</RegisteredOrganization> <RegisteredOwner>Olin Library</RegisteredOwner> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <Order>1</Order> <CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk **REMOVED**</CommandLine> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>2</Order> <CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <cpiWindows 10 - unable to build a sysprep image without OOBE :eek:fflineImage cpi:source="catalog:d:/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>[/quote]
    Please help

    :)
     
    devanshu, Jun 27, 2017
    #1
  2. JonW2016 Win User

    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?
     
    JonW2016, Jun 27, 2017
    #2
  3. Fresh Install - Stop Windows Store Updating

    Hi there

    I am trying to build a vanilla image of Win10Pro.

    I am clean installing the OS, joining a domain installing a limited array of software, updating the OS then trying to sysprep (oobe gen).

    But all I keep getting is the provisioned app for all users error when I try to run sysprep.

    I also get the same issue when not doing windows updates but everything else.

    Is there a way to disable the Store updates immediately as they seem to start updating the second after first login.
     
    DanielMinett, Jun 27, 2017
    #3
  4. Kari Win User

    Windows 10 - unable to build a sysprep image without OOBE

    I copied your answer file pasting it to Notepad to examine it. A fast scan reveals it is not kosher. Let me check it line by line, I will come back.
     
  5. devanshu Win User
    This is what I have updated to - using parts of previous file I have posted
    Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="0000" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>net user administrator /active:yes</Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="0000" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="0000" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DesktopOptimization> <ShowWindowsStoreAppsOnTaskbar>false</ShowWindowsStoreAppsOnTaskbar> </DesktopOptimization> <StartTiles> <PromoteOEMTiles>false</PromoteOEMTiles> </StartTiles> <ComputerName>7050-Win10-Pub</ComputerName> <CopyProfile>true</CopyProfile> <RegisteredOrganization>xxxx</RegisteredOrganization> <TimeZone>Central Time Zone</TimeZone> <ShowWindowsLive>false</ShowWindowsLive> <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="0000" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-us</InputLocale> <SystemLocale>en-us</SystemLocale> <UILanguage>en-us</UILanguage> <UserLocale>en-us</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="0000" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value>xxx</Value> <PlainText>false</PlainText> </Password> <Username>administrator</Username> </AutoLogon> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk **REMOVED**</CommandLine> <RequiresUserInput>false</RequiresUserInput> <Order>1</Order> </SynchronousCommand> <SynchronousCommand wcm:action="add"> <Order>2</Order> <CommandLine>cscript //b c:\windows\slmgr.vbs /ipk /ato</CommandLine> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <AdministratorPassword> <Value>xxx</Value> <PlainText>false</PlainText> </AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>xxx</Value> <PlainText>false</PlainText> </Password> <Description>Local Administrator</Description> <DisplayName>Administrator</DisplayName> <Group>Administrators</Group> <Name>Administrator</Name> </LocalAccount> </LocalAccounts> </UserAccounts> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipRearm>1</SkipRearm> </component> </settings> <cpiWindows 10 - unable to build a sysprep image without OOBE :eek:fflineImage cpi:source="wim:c:/windows/system32/sysprep/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>[/quote]
     
    devanshu, Jun 27, 2017
    #5
  6. Kari Win User
    @devanshu, please take this in positive way it is intended: I must reprimand you! When posting something like now your answer files, please edit them to remove all personal / organisational information.

    I've now asked moderators to remove your MAK product key from both answer files you have posted. That is information you should never share nor post.

    That being said, I think I've found your error but let me test something first, I will post more in a few minutes.
     
  7. Kari Win User
    OK, both your answer files contain one deprecated setting that does no harm, Sysprep just ignores it: <ShowWindowsLive> is no longer working. See this reference article: ShowWindowsLive

    OK, then the error: In your answer file you are creating a local admin account named Adminsitrator. That won't work, of course; user profile Administrator is the built-in system account. Whether it is disabled / unactivated as by default, or enabled / activated as you do in your answer file, the profile name Administrator is reserved and can't be used for another profile.

    What follows is that when OOBE runs, system tries to create the initial user profile failing every time because the name you have given cannot be used for a local non-system admin account. Windows reboots and tries again, with same result.
     
  8. devanshu Win User

    Windows 10 - unable to build a sysprep image without OOBE

    Thanks, I'll try that and post the update here in 12 hours
     
    devanshu, Jun 27, 2017
    #8
  9. devanshu Win User
    After the administrator details were removed, the system gave a blank error message followed by an error message saying - Windows could not complete the installation. To install Windows on this computer, restart the installation.

    Steps I followed:
    1. Install Windows without connecting to the internet
    2. Login into Audit mode
    3. Close sysprep pop-up. Launch Command prompt. Navigate to the sysprep folder and give the sysprep command.
    4. Restart
     
    devanshu, Jun 27, 2017
    #9
  10. Kari Win User
    Here's a standard answer file I use for my deployments. It completely automates OOBE. Compare it to your answer file to see if it could help you:

    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> <LocalAccount wcm:action="add"> <Password> <Value>UwBvAG0AZQBQAGEAcwBzAHcAbwByAGQAMQAyADMAUABhAHMAcwB3AG8AcgBkAA==</Value> <PlainText>false</PlainText> </Password> <Description>A guest account</Description> <DisplayName>Visitor in Casa </DisplayName> <Group>Guests</Group> <Name>House Guest</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <TimeZone>W. Europe Standard Time</TimeZone> <RegisteredOwner></RegisteredOwner> <RegisteredOrganization>ACME Computers</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>ACME Computers</Manufacturer> <SupportHours>24/7</SupportHours> <SupportPhone>+44 123 456 789</SupportPhone> <SupportURL>Web Server's Default Page</SupportURL> </OEMInformation> <CopyProfile>true</CopyProfile> <OEMName>ACME Computers</OEMName> <RegisteredOrganization>ACME</RegisteredOrganization> <RegisteredOwner></RegisteredOwner> <TimeZone>W. Europe Standard Time</TimeZone> </component> </settings> </unattend>[/quote] One thing I noticed is that you use synchronous commands. I try to avoid them, using batch files instead.
     
  11. devanshu Win User
    Thanks a lot, Kari.
    I'll remove the synchronous commands, compare with your file and check once again.
    Meanwhile, do the steps I mentioned seemed correct - I tried once again by adding a step: Set-ExecutionPolicy unrestricted
    But it has failed again.
     
    devanshu, Jun 27, 2017
    #11
  12. Kari Win User
    The answer file I posted works for 100% sure. Notice that my answer files contain reference to OEM logo. This line must be removed, if the mentioned location does not contain an OEM logo (120 pix BMP image):

    Code: <OEMInformation> <Logo>C:\Windows\System32\oemlogo.bmp</Logo> <Manufacturer>ACME Computers</Manufacturer> <SupportHours>24/7</SupportHours> <SupportPhone>+44 123 456 789</SupportPhone> <SupportURL>Web Server's Default Page</SupportURL> </OEMInformation>[/quote]
    Can't understand what you mean with setting PowerShell script execution policy unrestricted? PowerShell has nothing to do with Sysprep.

    About your steps, yes seems OK.
     
  13. devanshu Win User

    Windows 10 - unable to build a sysprep image without OOBE

    Thanks Kari, that worked.!!
    I do not want an admin account to be visible up front - should I just skip the entire part:
    Code: <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>Kari</DisplayName> <Group>Users</Group> <Name>Kari</Name> </LocalAccount> <LocalAccount wcm:action="add"> <Password> <Value>UwBvAG0AZQBQAGEAcwBzAHcAbwByAGQAMQAyADMAUABhAHMAcwB3AG8AcgBkAA==</Value> <PlainText>false</PlainText> </Password> <Description>A guest account</Description> <DisplayName>Visitor in Casa Kari</DisplayName> <Group>Guests</Group> <Name>House Guest</Name> </LocalAccount> </LocalAccounts> </UserAccounts>[/quote]
     
    devanshu, Jun 27, 2017
    #13
  14. Kari Win User
    That about accounts you set up, that's of course completely up to you and your needs. My answer file sample creates those three accounts I want on every machine; a local admin account, my own standard user account, and a guest account.
     
  15. devanshu Win User
    Works like a Charm.!
    I am setting it up for academic public systems where I am looking to setup deepfreeze. Would you suggest installing it before sysprep or after?
    Regards,
     
    devanshu, Jun 29, 2017
    #15
Thema:

Windows 10 - unable to build a sysprep image without OOBE

Loading...
  1. Windows 10 - unable to build a sysprep image without OOBE - Similar Threads - unable build sysprep

  2. SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation"

    in Windows 10 Gaming
    SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation": i have error of Sysprep "Sysprep was not able to validate your Windows installation.Review the log file at %WINDIR%\System32\Sysprep\Panther\setupact.log for details. After resolving the issue, use Sysprep to validate your installation again." when i want to enter the mode...
  3. SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation"

    in Windows 10 Software and Apps
    SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation": i have error of Sysprep "Sysprep was not able to validate your Windows installation.Review the log file at %WINDIR%\System32\Sysprep\Panther\setupact.log for details. After resolving the issue, use Sysprep to validate your installation again." when i want to enter the mode...
  4. SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation"

    in Windows 10 Installation and Upgrade
    SYSPREP OOBE GENERALIZE Error ""Sysprep was not able to validate your Windows installation": i have error of Sysprep "Sysprep was not able to validate your Windows installation.Review the log file at %WINDIR%\System32\Sysprep\Panther\setupact.log for details. After resolving the issue, use Sysprep to validate your installation again." when i want to enter the mode...
  5. Making Windows Image Without Sysprep Generalize tools, is Wrong?

    in Windows 10 Gaming
    Making Windows Image Without Sysprep Generalize tools, is Wrong?: Dear Microsoft teamI have a question about Windows Image, if i took Windows Image Without Sysprep Generalize tools, I installed all apps and Restated machine and took image with Acronis , and Restored this image in others machines, is this steps Wrong ?Should I make Sysprep...
  6. Making Windows Image Without Sysprep Generalize tools, is Wrong?

    in Windows 10 Software and Apps
    Making Windows Image Without Sysprep Generalize tools, is Wrong?: Dear Microsoft teamI have a question about Windows Image, if i took Windows Image Without Sysprep Generalize tools, I installed all apps and Restated machine and took image with Acronis , and Restored this image in others machines, is this steps Wrong ?Should I make Sysprep...
  7. Making Windows Image Without Sysprep Generalize tools, is Wrong?

    in Windows 10 Installation and Upgrade
    Making Windows Image Without Sysprep Generalize tools, is Wrong?: Dear Microsoft teamI have a question about Windows Image, if i took Windows Image Without Sysprep Generalize tools, I installed all apps and Restated machine and took image with Acronis , and Restored this image in others machines, is this steps Wrong ?Should I make Sysprep...
  8. Sysprep fails - Windows 10 build 10162

    in Windows 10 Installation and Upgrade
    Sysprep fails - Windows 10 build 10162: Hello Guys I'm trying to sysprep a Windows 10 Enterprise build 10162 so that i can capture, but i'm getting some errors and hope you guys have some sort of solution. I've tried removing The upgrade key in HKLM system, but that didn't help. [img] Settings i'm...
  9. Failure in Sysprep building install image

    in Windows 10 Installation and Upgrade
    Failure in Sysprep building install image: I am the manager of a group refurbishing computers for children and needy adults. We were doing Windows 7 until it was stopped. I am trying to build an image in Windows 10 which maintains the look and feel of the Win 7 machine. I have not made any change to anything in the...
  10. Windows 10 1511 sysprepping and imaging (LOG)

    in Windows 10 Installation and Upgrade
    Windows 10 1511 sysprepping and imaging (LOG): Hello, my native language is spanish but I will try to "make to undestand" all thigns that I will write here. May be there is not the place to log, but is my first time testing the installation to sysprep and image Windows 10 1511 (10586.0), and perhaps help to others....

Users found this page by searching for:

  1. sysprep without oobe

    ,
  2. sysprep without oobe windows 10

    ,
  3. sysprep witout oobe

    ,
  4. generalize windows 10 sysprep without oobe,
  5. windows 10 oobe do not display create an account for this pc