Windows 10: WDS Deployment Fails on OOBE unattend file every time

Discus and support WDS Deployment Fails on OOBE unattend file every time in Windows 10 Installation and Upgrade to solve the problem; Hello, My first post, but follow the site regularly! I am trying for the 1st time, to figure out WDS to deploy a customized W10 image. I have tried... Discussion in 'Windows 10 Installation and Upgrade' started by PrairieSailor, May 4, 2021 at 9:27 AM.

  1. WDS Deployment Fails on OOBE unattend file every time


    Hello, My first post, but follow the site regularly! I am trying for the 1st time, to figure out WDS to deploy a customized W10 image. I have tried many, many times, and just can not get the unattend.xml file to work. I keep getting an error about "microsoft-shell-setup". I have validated the XML file repeatedly in System Image Manager, and it always passes. Nevertheless I keep removing things to try to narrow down the problem, but keeps failing every time. And of course the whole deployment process takes forever each time...so it's getting frustrating. I have included my current version of the file, if someone has thoughts about a possible cause. <?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> <HideLocalAccountScreen>true</HideLocalAccountScreen> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>UwAzAHIAdgAxAGMAMwAhADMANgA1ACEARAAzAHMAawAhAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Description>Veeam Admin User</Description> <DisplayName>Veeam Admin</DisplayName> <Group>Administrators</Group> <Name>VeeamAdmin</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <RegisteredOrganization>365 Technologies Inc</RegisteredOrganization> <RegisteredOwner>365 Technologies Inc</RegisteredOwner> <TimeZone>Central Standard Time</TimeZone> </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"> <CopyProfile>true</CopyProfile> <ComputerName></ComputerName> <OEMName></OEMName> <RegisteredOrganization>365Technologies</RegisteredOrganization> <RegisteredOwner>365Technologies</RegisteredOwner> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <cpiWDS Deployment Fails on OOBE unattend file every time :eek:fflineImage cpi:source="wim:e:/esd/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

    :)
     
    PrairieSailor, May 4, 2021 at 9:27 AM
    #1

  2. WDS Deployment Fails on OOBE unattend file every time

    Hello,

    My first post, but follow the site regularly! I am trying for the 1st time, to figure out WDS to deploy a customized W10 image. I have tried many, many times, and just can not get the unattend.xml file to work. I keep getting an error about "microsoft-shell-setup".

    I have validated the XML file repeatedly in System Image Manager, and it always passes. Nevertheless I keep removing things to try to narrow down the problem, but keeps failing every time. And of course the whole deployment process takes forever each time...so it's getting frustrating. I have included my current version of the file, if someone has thoughts about a possible cause.

    <?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>
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <ProtectYourPC>1</ProtectYourPC>
    <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
    </OOBE>
    <UserAccounts>
    <LocalAccounts>
    <LocalAccount wcm:action="add">
    <Password>
    <Value>UwAzAHIAdgAxAGMAMwAhADMANgA1ACEARAAzAHMAawAhAFAAYQBzAHMAdwBvAHIAZAA=</Value>
    <PlainText>false</PlainText>
    </Password>
    <Description>Veeam Admin User</Description>
    <DisplayName>Veeam Admin</DisplayName>
    <Group>Administrators</Group>
    <Name>VeeamAdmin</Name>
    </LocalAccount>
    </LocalAccounts>
    </UserAccounts>
    <RegisteredOrganization>365 Technologies Inc</RegisteredOrganization>
    <RegisteredOwner>365 Technologies Inc</RegisteredOwner>
    <TimeZone>Central Standard Time</TimeZone>
    </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">
    <CopyProfile>true</CopyProfile>
    <ComputerName></ComputerName>
    <OEMName></OEMName>
    <RegisteredOrganization>365Technologies</RegisteredOrganization>
    <RegisteredOwner>365Technologies</RegisteredOwner>
    <TimeZone>Central Standard Time</TimeZone>
    </component>
    </settings>
    <cpiWDS Deployment Fails on OOBE unattend file every time :eek:fflineImage cpi:source="wim:e:/esd/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
     
    PrairieSailor, May 4, 2021 at 5:36 PM
    #2
  3. bro67 Win User
  4. Rose Cal Win User

    WDS Deployment Fails on OOBE unattend file every time

    WDS 2013 Deployment Error

    Hi Deejay,

    For in-depth assistance regarding your concern with
    WDS 2013 Deployment Error, we recommend posting your concern to
    TechNet Forums
    . In this way, you'll receive the best advice/troubleshooting steps from IT
    professionals who are more equipped in resolving this type of issue.

    Keep us posted if you need additional help.
     
