Hi there
@
tenjay
what I would do in this situation is to run both these systems as VHDX (Virtual hard drives) -- not Virtual machines - and then when you boot you will get a choice of which system to boot. You probably could manage with editing the boot menu but using Virtual hard disk drives IMO is the best way of keeping the two systems totally isolated from each other.
Needs a bit of work first but it's a great way of also having several Windows systems which you can test using "Real hardware.
Essentially clone both systems to VHDX files, clear the primary boot disk , create a winpe bootable usb device, copy the VHDX files to the relevant disks, attach to the winpe system and then create the boot entries. Then shutdown, remove the winpe device and re-boot. You'll now see a boot menu with your 2 systems. Just boot whichever one and all done !!!. You can also have several VHDX systems per disk -- all you need is that the VHDX files are big enough for your Windows install. Then they behave just like normal Windows systems. Advantage also is no overhead of any "HOST OS" either. Note these are NOT VM's but physical installations.
Good thing also about this is you do not need to enter BIOS to choose Boot disk !!!.
Example here -- I have an 80GB W11 system on a VHDX (I'm using it now) - and an internal 256GB SSD . As I only have 1 SSD on this laptop I have the 80GB VHDX file defined on it. I'm in the process of creating another 80GB VHDX to install the Windows 11 DEV system.
To create the VHDX files do it from Disk management (right mouse click on the W11 / W10 menu icon depending on the OS you are running. Choose VHDX rather than VHD at creation and choose allocate completely as a single file. You don't need HYPER-V or any VM software for this.
The Main Disk D is not used by the VHDX's in running the systems but the unallocated parts can be accessed via file explorer as normal - no mount needed.
Cheers
jimbo