If I create a generation 1 VM I can native boot the vhdx by adding bcd entry. If I make a generation 2 VM it fails with "a required device isn't connected...0xc0000225". Pressing f8 for "Startup Settings" gives "The application or operating system couldn't be loaded because a required file is missing. File \Windows\system32\winload.efi. Error code 0xc0000225"
This is my BCD entry
and the Hyper-V definition (I've tried with and without secure boot, changing the boot order and removing the separate pagefile drive. It always works on Hyper-V will never boot on native boot.
Windows Boot Loader
device vhd=[D:]\Hyper-V\Windows-vm3\Virtual Hard Disks\Windows-vm3.vhdx
osdevice vhd=[D:]\Hyper-V\Windows-vm3\Virtual Hard Disks\Windows-vm3.vhdx
Conversely if I install windows and turn off the VM before the first reboot I can boot it natively but Hyper-V will not boot (again complains of missing bootloader). The bootloader can't be repaired by bootrec, no valid windows installations are found.
Windows versions I'm using are 10 Pro build 10240 for host, build 10586 or 10240 for guest.
Does anyone know if it is possible to native boot a generation 2 VM vhdx and boot it through Hyper-V, the same as you can with generation 1?