Hyper-V: Generation 2 Virtual Machine compatibility error
I ran in to this problem the other day when trying to run Windows Server 2008 R2 in Hyper-V:
“Boot Failed. EFI SCSI Device. Failed Secure Boot Verification”
The reason for this was that I had created a Generation 2 Virtual Machines which uses Secure Boot which is supported in Windows 8, Windows Server 2012 and later.
So, remember that if you want to run an older operating system as a guest, select Generation 1 when creating the Virtual Machine:
Instead of changing to a Gen 1 VM, you can also simply disable Secure Boot under the VM settings.
Thanks to Armani for pointing that out.
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
- How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2 943,499 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 62,872 views
- Solution to OSD issue 80072ee7 28,872 views
- Powershell: Script to set Outlook 2010/2013 signature using information populated from Active Directory 30,388 views
- Guide: How to get PXE boot to work in Hyper-V 100,011 views
- Guide: How to force specific sites to always run in Compatibility View using Group Policy 136,079 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 63,071 views
- Hyper-V: Issue when starting virtual machine from downloaded ISO file 6,989 views
- Guide: Solving WDS issue with DHCP port conflict 10,683 views
- How to create a bootable Windows 8 USB using Diskpart 29,637 views