Best Practices

Have tried for a week to successfully deploy a BIOS version of windows 10 2004 with a k2000. Have successfully captured and deployed previous versions of windows 10, bios and uefi. Can capture/depoly windows 10 2004 UEFI. The image has been captured from a physical sysprepped computer. The sysprep file was created with the 2004 ADK on a technician computer. Have been using the WIM image format.

The issue I'm having is that Microsoft changed the way that the recovery partition is partitioned, so there are 3 possible partitions to capture instead of the two available to capture on previous versions of windows. I've tried capturing 1, 2, and 3 partitions. Cannot get the BIOS image to reboot after imaging successfully. The image will successfully deploy, but not boot after imaging to do post-install tasks. 

Windows will grind for awhile, complain that it can't start,  thinks a driver is needed and that a restart will fix the issue. Over and over. The drivers for the hardware are in the feed and are installed properly if deploying any other BIOS version of windows I have previously captured. If I use a windows 10 1909 image captured in the same time frame, no problem. The procedure that I followed with other BIOS versions of windows was to capture both partitions. 

Can someone advise me as to the partitions to capture along with a script to create the BIOS partitions for imaging? The script below from MS(https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions) does not work properly. As in after image is applied, computer reboots to do post-installation tasks, and windows wont boot as described above.

rem == CreatePartitions-BIOS.txt ==
rem == These commands are used with DiskPart to
rem    create three partitions
rem    for a BIOS/MBR-based computer.
rem    Adjust the partition sizes to fill the drive
rem    as necessary. ==
select disk 0
clean
rem == 1. System partition ======================
create partition primary size=100
format quick fs=ntfs label="System"
assign letter="S"
active
rem == 2. Windows partition =====================
rem ==    a. Create the Windows partition =======
create partition primary
rem ==    b. Create space for the recovery tools  
rem       ** Update this size to match the size of
rem          the recovery tools (winre.wim)
rem          plus some free space.
shrink minimum=650
rem ==    c. Prepare the Windows partition ====== 
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 3. Recovery tools partition ==============
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id=27
list volume
exit

Thank your for your consideration as I am stumped.

As a public institution, we have to use older equipment that does not support UEFI boot   very well. That is why we have a bios image option. Most (98%+) of our deployments are UEFI, wish they all were.