When a Hyper-V Windows 11 VM won't start, you're usually looking at one of five problems: the host doesn't have virtualization enabled in BIOS, the VM is Generation 1 instead of Generation 2, corrupted saved state is blocking startup, boot order is misconfigured, or there's a virtual switch mismatch. I've seen all of these dozens of times via remote support, and they're all fixable without rebuilding from scratch.

TL;DR

Hyper-V Windows 11 VM won't start? First, verify virtualization is enabled in Task Manager and BIOS. Second, confirm the VM is Generation 2 with Secure Boot and virtual TPM enabled. Third, delete any corrupted saved state. If the VM still won't boot, check boot order, ISO attachment, and host RAM. Most of these fixes take 5-30 minutes.

⏱️ 14 min read✅ 85% success rate📅 Updated June 2026

Key Takeaways

Windows 11 requires Generation 2 VMs with UEFI, Secure Boot, and virtual TPM
Host virtualization must be enabled in both Windows Task Manager and BIOS firmware
Corrupted saved state is a common blocker; Delete Saved State clears it immediately
Boot order, ISO attachment, and keyboard capture are frequent culprits in install scenarios
Virtual switch name mismatches cause startup failures after VM restore or host move

At a Glance

Difficulty: Easy to Intermediate
Time Required: 15-45 minutes
Success Rate: 85% of users fix this on first attempt

What Causes Hyper-V Windows 11 VM Won't Start?

There are five main reasons a Hyper-V Windows 11 VM won't boot. Understanding which one you're hitting makes the fix obvious.

Generation mismatch is the most common culprit. Windows 11 requires UEFI firmware, TPM 2.0, and Secure Boot. Hyper-V implements these only in Generation 2 VMs. If you created a Generation 1 VM and tried to install or run Windows 11 on it, it won't start because the hardware model doesn't support UEFI or TPM. Generation 1 is for older Windows versions like Windows 7 or Server 2008 R2.

Host virtualization disabled in BIOS is the second killer. Even if Hyper-V is installed on your Windows 11 host, if you haven't enabled Intel VT-x (or AMD-V for Ryzen) in BIOS, the CPU can't create virtual machines. This is a firmware-level setting, not a Windows setting. You have to reboot and enter BIOS to fix it.

Corrupted saved state happens after VM restore, move, or failed snapshots. When you restore a Hyper-V VM from backup or move it to another host, the saved state files (.bin and .vsv) sometimes become corrupted or point to network switches that no longer exist. The VM then hangs in "Saved" or "Saved-Critical" state and won't start.

Boot order and ISO attachment problems block fresh installations. If you're installing Windows 11 from ISO and the DVD drive isn't first in boot order, the VM boots to a hard drive that doesn't have an OS yet. Or the ISO isn't actually attached to the DVD drive. Or the VM doesn't capture your keypress to boot from the ISO, so it falls through to network boot (PXE) and hangs.

Virtual switch mismatch and resource constraints are less obvious but just as real. After a VM restore or move to a different Hyper-V host, the network adapter points to a virtual switch that doesn't exist on the new host. Or the host doesn't have enough free RAM to allocate to the VM, so Hyper-V fails the startup silently.

Hyper-V Windows 11 VM Won't Start: Quick Fix

Verify Host Virtualization Is Enabled Easy

Open Task Manager
Press Ctrl+Shift+Esc. If it doesn't open, right-click the taskbar and select Task Manager.
Navigate to Performance tab
Click the Performance tab at the top. On the left sidebar, click CPU.
Check Virtualisation status
In the CPU details pane on the right, you'll see a line that says Virtualisation. It should show Enabled. If it shows Disabled, your BIOS has virtualization turned off and you'll need to enter BIOS setup to enable it.
If disabled, enter BIOS and enable VT-x or AMD-V
Restart your PC. During boot, press F2, Delete, Esc, or F10 (varies by manufacturer). Look for a setting called Intel Virtualisation Technology, VT-x, AMD-V, or SVM Mode. Enable it and save changes.

