Home › Hyper-V › 0x80004005

Hyper-V · 0x80004005 · Windows Server 2019 / 2022 / Windows 11 Pro

Hyper-V Error 0x80004005 Fix: Win Server 2019/22 & Win 11 VM Start Failure

Root cause is usually NT VIRTUAL MACHINE\Virtual Machines lacking Full Control permissions or a locked VHDX file. Fix by granting folder permissions and deleting orphaned snapshot chains.

Error Details

FactValueSourceNote
Exact error stringFailed to start the virtual machine (Error ID: 0x80004005)Hyper-V Manager UI / PowerShell Start-VM outputGeneric unspecified error indicating access or config failure
Affected OS BuildsWindows Server 2019, Windows Server 2022, Windows 11 ProProduct DocumentationApplies to all supported Hyper-V host versions
Critical Security PrincipalNT VIRTUAL MACHINE\Virtual MachinesFile System ACLs / Registry PermissionsMust have Full Control on VM storage directory
Relevant Servicevmms (Hyper-V Virtual Machine Management)Windows Services (services.msc) / Get-Service vmmsMust be running; blocked if host OS is not activated
Event Log SignatureHyper-V-Worker Event IDs 12010, 13002, 14002Windows Event Viewer > Applications and Services Logs > Hyper-VIndicates VM state change failure or worker process error

Log Files to Check

What This Error Actually Means

The error code 0x80004005, commonly displayed as "Unspecified error" or "Failed to start the virtual machine," is a generic COM (Component Object Model) failure indicator. In the context of Hyper-V on Windows Server 2019, 2022, or Windows 11 Pro, this code rarely indicates a true hardware fault. Instead, it signifies that the vmms service (Hyper-V Virtual Machine Management Service) attempted an operation—such as starting a VM, applying a checkpoint, or modifying configuration—but was blocked by a lower-level subsystem. The component raising this error is typically the Hyper-V Worker process (vmmworker.exe), which handles the actual I/O and state transitions for virtual machines. When you see this in Hyper-V Manager or via PowerShell's Start-VM, it means the management layer successfully issued the command, but the execution layer failed to acquire necessary resources, permissions, or file locks. It is a "catch-all" failure that usually masks specific issues like ACL misconfigurations on virtual hard disks, corrupted configuration files (.vmcx), or resource contention.

Affected Versions and Scope

This error manifests across all modern Hyper-V implementations, specifically Windows Server 2019 (builds 17763+), Windows Server 2022 (builds 20348+), and Windows 11 Pro/Enterprise. It is not tenant-specific in the cloud sense but is highly sensitive to local host configuration. The scope includes both Generation 1 and Generation 2 virtual machines, though Gen 2 VMs are more prone to this error due to Secure Boot and TPM dependencies. It frequently occurs in environments where VM storage has been migrated between hosts without preserving NTFS permissions, or where dynamic memory settings conflict with physical RAM availability. Note that this error does not typically occur on Windows Server 2016 or earlier unless specific compatibility shims are involved, as the permission model for NT VIRTUAL MACHINE\Virtual Machines was tightened in later builds.

Where To Look First: Logs and Event IDs

Do not rely solely on the Hyper-V Manager UI. The definitive source of truth is the Windows Event Log. Open Event Viewer and navigate to Applications and Services Logs > Microsoft > Windows > Hyper-V-Worker > Admin. You are looking for specific Event IDs that correlate with the timestamp of your failed action. The most common signatures are:

To extract these logs programmatically, use the following PowerShell cmdlet to filter for recent Hyper-V-Worker errors:

Get-WinEvent -LogName "Microsoft-Windows-Hyper-V-Worker/Admin" -FilterXPath "*[System[Level=2 and (EventID=12010 or EventID=13002 or EventID=14002)]]" -MaxEvents 10

Additionally, inspect the verbose logs located at C:\ProgramData\Microsoft\Windows Hyper-V\Logs\*.log. These text-based logs often contain stack traces that the Event Viewer abstracts away. Look for lines containing "Access Denied" or "File Lock Conflict."

Root Causes

Incorrect NTFS Permissions on VM Storage

The most frequent cause is a missing or incorrect ACL entry for the NT VIRTUAL MACHINE\Virtual Machines group. This security principal requires Full Control over the directory containing the VM's configuration and virtual hard disks. If this permission is missing, the vmmworker.exe process cannot read the .vmcx file or lock the .vhdx, resulting in a generic 0x80004005 error.

