boot failed efi scsi device hyper v

I’ve installed Windows 2012 server on a few Hyper-V images in the past but ran into an error that looked unfamiliar. I created my Hyper-V machine, configured it with a dynamic hard drive, added a DVD and mounted the Windows Server 2012 ISO making sure the DVD drive was top of the boot order and started it up.

I was then presented with a black screen an the error message:

Here’s the long winded explanation from the Senior Program Manager of the Hyper-V team (John Howard).

The short answer: It’s because the virtual machine was created as a Generation 2 machine rather than Generation 1.

To get past this error simply hold down a key as you start up the virtual machine. You’ll notice at the top of the error screen it says “Press any key to boot from CD or DVD…..” the issue is that it doesn’t wait for you to press a key, just make sure you have a key held down when it gets to this point and you should see the Windows Boot Manager prompt allowing you to boot to the DVD image.

Then hey presto you’ll get a successful boot to DVD and the Windows Setup window you expected.

Knowledge is not what you can remember, but what you cannot forget.

When installing an Operating System other than Windows Server 2012 of Windows 8, you could see the warning:

Boot failed. EFI SCSI Device. Failed Secure Boot Verification

This is caused by the type of the virtual machine you are using. When you create a Virtual Machine in Hyper-V, you should select “Generation 1”.

Instead of changing to a Generation 1 virtual machine, you can also disable Secure Boot under the Virtual Machine settings. Make sure that the Virtual Machine is turned off.

After turning off the option “Enable Secure Boot”, or creating a new Generation 1 VM, you should be able to start the ISO without any warnings or errors.

About Nick van Vuren

My name is Nick van Vuren and i’m currently working as a System Engineer at IS Group in the Netherlands. I have been working here since 2009. We’ve started this blog to share our knowledge with other System Engineers. For any questions, you can contact me at nick(at)serverknowledge.net

4 thoughts on “ Boot failed. EFI SCSI Device. Failed Secure Boot Verification ”

Make sure that .iso file has a bootable image file.
you can use poweriso to check if it’s bootable or not.

Still get the same error.

Gen 2
Secure boot is off.
Guest OS is Win 10 Ent LTSB

Muchas Gracias, a veces algo tan sencillo puede ser muy útil en el momento adecuado. Y todo es sencillo hasta que se tiene el conocimiento

Introduction

There are quite a few different errors that you may run into when using Hyper-V.

In this blog post, I explain the following error related to secure boot in Hyper-V, and how to solve it:

Boot Failed. EFI SCSI Device. Failed Secure Boot Verification

Description of the error

The reason why you are receiving this error is that a generation 2 machine in Hyper-V by default runs Secure Boot.

How to solve the error

There are two ways to solve the error.

These solutions are explained below.

Solution 1 – Create a generation 1 virtual machine in Hyper-V

If you want to run an older operating system as a guest, select Generation 1 when creating the Virtual Machine:

Solution 2 – Disable Secure Boot

The second solution is to disable Secure Boot under the VM settings for a Generation 2 Virtual Machine.

Disable Secure Boot for a Hyper-V machine using the Hyper-V Manager

Open Hyper-V Manager -> Right-Click -> Press Settings

Go to the Security tab and uncheck Enable Secure Boot.

Disable Secure Boot for a Hyper-V machine using Powershell

An alternative to the Hyper-V Manager is Powershell.

Run the following command, replacing “VM1” with the name of your virtual machine.

Conclusion

When configuring virtual machines in Hyper-V, it is important that you understand the difference between the different generations and how the new security features work.

Did you find this article helpful? Please leave a comment below!