Can you send a screenshot of the first part of your provisioning template that you use on this device i.e System migration -> post-OS, It might help me advise you as to what the issue might be . The unattend file should not have an effect unless you configure your disk and partitions using it.
According to me the problem isn’t located into the unattend file , it should work in bios legacy and UEFI mode.
First point : Is your image is a WIM image ?
Second point :
You have many things to change in your Template between a BIOS legacy system and an UEFI system
First of all you have to to convert your disk in GPT mode and create 3 kind of partitions. (see below an example of UEFI patition)
rem == CreatePartitions-UEFI.txt ==
rem == These commands are used with DiskPart to
rem for a UEFI/GPT-based PC.
rem Adjust the partition sizes to fill the drive
select disk 0
rem == 1. System partition =========================
create partition efi size=100
rem ** NOTE: For Advanced Format 4Kn drives,
rem change this value to size = 260 **
format quick fs=fat32 label="System"
rem == 2. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 3. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery image ===
rem ** NOTE: Update this size to match the size
rem of the recovery image **
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
After deploying your image you need to use the bcdboot.exe command that allowing your OS to be bootable. (See Below the action) In my example the S partition is the system location
Thanks for getting back to me, so are you running a script to partition the drive in the Pre-OS installation? is this just a batch file that you are running? My image is a .tbi file, that is what we currently use for all our computers. Could you share a picture of your Pre-OS installation provisioning tasks? Thanks again!
Do you still have the example template? I am running into the same problem as Hunter when trying to provision a Surface.We are using Surface 3 and Surface Pro 4.
Thank you for the template. I kind of figured it out myself, but eventhough thanks!