I went to install a Debian instance on Windows Hyper-V client in Windows 10. However, when I attempted to start the VM, it would not boot from the cd. Eventually the Hyper-V BIOS gave me a failure to start screen that listed boot devices and their status. The status of the SCSI-DVD device said: "The unsigned image's hash is not allowed (DB)".

Finding information about this error on the internet is proving to be difficult.

up vote 151 down vote accepted

This error is a consequence of having Secure Boot enabled on the VM. Secure Boot prevents the system from getting hijacked at boot time by only allowing specifically authorized boot images to load. In Hyper-V client, the list is rather short.

To disable Secure Boot, power off the VM and then open the VM settings. Under Secure Boot, uncheck the box "Enable Secure Boot" and then click "OK". This will allow the VM to boot the "unauthorized" CD image.

  • Thanks, really odd that this failed with ISO images directly from MSDN. But that's M$ for ya. – Rob Jun 30 '16 at 19:08
  • Perfect answer thanks, I was wondering what it was.Can we reactivate it after the installation ? – Raphael Teubner Dec 4 '16 at 18:19
  • Secure Boot is enabled or disabled on a per-VM basis. As long as the installed OS has a recognized boot image, you can re-enable Secure Boot after the installation. – Thomas Dec 5 '16 at 1:01
  • 3
    I chose a different template: "Microsoft UEFI Certificate Authority". Worked like charm. – Itai Bar-Haim Feb 7 at 8:16
  • Works perfectly! – Damian Aug 31 at 9:33

Disable Secure Boot option in the VM Settings:

enter image description here

This feature is enabled by default on Gen2 VMs and requires your ISO image boot loader to be signed by Microsoft Authenticode certificate. Any custom images with modified boot loader will fail to boot. There is also "Microsoft UEFI Certificate Authority" template for Linux images.

I was looking into this issue and came upon this thread. I found that changing the option to utilize the "Microsoft UEFI Certificate Authority" resolved my problem using Ubuntu Server 17.x.

Set-VMFirmware -VM $VM -FirstBootDevice $(Get-VMDvdDrive -VM $VM) -EnableSecureBoot On -SecureBootTemplate MicrosoftUEFICertificateAuthority
  • how do you set the value of $VM? – code_monk Nov 24 '17 at 16:41
  • 1
    You can also set this in the UI (show in Makhail's answer) by selecting "Microsoft UEFI Certificate Authority" from the Template dropdown on the Security settings screen. – devrelm Dec 11 '17 at 16:04

This happened to me too while trying to install Windows server 2008 R2 on windows 10 hyper-v. It also said DHCP failed and no bootable OS was found. Unchecking the Secure boot option didn't resolve the issue. However, creating a new Gen 1 VM did.

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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