Weirdness with K2000/Diskpart/Windows 10
Working on creating a Windows 10 image. I'm pretty close, but during the OS install I occasionally get this error -
"The partition selected for installtion (1) does not exist in disk 0. Make sure the unattend anwer file's <ImageInstall> setting references a valid partition on this computer, and then restart the installation"
Weirdly enough I don't get it every time, and sometimes I can retry and I don't get the error. I have a preinstallation task that formats the disk and creates Partition 1, so I'm not too sure why this comes up intermittently. Here's the Diskpart script -
select disk 0
clean
create partition primary
select partition 1
active
assign letter=c
exit
The unattend.xml file just uses the InstallToAvailablePartition command so not sure what the issue is. I've tried specifying the Disk/Partition and it didn't make a difference...still get that error maybe 25% of the time. Just figured I'd see if anybody has any ideas.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
TheAustinDave
8 years ago
Hi,
The capture of a system OS that is updated from say Windows 7 to 10, or even within some of the Windows 10 OS versions is regarded as an upgrade and sysprep will cause issues. If you look at the windows\system32\sysprep\panther\setuperr.log file there will most likely be items listed there.
The fix is to obtain a WIN10 OS and install it fresh to sysprep and use for the deployment.
Posted by:
SMal.tmcc
8 years ago
I deleted my other answer, I reread your question closer and those answer file entries are used in a scripted install not a sysprep image. Can you post your answer file (unattend.xml)
Posted by:
tech07
8 years ago
Well, I figured this out if anybody is curious. The laptops have DDPE installed on them and it looks like you're not able to partition a drive until you uninstall it. If you try to partition a drive while it's still active it won't work at all. Now to figure out a way to automate this in my scripted install...