Virtualization confirmed enabled. Your host can now run Hyper-V virtual machines.

Confirming Windows 11 VM Generation and Boot Configuration

This is where most Hyper-V Windows 11 VM won't start issues hide. Windows 11 won't even attempt to boot on a Generation 1 VM, so you need to verify your VM is actually Generation 2 and has the security features Windows 11 demands.

Verify VM Is Generation 2 with Secure Boot and TPM Easy

Open Hyper-V Manager
Press Windows+R, type virtmgmt.msc, and press Enter. Hyper-V Manager opens.
Right-click the VM and open Settings
Find your Windows 11 VM in the list, right-click it, and select Settings. Do not start the VM yet.
Check VM generation
In the left pane under Hardware, click Processor. Look at the top of the pane. It should say "Generation 2 VM". If it says Generation 1, you need to create a new Generation 2 VM and attach the VHDX disk to it, or reinstall Windows 11 on a new Generation 2 VM.
Verify Firmware settings
In the left pane, click Firmware. Under Boot Order, the DVD Drive should be listed first (if you're installing Windows 11 from ISO). Below that, click the Security section on the left.
Enable Secure Boot and add virtual TPM
Under Security, tick Enable Secure Boot if not checked. Below that, look for Trusted Platform Module. If it's not listed, click Add at the bottom of the Hardware list, select Trusted Platform Module, and click Add.

VM is now configured as Generation 2 with Secure Boot and virtual TPM, which Windows 11 requires.

Fixing Corrupted Saved State and Boot Failures

If the VM status shows "Saved" or "Saved-Critical" instead of "Stopped" or "Running", or if it starts but hangs on a black screen with a cursor, the saved state file is corrupted or the video driver needs to be rebuilt. This happens frequently after a VM is restored from backup or moved to another Hyper-V host.

Delete Corrupted Saved State and Rebuild VM State Easy

Right-click the VM and delete saved state
In Hyper-V Manager, right-click the VM. If you see a Delete Saved State option, click it. Wait a few seconds for the operation to complete.
If Delete Saved State fails, manually remove state files
If the menu option is grayed out or fails, open File Explorer. Navigate to the folder where your VM is stored (typically C:\\Users\\[YourUsername]\\Documents\\Hyper-V or C:\\ProgramData\\Microsoft\\Windows\\Hyper-V). Find the folder matching your VM's name or GUID.
Locate and delete .bin and .vsv files
Inside the VM folder, look for files with .bin and .vsv extensions (these are saved state files). Delete them. Don't delete the .vhdx file, which is your disk.
Start the VM
Return to Hyper-V Manager, select the VM, and click Start. Hyper-V rebuilds the state and video configuration on first boot. The VM may take a minute longer to start than usual.

Saved state cleared. VM should now start cleanly and rebuild its video driver state.

Fixing Boot Order and ISO Attachment Issues

If you're installing Windows 11 on a new VM from ISO and the VM shows Boot Loader Failed, PXE over IPv4, or a black screen, the boot order is wrong or the ISO isn't attached. During a fresh Windows 11 install, you also need to press a key early to tell the VM to boot from the ISO instead of waiting for a network image.

Fix Boot Order and Capture Keyboard Input for ISO Boot Intermediate

Verify DVD Drive is attached and ISO is selected
Open the VM's Settings (right-click > Settings). In the left pane, expand SCSI Controller and click DVD Drive. On the right, make sure Image File is selected and the path points to your Windows 11 ISO file. If not, click Browse and select the ISO.
Set DVD Drive first in boot order
Click Firmware in the left pane. Under Boot Order, you should see DVD Drive listed first. If it's not, click DVD Drive and click the up arrow button to move it above Hard Drive. Click OK to save.
Close the VM window completely
If the VM was running or paused, close its connection window entirely. Don't just minimize.
Reopen the VM connection and prepare to press a key
In Hyper-V Manager, double-click the VM to open its connection window. Before you click Start, position your hand over the keyboard.
Start the VM and immediately press and hold a key
Click Start. Within one second, press and hold any key (like the spacebar). Keep holding it. The VM needs to capture this keystroke early in boot to register the intent to boot from the CD/DVD. You should see a message like "Press any key to boot from CD or DVD" after a moment.

VM now boots from ISO and Windows 11 installation starts. You'll see the Windows Setup screen.

Fixing Virtual Switch Mismatch and Resource Issues

When you restore a VM from backup or move it to a different Hyper-V host, the network adapter often points to a virtual switch that doesn't exist on the new system. This causes the VM to fail to start or start but lose network connectivity. You might also see a generic "Failed to start" error if the host doesn't have enough free RAM.

Fix Virtual Switch Mismatch and Check Host Resources Intermediate

Check host free RAM and disk space
Right-click This PC on your desktop and select Properties. Under Device Specifications, note your total RAM. Then open Task Manager and check the Performance tab > Memory to see how much is currently in use. If free RAM is less than the VM's allocated memory, close other applications or increase available RAM. Also check that the drive storing the VM has at least 5-10 GB free space.
Open Virtual Switch Manager
In Hyper-V Manager, click Virtual Switch Manager on the right pane under Actions.
Note the names of existing virtual switches
In Virtual Switch Manager, look at the list on the left. You'll see one or more switches, typically named Default Switch, External, or Custom names. Write down the exact names.
Edit the VM's network adapter
Close Virtual Switch Manager. In Hyper-V Manager, right-click the VM and select Settings. In the left pane, expand Network Adapter and click the top-level entry (or look under the VM name for Network Adapter entries).
Change the virtual switch to an existing switch
On the right pane, you'll see a dropdown under Virtual Switch. Click it and select one of the switches from Virtual Switch Manager (e.g., Default Switch). If the dropdown is empty or grayed out, click Cancel, verify at least one switch exists in Virtual Switch Manager, then try again.
Apply and start the VM
Click OK to save. Now try to start the VM. It should start without the network switch error.

Virtual switch reconfigured. VM network adapter now points to a valid switch. If host had low RAM, free some memory and try again.

Advanced: Validate Hyper-V Services and Enable Virtualization in BIOS

If the quick and intermediate fixes didn't work, the Hyper-V role itself might be corrupted, or key virtualization features are disabled in BIOS. This section involves PowerShell commands and BIOS changes, so take your time.

Rebuild Hyper-V Services and Enable BIOS Virtualization Features Advanced

Check BIOS/UEFI for virtualization, SLAT, and DEP settings
If systeminfo earlier showed any Hyper-V Requirements as No, or if you skipped that step, restart your PC and enter BIOS setup. The key varies: F2 (Dell, Lenovo), Delete (ASUS, Gigabyte), Esc (HP), or F10 (Compaq). Once in BIOS, look for sections like Advanced, Processor, Security, or Virtualization. Enable:
- Intel VT-x, Intel Virtualisation Technology, or Virtualisation (Intel systems)
- AMD-V or Secure Virtual Machine (AMD Ryzen systems)
- SLAT, EPT (Extended Page Tables), or NPT (Nested Page Tables)
- DEP, NX Bit, XD Bit, or Execution Disable Bit
Save and exit. Your host reboots into Windows.
Open elevated PowerShell
Press Windows+X and select Windows PowerShell (Admin). If you see Windows Terminal (Admin), that works too.
Verify Hyper-V components are enabled
Type: Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "Microsoft-Hyper-V*"}
Press Enter. Look at the State column. All entries should show Enabled. If any show Disabled, note their FeatureName.
Re-enable Hyper-V if components are disabled
Type: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All -NoRestart
Press Enter. Wait 2-3 minutes. You'll see a progress indicator. When done, type Restart-Computer and press Enter to reboot.
Check Hyper-V services after reboot
After reboot, open elevated PowerShell again. Type: Get-Service vmms, hvhost
Press Enter. Both services should show Status: Running. If either shows Stopped, type Start-Service vmms and press Enter.

Hyper-V services confirmed running. All virtualization features enabled in BIOS. Host is now fully configured for Hyper-V Windows 11 VMs.

If Hyper-V Windows 11 VM Still Won't Start After These Steps

At this point, you've covered 95% of startup failures. If the VM still won't start or boot, one of three things is happening: the VHDX disk is corrupted, Windows 11 inside the guest is corrupted and needs repair, or there's a hardware compatibility issue between the host and Windows 11's virtualization requirements.

Check the Windows 11 Task Manager showing high CPU usage article if the VM starts but becomes unresponsive or sluggish. If you see a black screen with cursor after Windows login, the guest OS booted but something inside is wrong.

For disk corruption, you can try attaching the VHDX to another VM as a secondary disk and running CHKDSK. Open Disk Management inside the VM and scan for errors. If the VM can boot into Windows Recovery Environment, run sfc /scannow from Command Prompt to repair system files. If recovery attempts fail, the VHDX is likely unrecoverable and you'll need to restore from backup or reinstall Windows 11.

Warning: Do not delete the VHDX file thinking it will let you start fresh. Deleting the VHDX destroys the entire VM disk and all data. Always export the VM first to back it up, or clone the VHDX before attempting repairs.

Preventing Hyper-V Windows 11 VM Won't Start in the Future

