Need help?

Our experts will login to your server within 30 minutes to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price per month.

Boot failed EFI SCSI device Hyper-v – How we fix it!

Are you stuck with boot failed EFI SCSI device error in Hyper-V? We can help you fix it.

The common reason for the error is because of the Boot Architecture in Hyper-V

At Bobcares, we often receive requests to fix Hyper V errors as part of Server Management Services.

Today, let’s see how our Support Engineers resolve boot failed EFI SCSI device error.


Cause for boot failed EFI SCSI device in Hyper-V

One of the major causes of the error is that servers are not created using the correct generation.

Microsoft introduced two Hyper-V Boot Architectures setup. One for BIOS and another for UEFI. Generation 1 supports BIOS whereas Generation 2 supports UEFI.

So when creating a server with an older OS version we need to create it in Generation 1 since it is for BIOS-based.

The sample error looks like:

boot failed efi scsi device hyper-v

Let’s discuss how our Support Engineers create Generation 1 servers. Also, let’s discuss alternative methods to resolve the error.


How we fix boot failed EFI SCSI device in Hyper-V

Recently one of our customers approached us saying that they were unable to boot the server and were getting this error. Let’s see how our Support Engineers fix it for our customer.


Create a Generation 1 Hyper-V

Now let’s see how our Support Engineers create Generation 1 servers in Hyper-V

1. Open Hyper-V Manager. Click on Hyper-V host and click on Virtual Machine.

2. Now a new window appears and then click Next. Select a location to store the Virtual Machine data.

3. In the Specify Generation, our Engineers select Generation 1 and click Next.

4. In Assign Memory we specify the memory. Now, in Configure Networking we select the Virtual Switch.

5. Then in Connect Virtual Hard disk, we select the required option and click Next.

6. Now the summary displays. We verify the details and finally, we click Finish.


Disable Secure boot

Another workaround to resolve the error without changing the Generation is to disable secure boot. Let’s discuss how our Support Engineers disable secure boot for a VM.

Initially, we open Hyper-V Manager. We select the virtual machine. Right-click on the VM and click on the setting.

Then we click on the Security tab. Uncheck Enable Secure Boot.

Thus it resolved the error when loading the Virtual Machine.


Booting from a DVD drive

Another reason for the error to occur is when trying to load from the DVD drive. Let’s discuss how our Support Engineers change the boot order to resolve the error.

So when ISO is mounted as a DVD drive we need to change the boot order at the startup.

To change it we right-click on the VM and select properties. We select the Firmware tab.

Then we move the DVD Drive to the top of the list. Thus starting the VM the OS loaded without any issue.


[Need assistance to fix Hyper-V error? – We can help you fix it]



In short, we have discussed the causes of the error boot failed EFI SCSI device. Also, we have discussed how our Support Engineers resolves the error for our customers.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.