Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows » How to Fix Boot Failed UEFI SCSI Device on HyperV
  • https   blogs images.forbes.com jasonevangelho files 2018 06 windows 7 2018 edition 1200x676 1
    Windows deployment cannot continue, the operating system is missing via MDT deployment Windows Server
  • sdfgh
    Get a list of installed applications on Windows Scripts
  • dfefeq
    Error 740: Elevated permissions are required to run DISM Windows Server
  • sdgfdhx
    MDT Warning: Unable to set working directory, the application returned an unexpected code 2 Windows Server
  • Bulk operations in Azure AD
    Perform Bulk User Operations in Azure AD AWS/Azure/OpenShift
  • File Share in Windows
    Create Folders and Enable File sharing on Windows Windows Server
  • How to create EC2 instance using Ansible
    How to launch an EC2 instance AWS/Azure/OpenShift
  • Enhancing Proactive Monitoring with Veeam ONE
    Enhanced Proactive Monitoring with Veeam ONE Backup

How to Fix Boot Failed UEFI SCSI Device on HyperV

Posted on 17/11/202219/02/2025 Temitope Odemo By Temitope Odemo No Comments on How to Fix Boot Failed UEFI SCSI Device on HyperV
Fix Boot Failed UEFI SCSI Device on HyperV

While setting up your Windows 2016 Server on Hyper-V you may have selected Generation 2 simply because you need features like Secure Boot, SCSI boot, TPM, and PXE boot but this selection can also lead to another issue of boot failure. In this guide, I will show you how to quickly fix the “Fix UEFI SCSI Device Boot Failure on HyperV on Windows Server when installing Windows Server 2016. Please see Initialize and format a virtual disk: How to add and remove a new virtual disk from a VM on VMware Workstation.

The UEFI SCSI means that the system is using the UEFI firmware interface for the boot process, and the storage devices, such as hard drives are connected using the SCSI protocol.

Check this if you want to know How to fix “This PC Can’t Run Windows 11” error on Hyper V and how to enable Secure Boot on PC to install Windows 11. Below is a YouTube video on how to Fix the Boot Failed UEFI SCSI Device on HyperV

Generation 2 VM Selection

The image below shows Generation 2 is selected. Please see these related articles: Generation 2 VM: How to set up a Hyper-V Virtual Machine through PXE boot, Enable HyperV on Windows: How to install Windows 11 on HyperV,

boot

Why was the error “Boot Failed UEFI SCSI Device” prompted?

Once you launch the Virtual Machine and you do not press any Key immediately. It will not boot from the source you configured.

boot2

Below is what will show next. Simply because you did not press any key on time and this will affect the installation from proceeding.

boot3

You may want to see Hyper-V Server Core Mode: How to install free Hyper-V Server on a VMware Workstation, how to fix VMware vCenter converter standalone started but not running.

Fix the “Boot Failed UEFI SCSI Device” Error

To get past this above error you need to hold down any key as you start up the virtual machine. You will notice it at the top of the screen. It says “Press any key to boot from CD or DVD”.

The issue is that it does not wait for you to press a key when it gets to this stage. Rather make sure you have a key held down before it shows this message.

 Once that is done, you will see the Windows Boot Manager prompt allowing you to boot to the setup by just hitting the Enter key.
boot4

After this is done you will get a successful boot to the Windows Setup. Please see An error occurred while attempting to connect to the server.

boot5

Your Windows Server 2016 will be installed successfully.

boot6

Please see how to fix Error –“ kinit: Malformed representation of principal when parsing name”. And how to Hide Windows Notification Center.

FAQs

Is there a way to change the boot order for UEFI SCSI devices in Hyper-V?

Yes, please access the virtual machine settings in Hyper-V Manager and navigate to the Boot Order section. Adjust the boot order to prioritize the UEFI SCSI device over other boot options. This ensures that the virtual machine attempts to boot from the correct SCSI device.

How can I troubleshoot corrupted boot files causing the UEFI SCSI boot failure?

Use installation or recovery media to access the UEFI command prompt. From there, run commands such as bootrec /RebuildBcd or sfc /scannow to repair potential issues with boot files.

How do I check and update the UEFI firmware on my Hyper-V virtual machine?

Ensure that your virtual machine’s UEFI firmware is up-to-date. Access the Hyper-V manager, select the virtual machine, go to Settings, and navigate to the Firmware section. Check for firmware updates and apply them to address potential compatibility issues.

Why is my UEFI SCSI device failing to boot on Hyper-V?

The UEFI SCSI boot failure on Hyper-V can occur due to various reasons, such as misconfigured settings, corrupt boot files, or issues with the virtual machine configuration. Identifying the specific cause is crucial for finding an effective solution

I hope you found this blog post on how to Fix Boot Failed UEFI SCSI Device on HyperV helpful. In case you have any questions do not hesitate to ask in the comment section.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Pocket (Opens in new window) Pocket
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization, Windows, Windows Server Tags:Boot Image, Hyper V, Hyper-V, hyperV, Hypervisor, Microsoft Windows, UEFI, Windows 10, Windows 11, Windows Server 2016

Post navigation

Previous Post: Enable vTPM and BitLocker HyperV VM: Fix the device that cannot use a TPM module
Next Post: Kerberos Delegation: A Comprehensive Guide

Related Posts

  • screenshot 2020 03 14 at 10.13.38
    How to Hide the Action Center Taskbar Icon In Windows 10 Windows
  • Screenshot 2020 12 06 at 17.01.38
    Start Print Spooler Service: How to fix Print Spooler Service not running Windows
  • Ping 4
    Perform continuous ping on OSes and network Appliances Mac
  • task manager not responding thumbnail
    Process Explorer: Replace built-in Task Manager Windows Server
  • Microsoft BitLocker Administration and Monitoring
    How to deploy MBAM for BitLocker Administration Windows Server
  • SysInternals
    How to use the Process Explorer from SysInternals Tools Windows Server

More Related Articles

screenshot 2020 03 14 at 10.13.38 How to Hide the Action Center Taskbar Icon In Windows 10 Windows
Screenshot 2020 12 06 at 17.01.38 Start Print Spooler Service: How to fix Print Spooler Service not running Windows
Ping 4 Perform continuous ping on OSes and network Appliances Mac
task manager not responding thumbnail Process Explorer: Replace built-in Task Manager Windows Server
Microsoft BitLocker Administration and Monitoring How to deploy MBAM for BitLocker Administration Windows Server
SysInternals How to use the Process Explorer from SysInternals Tools Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • https   blogs images.forbes.com jasonevangelho files 2018 06 windows 7 2018 edition 1200x676 1
    Windows deployment cannot continue, the operating system is missing via MDT deployment Windows Server
  • sdfgh
    Get a list of installed applications on Windows Scripts
  • dfefeq
    Error 740: Elevated permissions are required to run DISM Windows Server
  • sdgfdhx
    MDT Warning: Unable to set working directory, the application returned an unexpected code 2 Windows Server
  • Bulk operations in Azure AD
    Perform Bulk User Operations in Azure AD AWS/Azure/OpenShift
  • File Share in Windows
    Create Folders and Enable File sharing on Windows Windows Server
  • How to create EC2 instance using Ansible
    How to launch an EC2 instance AWS/Azure/OpenShift
  • Enhancing Proactive Monitoring with Veeam ONE
    Enhanced Proactive Monitoring with Veeam ONE Backup

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,832 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.