Solving the “Boot Failed. EFI SCSI Device” error when installing Windows 2012 Server on 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:

Boot Failed. EFI SCSI Device.


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.


32 thoughts on “Solving the “Boot Failed. EFI SCSI Device” error when installing Windows 2012 Server on Hyper-V

Add yours

  1. Unchecking Enable Secure Boot in the Settings > Firmware section did the job for me. I did not have a problem with this when loading Server 2012R2 but did when trying to install Win7, Win8 and Server 2008R2.


    1. Also forgot to pay attention to GEN1 vs GEN2 settings. Only Server 2012 or Win8 x64 can be created with GEN2. Installing Win7 x64 or Server 2008R2 as GEN2 will hang at “Starting Windows”.


  2. Can you mount an ISO file to boot from using Generation 2? My understanding is Generation 2 is more secure. I’d like to keep it that way.


  3. very helpful, if you are doing this remotely, you may have to wait for it to fail, then when it says hit any key to retry boot sequence, hit any key and hold it. Then it works.

    Liked by 1 person

  4. This was tremendous help to me. I was baffled and frustrated. Internet is full of nonsense, and a lot of people who think they’re technical post the most ridiculous suggestions out there. Yes, this did work for a Windows 2019 install like a charm. Thank you!

    Liked by 1 person

Leave a Reply to Prem Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a website or blog at

Up ↑

%d bloggers like this: