How to Fix Hyper-V Startup and VM State Errors in Windows 11

Hyper-V VMs can fail to start for several reasons. The usual causes include corrupted state files, invalid permissions, damaged disks, disabled virtualization settings, or stopped services. Errors like “Failed to start”, “General access denied”, or “The application encountered an error while attempting to change the state” often appear when these issues exist.

This guide gives you a clear path to identify what failed and what you need to fix the Hyper-V startup error and resolve VM state issues.

Methods to fix Hyper-V startup error and VM state issues in Windows 11

Make sure your environment meets these requirements before you start. This helps you avoid errors while troubleshooting.

📌 General prerequisites: 

• Windows 11 Pro, Enterprise, or Server with Hyper-V enabled
• Administrator rights on the host machine
• Access to VM configuration folders
• Ability to review event logs
• A known good backup if the VM is production critical

Method 1: Identify the error and gather diagnostic information

Your first goal is to understand the exact problem. This prevents guesswork and wasted effort. In this method, you capture the error and match it with Hyper-V logs so the next methods target the correct layer of the issue.

📌 Prerequisites:

• Access to Hyper-V Manager and Event Viewer.

Steps:

1. Attempt to start the VM in Hyper-V Manager to produce a fresh error message and new log entries.
2. Note the exact error message shown in the console.
3. Press Win + R, type eventvwr.msc, then click Enter to open Event Viewer.
4. Navigate to:

Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS > Operational
Applications and Services Logs > Microsoft > Windows > Hyper-V-Worker > Operational

5. Review recent error entries and record:
   • Event IDs such as 14050 or 18590
   • Detailed descriptions for troubleshooting

If relevant startup errors are identified, proceed to Method 2 to validate Hyper-V services and host virtualization settings.

Method 2: Confirm Hyper-V services and host virtualization settings

Next, confirm that the host is running Hyper-V properly. Hyper-V needs its core services and hardware virtualization active, or it will not work.

📌 Prerequisites:

• Ability to restart the system if BIOS changes are required.

Steps:

1. Press Win + R, type services.msc, and click Enter to launch Services.
2. Find the following entries:

• • Hyper-V Virtual Machine Management
  • Hyper-V Host Compute Service

3. Ensure both are Running and the Startup Type is set to Automatic. If either service is stopped, right-click and select Start.
4. Press Ctrl+Shift+Esc to open the Task Manager.
5. Navigate to Performance > CPU and confirm that Virtualization is Enabled.
6. If Virtualization is Disabled, restart your PC and enter the system setup utility (BIOS or UEFI).
7. Enable the following settings if available:

• • Intel VT-x (Intel systems)
  • Intel VT-d (if available)
  • AMD-V / SVM Mode (AMD systems)

8. Save and exit the system setup utility (BIOS/UEFI).
9. Restart the machine if the settings have changed.

Method 3: Check permissions and ownership of VM files

Hyper-V needs full access to VM folders and virtual disk files. In this method, you ensure there are no incorrect permissions or blocked files that can prevent VMs from starting. Your goal is to verify that the required accounts can read and write all VM-related files.

📌 Prerequisites:

• Path to the VM folder and VHD/VHDX files.

Steps:

1. Navigate to the VM’s storage folder. This is usually under:

C:\ProgramData\Microsoft\Windows\Hyper-V

or your custom storage location.

2. Right-click the folder, select Properties, then click Security.
3. Ensure the following have Full Control:
   • SYSTEM
   • NT VIRTUAL MACHINE\<Virtual Machine ID>
4. If the virtual machine SID is missing:
   • Click Edit > Add
   • Enter NT VIRTUAL MACHINE\<Virtual Machine ID>
   • Grant Full Control, then apply the changes.
5. Check VHD/VHDX file accessibility:
   • Right-click the disk file and select Properties.
   • Confirm Read-only is unchecked.
   • If the file was downloaded, click Unblock under Security.

Method 4: Fix locked or corrupted state files

Remove locked or corrupted state files if the VM fails to start. Hyper-V relies on state files to store memory and guest state during pause or save. When these files become damaged, the VM cannot load its previous state. Removing them allows Hyper-V rebuild clean state files on startup.

Steps:

1. Navigate to the VM’s storage folder. This is usually under:

C:\ProgramData\Microsoft\Windows\Hyper-V

or the VM’s active state folder (typically the Virtual Machines directory), not the Snapshots folder.

2. Delete the following state files if they exist or are corrupted:
   • .VMRS (runtime state)
   • .VMGS (guest state)

💡 These files will be recreated when the VM starts, but VM will not resume and will start from a powered-off state.

3. If a checkpoint is corrupt or causing errors, export the VM without checkpoints and reimport it in Hyper-V Manager.
4. Start the VM again in Hyper-V Manager.

Method 5: Validate the disk (VHD or VHDX)

In this method, you validate the structural integrity of VHD/VHDX files and address disk issues when detected. This is crucial because a corrupted virtual disk can prevent a VM from starting or cause data loss.

Steps:

1. Open Hyper-V Manager.
2. Select Actions > Edit Disk.
3. Browse to the VHD/VHDX.
4. Choose Inspect (if available):
   • Confirm the disk opens without errors
   • For AVHDX files, verify the parent disk path is correct
5. If the disk report issues, use Convert to create a new disk file and replace the original disk.
6. Mount the disk in read-only mode to validate accessibility.

Mount-VHD -Path “D:\VMs\disk.vhdx” -ReadOnly

7. Open File Explorer, right-click the mounted volume, select Properties, then navigate to Tools > Check.

Or open Command Prompt (Admin) and run: chkdsk X: /f

📌 Note: Replace X: with the mounted drive letter. Mount the disk in read-only mode to validate accessibility. Read-only mounts do not allow filesystem repairs.

8. Unmount the disk when finished: Dismount-VHD -Path “D:\VMs\disk.vhdx”

Method 6: Recreate or reimport the VM configuration

If the VM configuration is corrupted, Hyper-V may fail to start the VM even when the disks and state files are healthy. In this method, you recreate or reimport the configuration to restore a clean setup while preserving the existing virtual disks.

📌 Use Cases: Previous fixes did not resolve startup issues.

📌 Prerequisites:

• Enough storage space for VM export, and the VM is powered off or in a consistent state.

Steps:

1. Open Hyper-V Manager.
2. Right-click the VM and select Export.
3. Select a secure location with sufficient storage space.
4. Wait for the export process to complete.
5. Delete the broken VM entry by right-clicking the VM in Hyper-V Manager and selecting Delete. This removes the corrupted configuration but does not delete the exported files.
6. Then, reimport the VM by clicking Import Virtual Machine.
7. Browse to the exported folder.
8. Choose an import type:
   • Register: Use existing files.
   • Restore: Use exported files and keep original IDs.
   • Copy: Create new unique IDs.
9. After importing, open the VM settings and verify that all VHD/VHDX files are correctly attached.

Method 7: Validate the VM startup

Last in the process is confirming that the problem is fixed and that the VM can run reliably. In this method, you confirm that the VM starts successfully and stays stable for production use.

📌 Use Cases: Final verification after troubleshooting.

Steps:

1. Open Hyper-V Manager.
2. Select the VM and click Start.
3. Confirm the VM transitions to the Running state.

💡 If it fails, return to earlier methods based on the error type.

4. Check Event Viewer (eventvwr.msc) and navigate to:

Applications and Services Logs → Microsoft → Windows → Hyper-V-VMMS
Applications and Services Logs → Microsoft → Windows → Hyper-V-Worker

Look for warnings or errors related to VM startup.

5. Ensure Hyper-V services are still running.
6. Confirm VM folder permissions remain intact.
7. Optionally, create a temporary checkpoint and restart the VM to further validate stability.
8. Delete the checkpoint after testing to avoid unnecessary storage usage.

Troubleshooting

If you encounter any of these common Hyper-V issues during the process, use the following quick fixes to resolve them.

General access denied error

Reset permissions on the VM folder and all VHD or VHDX files. Confirm that SYSTEM and the Hyper-V Virtual Machine Management Service have Full Control.

Failed to attach disk

The VHD or VHDX is in use or corrupted. Close any process that has the disk open, then reattach it. If the disk still fails to open, validate it using the steps in Method 5.

VM stuck in saved state

Delete the .VMRS and .VMGS files from the VM storage folder. Hyper-V will create new state files when the VM starts.

Hyper-V Manager fails to start

Confirm that hardware virtualization extensions are enabled in BIOS or UEFI, that Hyper-V services are running, and the Hyper-V management components are properly installed and accessible.

Event logs show merge or checkpoint errors

Export the VM without checkpoints and then reimport it to restore a clean configuration and resolve damaged checkpoint chains.

Fix Hyper-V startup error and keep VMs running

Many Hyper-V startup errors come from permission problems, corrupted state files, invalid configurations, or disk issues. When you identify the root cause by reviewing diagnostics, checking file access, and confirming services, you can proceed to repair state files and validate disk health. This resolves most failures. Always validate the VM after repair to confirm stable and consistent operation.

Related topics:

• What is Hyper-V? Key Features and Capabilities
• How to Import Hyper-V Virtual Machines
• How to Export Hyper-V Virtual Machines in Windows
• How to Install and Enable Hyper-V on Windows 10 for Hardware Virtualization
• How to Delete Checkpoints for a Hyper-V Virtual Machine in Windows 11