That is interesting, although I don't know if that matters here. the "505 MB Recovery Partition" at the end is missing.the partition "System Reserved 50 MB NTFS Primary Partition" at the beginning is missing, instead I have a 260 MB (in this screenshot 100 MB) EFI System Partition" there.I noticed that in the VHD-image created by Rufus basically So no matter if I use a VHD or a VHDX-file the partitions look like "Disk 0" on this screenshot, that I found on the Internet: The same error as described in the first post in step 4 shows up. And then thanks to Steve2926 of his idea of using a VHDX instead of a VHD. Midas, thank you for your ideas on this topic. I have had nothing but endless grief trying to juggle those restrictions under Windows. This absolutely won't work with MBR style drives. I have gone the VHDX path before, since my go to recipe for installing Windows 7 in a virtual disk apparently didn't work any longer with 10 - and, at first, everybody just said it couldn't even be done.īear in mind that, should you decide to try it, you'll be restricted to VHDX under mandatory GPT formatted drives and the new UEFI booting scheme That " System Reserved" partition is in fact the EFI boot store and it becomes active only after Ventoy successfully boots the VHD - prior to that the main boot store is Ventoy's own " VTOYEFI" partition present in the physical boot drive (also hidden). I have a hunch that Steve2926 has hit the target in his post above where he points that BCD might be the culprit here.Į.g., here's the internal disk layout of my Windows 10 VHD, automagically created with VirtualBox under Linux, which boots fine placed on a MBR disk.
0 kommentar(er)
