Windows 10: Windows SIM autounattend.xml stuck on disk selection

This is driving me nuts. I'm sure it's a simple and stupid mistake fix, but I can't find it. I'm new to WSIM.First, here is my autounattend.xml with some obvious redactions ...<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="

:)

 

Windows 10 autounattend xml installation problem

Hi guys, I have a problem with autounattend XML install. Basically, I have a Windows image that is downloaded from MS and edited to skip all steps for setup. The windows boots and wipe the hard drive created partitions, select language, and created one admin account with the password. The image work when I test it on a laptop and everything seems fine. The image is not working on Virtual box or Hyper- V, when it's, starts on the parts that create partitions I received that error:
windows could not create a partition on disk 0 the error occurred while applaying the auto unnatednd asnwer file's < DiskConffiguration>Setting. Error code: 0x80042565 . The main issue is that I set up a TFTP server and crated WinPE to boot from the samba server where the image is so that I can boot it from the network. When I tested the image from the server it's finding the image and start the setup but I receive the same error with the creation of the partitions like on a virtual machine. With a flash drive, it works I don't know what might be the problem if someone has an idea?

 

Is it possible to select disk during autounattended setup?

Absolutely - just add another disk (see screenshot below), choose to wipe that disk, and partition the disk as you like. You would simply add a "CreatePartitions" and "ModifyPartitions" just as you did for the disk to which Windows is to be installed.

 

Windows 10 autounattend xml installation problem

Ok, that's a good start.

Your answer file is made for a Gen 2 Hyper-V. It won't work on Gen 1.

Verify the settings I have outlined in the image below:





NOTE: I have not looked at the answer file in detail. If you are still having difficulty, I'll look closer, but for now, time for sleep. It's 0500 here *Smile