Orphaned Snapshot Chains or Locked VHDX Files

If a previous VM crash left an orphaned differencing disk (.avhd) or if another process (like antivirus software or a backup agent) has locked the .vhdx file, Hyper-V cannot merge or access the disk. This is common after abrupt host power losses.

Secure Boot and TPM Configuration Mismatches

For Generation 2 VMs, if Secure Boot is enabled but the guest OS does not trust the selected template (e.g., using MicrosoftUEFI for a Linux distro that requires MicrosoftEFI), the VM will fail to start with this error. Similarly, if the virtual TPM state file is corrupted, the VM cannot initialize its security stack.

Fix Procedure

  1. Verify Service Status: Ensure the Hyper-V Virtual Machine Management service is running. Use Get-Service vmms | Select-Object Status, StartType. If it is stopped, restart it with Restart-Service vmms.
  2. Correct NTFS Permissions: Navigate to the VM's storage folder in File Explorer. Right-click > Properties > Security > Edit > Add. Enter NT VIRTUAL MACHINE\Virtual Machines. Grant "Full Control" and ensure "Apply to" is set to "This folder, subfolders, and files." This is critical for the vmmworker.exe to function.
  3. Check for Locked Files: Use PowerShell to identify if any process has locked the VHDX. Run Get-Process | Where-Object { $_.Modules.FileName -like "*vhdx*" }. If a backup agent is holding the lock, pause it temporarily.
  4. Reset Secure Boot Template (Gen 2): If permissions are correct, disable Secure Boot in the VM settings to isolate the issue. If the VM starts, re-enable Secure Boot and change the template to "MicrosoftUEFICustom" or "MicrosoftEFI" depending on the guest OS.
  5. Validate Configuration File: If the error persists, rename the .vmcx file (e.g., to .vmcx.bak) and create a new VM with the same VHDX. This bypasses configuration corruption.
Warning: Do not manually delete .avhd files without merging them first. Deleting an active differencing disk will cause data loss in the virtual hard disk chain. Always use Hyper-V Manager > Delete Snapshot Subtree to safely merge changes.

Error Code Variants

Error Code Description Distinguishing Factor
0x80004005 Unspecified Error Generic failure; usually permissions, locks, or config corruption.
0x803F0014 Virtual Machine Failed to Start Specifically indicates a resource exhaustion issue (CPU/RAM) or incompatible VM generation settings.
0x803F0016 Virtual Machine Configuration Error Directly points to a malformed .vmcx or .vmrs file, often after an incomplete migration.

Verification

To prove the fix worked, attempt to start the VM again. In PowerShell, run Start-VM -Name "YourVMName". A successful start will return no output and exit code 0. Verify the state by running Get-VM -Name "YourVMName" | Select-Object State, which should return "Running." Check the Event Log again for new entries; the absence of Event IDs 12010, 13002, or 14002 in the last 5 minutes confirms stability. Additionally, inspect the VM's integration services status via Get-VMIntegrationService -VMName "YourVMName" | Where-Object Name -eq "Heartbeat" to ensure the guest OS is communicating properly.

Prevention

To prevent recurrence, implement a standardized deployment script that applies correct NTFS permissions during VM creation. Use Group Policy or Intune Configuration Profiles to enforce baseline security settings on Hyper-V hosts. Specifically, configure an OMA-URI policy to ensure consistent management of virtualization settings if managed via MDM:

./Device/Vendor/MSFT/Policy/Config/MDM_Virtualization/EnableHyperV

Furthermore, exclude VM storage directories from real-time antivirus scanning to prevent file lock contention. In Intune admin center > Devices > Configuration Profiles, create a new profile for Windows 10 and later, add the exclusion paths under Endpoint Protection settings. Regularly audit VM configurations using Get-VM | Select-Object Name, State, Generation to identify any anomalies before they cause outages.

Tip: Use dsregcmd /status on the Hyper-V host to verify its domain join state. A degraded domain trust relationship can sometimes interfere with the resolution of the NT VIRTUAL MACHINE\Virtual Machines SID, leading to permission errors even if ACLs appear correct.

Sources & References

  • Troubleshoot virtual machine startup failures in Hyper-V - Microsoft Learn
  • Error 0x80004005 when starting a VM due to permission issues - TechNet Community

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.