How to Fix Hyper-V Not Booting ISO on Windows 11: Complete Troubleshooting Steps

Using Hyper-V to boot an ISO file on Windows 11 is a common way to run virtual machines for testing or development. However, sometimes the virtual machine may fail to boot from the ISO, causing frustration. Troubleshooting this issue requires a series of simple checks and adjustments.

This guide walks you through the basic to advanced steps to fix the problem of Hyper-V not booting an ISO on Windows 11. Each step is explained clearly to help even beginners understand the process.

By following these instructions carefully, you can identify the root cause and get your virtual machine running smoothly. Let’s get started with some initial quick notes.

Remember, patience and attention to detail are key when troubleshooting virtual machine issues.

Quick Note Before You Begin

Ensure Hyper-V is enabled: Hyper-V must be properly installed and enabled on your Windows 11 system. Without this, virtual machines won’t run.
Check the ISO file: The ISO image you want to boot must be intact and not corrupted. If the file is damaged, the VM won’t boot correctly.
Verify system requirements: Your PC must support virtualization technology (Intel VT-x or AMD-V) and have it enabled in BIOS/UEFI.
Confirm VM settings: The virtual machine should be configured to boot from the ISO file in the virtual DVD drive.

Step 1: Confirm Hyper-V is Enabled on Windows 11

Before anything else, make sure Hyper-V is turned on in your system. Without Hyper-V enabled, you won’t be able to run virtual machines.

Press Win + R to open the Run dialog.
Type optionalfeatures.exe and press Enter.
In the Windows Features window, scroll down and find Hyper-V.
Make sure both Hyper-V Management Tools and Hyper-V Platform are checked.
Click OK and restart your computer if prompted.

Why this matters: Without enabling Hyper-V, your system cannot create or run virtual machines. This step ensures the necessary components are active.

Step 2: Verify Virtualization is Enabled in BIOS/UEFI

Hyper-V requires hardware virtualization to be enabled at the BIOS or UEFI level. Most modern PCs support it, but it might be turned off by default.

Restart your PC and enter BIOS/UEFI settings (usually by pressing Del, F2, or Esc during boot).
Look for settings related to Virtualization Technology, Intel VT-x, or AMD-V.
Enable the virtualization option if it is disabled.
Save changes and exit BIOS/UEFI.

Why this matters: Hyper-V depends on virtualization hardware support. If disabled, the VM cannot access the CPU features needed to boot the ISO.

Step 3: Check the ISO File Integrity

Sometimes the ISO file itself might be corrupted or incomplete, which prevents the virtual machine from booting.

Make sure you have downloaded the ISO from a reliable source.
Try opening the ISO with a file archiver tool (like 7-Zip) to see if the contents are accessible.
If you have a checksum (MD5, SHA1, SHA256) for the ISO, verify the file matches to ensure it’s not corrupted.
If the ISO is damaged, download a fresh copy.

Why this matters: A damaged ISO will cause the boot process to fail, so verifying file integrity is crucial.

Step 4: Correctly Attach the ISO to the Virtual Machine

Ensure that the ISO file is properly linked to your VM’s virtual DVD drive so that it boots from the ISO image instead of the virtual hard disk.

Open Hyper-V Manager.
Select your virtual machine and click Settings.
In the left pane, click on DVD Drive under Hardware.
On the right, select Image file and browse to your ISO file location.
Click Apply and then OK.

Why this matters: Without correctly attaching the ISO, the VM will not boot from it and may try to boot from an empty or incorrect device.

Step 5: Set the Boot Order to Boot from DVD Drive

The virtual machine must be instructed to boot from the DVD drive before the hard disk. This ensures it boots the ISO.

In Hyper-V Manager, select your VM and click Settings.
Go to Firmware in the Hardware list.
In the Boot Order section, make sure DVD Drive is listed above the Hard Drive.
Use the arrows to adjust the order if needed.
Click Apply and then OK.

Why this matters: The VM checks the devices in the boot order sequence. If the DVD drive is lower than the hard drive, it will skip booting the ISO.

Step 6: Use Generation 1 Virtual Machine if Needed

Hyper-V supports two VM generations: Generation 1 and Generation 2. Some ISO images, especially older ones, may not boot correctly on Generation 2 VMs due to UEFI requirements.

When creating a new VM, choose Generation 1 instead of Generation 2.
Attach your ISO and try booting again.

Why this matters: Generation 2 VMs use UEFI firmware, which some ISOs may not support. Generation 1 uses legacy BIOS, which is more compatible with older ISOs.

Step 7: Disable Secure Boot for Generation 2 VMs

If you are using a Generation 2 VM, Secure Boot may prevent some ISOs from booting properly.

Open VM Settings in Hyper-V Manager.
Go to Security in the left pane.
Uncheck Enable Secure Boot.
Click Apply and OK.

Why this matters: Secure Boot restricts the software that can run during the boot process. Disabling it can allow unsigned or older bootloaders to work.

Step 8: Check Hyper-V Virtual Switch Configuration

Although networking isn’t directly related to booting from an ISO, misconfigured virtual switches can cause VM startup issues.

Open Hyper-V Manager and select Virtual Switch Manager from the right pane.
Create or select an existing virtual switch that is properly connected to your network adapter.
Assign the virtual switch to your VM’s network adapter in VM settings.

Why this matters: A disconnected or misconfigured network adapter sometimes causes the VM to hang during startup.

Step 9: Use PowerShell to Mount and Boot the ISO (Advanced)

If the GUI method doesn’t work, use PowerShell commands to attach the ISO and start the VM.

Set-VMDvdDrive -VMName "YourVMName" -Path "C:PathToYour.iso"
Start-VM -Name "YourVMName"

Why this matters: PowerShell gives more control and can help identify errors that the GUI might not show.

FAQs

Why does my VM say “No bootable device found”?

This usually means the VM cannot find a bootable disk or ISO. Check if the ISO is properly attached and boot order is correct.

Can I use any ISO file with Hyper-V?

Most standard ISO files work, but some may require Generation 1 or Generation 2 VM depending on the OS and boot firmware compatibility.

How do I check if virtualization is enabled on my PC?

Use Task Manager > Performance tab > CPU section. It will show if Virtualization is enabled or disabled.

Why is my ISO not recognized when attaching in Hyper-V?

Make sure the ISO file is not corrupted and is a valid bootable image. Also, check file permissions and path.

Can Secure Boot cause boot issues?

Yes, Secure Boot can block unsigned bootloaders. Disabling it in Generation 2 VM settings can help.

When Nothing Works

If you have tried all the steps above and Hyper-V still does not boot from the ISO, consider the following:

Update Windows and Hyper-V: Make sure your Windows 11 and Hyper-V components are fully updated.
Try another ISO: Test with a different ISO to rule out file-specific issues.
Check event logs: Open Event Viewer and look for Hyper-V or system errors during VM startup.
Use official Microsoft resources: Visit the Microsoft Hyper-V documentation and forums for more help.
Reinstall Hyper-V: Disable Hyper-V from Windows Features, reboot, then enable and reboot again.

Conclusion

Fixing the issue of Hyper-V not booting an ISO on Windows 11 involves a methodical approach starting from enabling Hyper-V and virtualization, verifying your ISO, and correctly configuring the VM settings. Simple steps like attaching the ISO properly and setting the boot order often resolve the problem.

For more complex cases, adjusting VM generation type and disabling Secure Boot can help. Always verify your system meets requirements and keep your software updated.

Following this detailed guide will help ensure your virtual machines boot from ISO files successfully on Windows 11 using Hyper-V.