/build/static/layout/Breadcrumb_cap_w.png

Error during Windows Setup: Windows cannot locate the disk and partition specified in the unattend answer file's setting. ...

I didn't change anything in relation to this image, though I did recache the drivers today while attempting to build a new KBE. The answer file still looks the same. Here is the error I am getting. Though I am not sure if something happened with the drivers. 

In our Samba share all of the drivers still look to be there.

 9k=

Here is the answer file:

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <settings pass="windowsPE">

    <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <UseConfigurationSet>true</UseConfigurationSet>

      <UserData>

        <AcceptEula>true</AcceptEula>

        <FullName>Donuts Inc</FullName>

        <Organization>Donuts Inc</Organization>

      </UserData>

      <ImageInstall>

        <OSImage>

          <InstallFrom>

            <MetaData>

              <Key>/IMAGE/Name</Key>

              <Value>Windows 10 Enterprise</Value>

            </MetaData>

          </InstallFrom>

          <InstallToAvailablePartition>true</InstallToAvailablePartition>

        </OSImage>

      </ImageInstall>

    </component>

    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <UILanguage>en-US</UILanguage>

      <SetupUILanguage>

        <UILanguage>en-US</UILanguage>

      </SetupUILanguage>

      <InputLocale>en-us</InputLocale>

      <SystemLocale>en-us</SystemLocale>

      <UserLocale>en-us</UserLocale>

    </component>

  </settings>

  <settings pass="specialize">

    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <RegisteredOwner>Donuts Inc</RegisteredOwner>

      <RegisteredOrganization>Donuts Inc</RegisteredOrganization>

      <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>

      <TimeZone>Eastern Standard Time</TimeZone>

      <AutoLogon>

        <Enabled>true</Enabled>

        <Username>Admin</Username>

        <Password>

          <PlainText>true</PlainText>

          <Value>Password</Value>

        </Password>

        <LogonCount>1</LogonCount>

      </AutoLogon>

      <ComputerName>*</ComputerName>

    </component>

    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <Identification>

        <JoinWorkgroup>WORKGROUP</JoinWorkgroup>

      </Identification>

    </component>

    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <RunSynchronous>

        <RunSynchronousCommand wcm:action="add">

          <Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>

          <Description>Setting Network Location</Description>

          <Order>1</Order>

          <WillReboot>OnRequest</WillReboot>

        </RunSynchronousCommand>

        <RunSynchronousCommand wcm:action="add">

          <Path>reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f</Path>

          <Description>Hide First Logon Animation</Description>

          <Order>2</Order>

        </RunSynchronousCommand>

        <RunSynchronousCommand wcm:action="add">

          <Path>reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f</Path>

          <Description>Hide First Logon Animation</Description>

          <Order>3</Order>

        </RunSynchronousCommand>

      </RunSynchronous>

    </component>

  </settings>

  <settings pass="oobeSystem">

    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <OOBE>

        <HideEULAPage>true</HideEULAPage>

        <HideWirelessSetupInOOBE>True</HideWirelessSetupInOOBE>

        <NetworkLocation>Work</NetworkLocation>

        <SkipMachineOOBE>false</SkipMachineOOBE>

        <SkipUserOOBE>false</SkipUserOOBE>

        <ProtectYourPC>3</ProtectYourPC>

      </OOBE>

      <UserAccounts>

        <LocalAccounts>

          <LocalAccount wcm:action="add">

            <Name>Admin</Name>

            <Group>Administrators</Group>

            <Password>

              <Value>Password</Value>

              <PlainText>true</PlainText>

            </Password>

          </LocalAccount>

        </LocalAccounts>

      </UserAccounts>

    </component>

    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">

      <InputLocale>en-us</InputLocale>

      <SystemLocale>en-us</SystemLocale>

      <UILanguage>en-us</UILanguage>

      <UserLocale>en-us</UserLocale>

    </component>

  </settings>

</unattend>



2 Comments   [ + ] Show comments
  • Does your target device have more than one disk? - Hobbsy 3 years ago
    • Turns out this was the issue. I was under the impression multiple things weren't working, but it was just a couple devices with multiple hdds. Sorry! Thank you for the comment, it did lead me to verify. - ISEKOLD 3 years ago
  • It does not. It seems like it will work on newer devices, but it is not working on older devices. This device specifically was an older Dell all in one.

    If I contact support, are they going to ask me to update the appliance before doing anything else? - ISEKOLD 3 years ago

Answers (1)

Posted by: Channeler 3 years ago
Red Belt
0
Is this a custom XML Answer file or 100% wizard generated?

The Windows Setup Wizard is not able to find your hardrive.

If your disk partitioning tasks are working fine (PRE INSTALL), it means the KBE is able to see HDD.

You might want to use an updated version of the ISO (check Microsoft's volume license portal).
You might want to delete everything from \\SDA-IP\drivers\windows_10_x64\    and recache all drivers.
You might want to get into the BIOS, and switch the SATA Mode from RAID to AHCI.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