There is some confusion in the way NTLite handles disk layouts, mostly because of Windows Setup's own limitations in regards to extended partitions. Extended partitions can only expand to the disk's end, but with
no other partitions in the way.
1. The default layout assigns Windows partition as #3, with size
100GB. Recovery partition as #4, with size 700MB.
Unless you own a tiny NVME drive, everyone has a much larger system disk. This layout design leaves a gaping hole with everything after the Recovery partition as unassigned, empty space. You cannot expand Windows to the right, because it's trapped in middle, right before Recovery. If you knew the target disk's exact size, then you could replace the default 100000MB size with a proper number.
2. When you click on the disk wizard's "double arrow" icon for Windows, NTLite switches Recovery partition as #3, and Windows partition as #4.
This is more ideal (actually not, but we'll get there in a moment). Windows as the last partition can extend to the rest of the disk. What's the problem? In this layout, to allow Windows to expand, Recovery is moved ahead of Windows and no longer has the option to resize itself.
To resize Recovery (if required), would require a disk re-partitioning tool to shift Windows "to the right", and expand Recovery into the cleared space. Presuming Recovery is sized large enough, ~700 MB, then we might not ever encounter this problem.
For your scenario, you have existing volumes which you want to preserve. I would never automate the disk layout for these reasons:
1. By default, NTLite is wiping the disk layout from the install drive. Not what you wanted.
Code:
<WillWipeDisk>true</WillWipeDisk>
2. Extended partitions (handled by Setup) can only expand, when there are no existing partitions blocking its path. Unless your install is taking over the empty back end of a disk, this isn't going to work.
The only way to safely automate disk layout on a dual-boot situation is if you owned multiple disks, and each disk is a separate copy of Windows. With a single disk config, your chances for error are very high and will lead to data loss.
Even if your other volumes are data only, it's still risky.