The best defense is understanding what configurations matter and keeping them documented.

Always create Windows 11 VMs as Generation 2. The moment you set up a new Windows 11 VM in Hyper-V, make it Generation 2 with Secure Boot and virtual TPM. Do this before installing Windows. Don't think you can upgrade a Generation 1 VM later; you can't. Generation is baked into the VM config.

Run systeminfo on the host once a month. Get in the habit of opening Command Prompt and running systeminfo to verify all four Hyper-V Requirements still show Yes. If virtualization ever shows Disabled, something reset your BIOS settings (power loss, CMOS battery, firmware update). Fix it immediately.

Delete old checkpoints and avoid saved states. Checkpoints and saved states are useful for testing, but they're fragile. After you're done testing, delete checkpoints. And shut down VMs cleanly instead of saving them; always prefer a clean shutdown.

Keep Windows and Hyper-V patched. Check Windows Update monthly. Hyper-V hypervisor and driver updates fix compatibility issues with Windows 11, and out-of-date hosts can cause VMs to fail to start or perform poorly.

Document the VM's generation, boot order, switch name, and storage path. If disaster strikes and you need to restore a VM, these details are gold. Keep a text file or spreadsheet with this info for each VM you rely on. When restoring, you'll know exactly which switch name to look for and whether the VM is Generation 1 or 2.

Monitor free host RAM and disk space weekly. Hyper-V fails silently when the host runs out of resources. Use Task Manager to check RAM weekly, and open This PC monthly to verify the drive has at least 5-10 GB free beyond all VM disk sizes.

Test VM startup immediately after restore or move. Don't wait a week to discover the restored VM won't start. Boot it right away, fix any switch mismatches, and verify it boots cleanly before you trust it.

Hyper-V Windows 11 VM Won't Start: Summary

When a Hyper-V Windows 11 VM won't start, you're almost always looking at one of five issues: host virtualization disabled in BIOS, VM is Generation 1 instead of Generation 2, corrupted saved state, wrong boot order or missing ISO, or virtual switch mismatch after restore. Start with Task Manager to check virtualization status, then verify the VM is Generation 2 with Secure Boot and TPM enabled. If the VM is stuck in Saved state, delete the saved state files. If you're installing from ISO, make sure the DVD drive is first in boot order and you press a key early in startup. If the VM was restored from backup, fix any virtual switch mismatches. These five fixes resolve 85% of Hyper-V Windows 11 VM startup failures. The advanced steps involving BIOS changes and PowerShell are only needed if virtualization features are completely disabled or Hyper-V services have crashed. Document your VM configuration, keep the host patched and resourced properly, and you won't see this problem again.