Thema:

WDS Deployment Fails on OOBE unattend file every time

Loading...
  1. WDS Deployment Fails on OOBE unattend file every time - Similar Threads - WDS Deployment Fails

  2. OOBE Unattended install

    in Windows 10 Ask Insider
    OOBE Unattended install: I am trying to be able to quickly provision machines with windows pre-installed. I created the below answer file and named it unattend.xml. I put this on the root of a blank flash drive and booted, it did not grab the file. Did i miss something? <?xml version="1.0"...
  3. Creating deployment process with WDS/MDT.

    in Windows 10 Installation and Upgrade
    Creating deployment process with WDS/MDT.: Hi, I am a Help Desk Analyst and am being challenged with learning sysAdmin tasks. I've been tasked with setting up a deployment process, and I have been trying for a few weeks now to deploy an image with WDS/MDT. I've searched the internet hard trying to figure it out but...
  4. WDS - configuring the unattended install correctly

    in Windows 10 Installation and Upgrade
    WDS - configuring the unattended install correctly: Hi Everyone, I have been struggling trying to get this going now and I have been working on this for about a month now (on and off) with little progress. My goals for the unattended install are as follows: - not have to enter admin credentials to proceed with the install -...
  5. Import Capture WIM file at the time of deployment

    in Windows 10 Installation and Upgrade
    Import Capture WIM file at the time of deployment: Hi All, I need help with MDT. I want to create a task sequence which will take custom WIM at the time of installation. As I have different computer models and I don't want to import all WIM into the operating systems folder. I will make a shared folder where all of WIM's will...
  6. SCCM Deployment OOBE issue using xml File

    in Windows 10 Installation and Upgrade
    SCCM Deployment OOBE issue using xml File: Hi All I am rolling out windows 10 Enterprise using SCCM. The image that I have taken is from the msdn network and has a option of which Image i would like to use. (Please see pic labelled 1) [img] I am trying to create an automation so that it does not prompt me for...
  7. Unattend File

    in Windows 10 Installation and Upgrade
    Unattend File: Hi, I'm using WDS with Unattend File to deploy Win 10 to my VMs. It works fine, but the problem is, after the installation, the VM restarts and then boots from PXE again. (Basically, it's an infinite loop of Win 10 Installation because of the restart). What options do I have...
  8. unable to login after a win10 1803 MDT/WDS deployment

    in Windows 10 Installation and Upgrade
    unable to login after a win10 1803 MDT/WDS deployment: I was able to create and deploy a win10 1803 image containing a number of software packages, the deployment ends with no errors, it joins a domain. Everything worked fine with the first set of computers. However it is not working right for some other computers which have...
  9. Cant get computer to join domain with unattended file in WDS

    in Windows 10 Network and Sharing
    Cant get computer to join domain with unattended file in WDS: Hello, Recently, I have implemented WDS within my workplace to get away from Configuration Manager (As crazy as this might sounds), the reason being is to help streamline and reduce the time it takes to image a single machine and also to decrease the amount of post...
  10. Cant get computer to join domain with unattended file in WDS

    in Windows 10 Installation and Upgrade
    Cant get computer to join domain with unattended file in WDS: Hello, Recently, I have implemented WDS within my workplace to get away from Configuration Manager (As crazy as this might sounds), the reason being is to help streamline and reduce the time it takes to image a single machine and also to decrease the amount of post...