I have a vhdx image of a windows installation with UEFI partition. When i try to boot it on a hyper-v, it goes to system recovery mode all the time. When i try to disable secure boot option from hyper-v, it comes up properly.

I tried the same procedure with windows 8 and it works fine. what might be the reason for it? Is there any workaround so that I can boot it with secure boot enabled?

  • What generation is the VM? See these references for bootloader problems : article 1 and thread 2. – harrymc Aug 1 '16 at 17:34
  • Hyper-V Manager - Microsoft Corporation - Version: 10.0.10586.0 – DTdev Aug 2 '16 at 3:57
  • I mean if they are generation 1 or 2 (see this for the difference). – harrymc Aug 2 '16 at 6:13
  • Windows 10 has UEFI partition. I am using generation 2 in hyperV (I think it is necessary for UEFI based partition). – DTdev Aug 2 '16 at 6:26
  • 1
    @Durgesh If this weren't a VM, I'd say that your HD doesn't have a GPT defined or EFI to see the bootloader for what to boot to via UEFI, & you have Windows installed on the disk with a MBR type of setup. Maybe enabling the Secure Boot feature of UEFI takes it to recovery so you can create GPT, etc. so it knows what to do. Otherwise, disable Secure Boot and it is booting to the MBR rather than using some UEFI feature/option for where to boot.You may already know all this but I thought I'd at least drop you a comment and mention the obvious--not too sure about VMs & Secure Boot myself though. – Pimp Juice IT Aug 6 '16 at 1:11

My understanding is that Windows 10 & Windows 2012 R2 support Generation 1 (same as previous versions of Hyper-V) and Generation 2 (new functionality) virtual machines.

Generation 2 is required for: - Booting from SCSI HDD & DVDs - Secure Boot - UEFI (Unified Extensible Firmware Interface) firmware support

Guest OS's supported under Gen 2 are: - Windows Server 2012 R2 - Windows Server 2012 - 64-bit versions of Windows 8, 8.1 & 10 (64-bit-only UEFI firmware)

The firmware only starts the bootloader when its signature has been signed by a trusted authority that is registered in the UEFI database.

| improve this answer | |
  • I understand that. My doubt is - in what case VHDX may fail only for Win10 UEFI but not for Win8 UEFI? And how can I get and debug memory for the same? is there any way that i can check the failure dump of Vhdx? – DTdev Aug 4 '16 at 8:52
  • @Durgesh Does your computer support Secure Boot? – juniorRubyist Aug 6 '16 at 23:57
  • It is HyperV. It has option to enable or disable secure boot. – DTdev Aug 12 '16 at 10:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.