Hyper-V Error 0x80070005: Access Denied — How to Fix

What Does Hyper-V Error 0x80070005 Mean

Error 0x80070005 in the context of Hyper-V is the system code ERROR_ACCESS_DENIED ("Access is denied"). It occurs when the hypervisor or Hyper-V service cannot obtain the necessary permissions to read, write, or perform operations on files, the registry, or other system resources.

Typical scenarios where it appears:

• When creating a new virtual machine (VM) or virtual hard disk (VHD/VHDX).
• When starting an existing virtual machine.
• When exporting/importing a VM.
• When configuring network adapters of a virtual switch.

The full error text may vary, but the key phrase always indicates a permissions problem: The requested operation requires elevation. Access is denied.

Causes

Error 0x80070005 has specific and verifiable causes:

1. Insufficient access permissions (ACL) on Hyper-V folders. This is the most frequent cause. The account under which the Hyper-V service runs (NT VIRTUAL MACHINE\Virtual Machines or SYSTEM), as well as your current user, do not have full control over the folders:
   • C:\ProgramData\Microsoft\Windows\Hyper-V (VM configurations)
   • The folder where you save VHD/VHDX files.
   • The disk on which these files are located.
2. Conflict with third-party antivirus software or Windows Defender. Antivirus programs often block the hypervisor's access to low-level CPU resources (VT-x/AMD-V) or VM files, interpreting it as suspicious activity.
3. Strict Group Policy (GPO) or registry settings. Security policies, especially in corporate environments, may explicitly prohibit running the hypervisor or accessing certain types of memory/disks.
4. Corruption or outdated Hyper-V components. An incomplete Windows update installation can lead to permission conflicts between components.
5. Disk encryption (BitLocker). If the disk containing VM files is encrypted with BitLocker and is not automatically unlocked before system boot, Hyper-V will be unable to read it.

Method 1: Configuring Access Permissions (ACL) — Primary Solution

This resolves cause #1.

1. Identify the folder causing the problem. Most often, this is the folder you specified when creating the virtual hard disk or virtual machine.
2. Open the folder's properties. Right-click the folder → Properties → Security tab.
3. Click "Advanced". At the top of the window, find and click the "Advanced" button.
4. Change the owner (if needed). If the "Owner" field does not show Administrators or SYSTEM, click "Change". Enter Administrators or SYSTEM, click "Check Names" → OK. Don't forget to check the box "Replace owner on subcontainers and objects".
5. Add the necessary accounts and grant permissions:
   • Click "Add" → "Select a principal".
   • Enter SYSTEM → "Check Names" → OK.
   • Under "Basic permissions", select "Full control".
   • Repeat for the account: NT VIRTUAL MACHINE\Virtual Machines (if it exists) and for your personal user account.
   • For each added principal, also check the box "Replace all child object permission entries with inheritable permission entries from this object".
6. Apply changes. Click OK in all windows. The system will begin recursively applying permissions. This may take a while if there are many files.

⚠️ Important: If the folder is on a different partition (not the system partition), ensure that file system does not have special restrictions (e.g., it is not mounted as Read-only).

Verification via Command Prompt (Administrator)

You can check current ACLs by running in PowerShell (Administrator):

Get-Acl -Path "D:\HyperV\VMs" | Format-List

To grant permissions en masse (replace D:\HyperV\VMs with your path):

$path = "D:\HyperV\VMs"
$acl = Get-Acl $path
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("SYSTEM","FullControl", "ContainerInherit,ObjectInherit", "None", "Allow")
$acl.SetAccessRule($rule)
$acl | Set-Acl -Path $path

Method 2: Disabling Conflicting Software (Antivirus, Firewall)

This resolves cause #2.

1. Temporarily disable real-time protection:
   • Windows Defender: Go to Windows Security → Virus & threat protection → Manage settings → turn off Real-time protection.
   • Third-party antivirus: Find its icon in the system tray, right-click it, and select "Disable" or "Pause protection" for 15-30 minutes.
2. Disable Windows Firewall (temporarily): Open Windows Defender Firewall → "Turn Windows Defender Firewall on or off" → disable it for both private and public networks.
3. Try the action again (start the VM, create VHDX).
4. If the error disappears, the issue is with the security software. Configure exclusions:
   • Add Hyper-V folders (C:\ProgramData\Microsoft\Windows\Hyper-V and your working folder) to the exclusions list in your antivirus and Defender.
   • Add the processes vmms.exe (Hyper-V management service) and vmwp.exe (VM worker process) to exclusions.
   • In the firewall, create a rule allowing inbound/outbound connections for these processes.

Method 3: Checking and Correcting Group Policies and Registry

This resolves cause #3. Particularly relevant for corporate computers.

1. Check for a registry key disabling Hyper-V. Press Win+R, type regedit, press Enter.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Hyper-V
   

3. If such a key exists, check the parameters inside it. The most likely culprit is the DWORD parameter DisableHypervisor. If its value is 1, the hypervisor is disabled. Change the value to 0 or delete the entire Hyper-V key.
4. Also check the path for Hyper-V policies under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization.
5. Restart the computer after making registry changes.

💡 Tip: If the computer is domain-joined, policies may be overwritten from a server. In this case, contact your system administrator.

Method 4: Restoring Hyper-V Components and Updating the System

This resolves cause #4.

1. Run a system file integrity check. Open PowerShell as Administrator and execute:

   DISM.exe /Online /Cleanup-image /Restorehealth
   

   Wait for completion.
2. Then check and repair protected system files:

   sfc /scannow
   

3. Install the latest Windows cumulative updates. Go to Windows Settings → Update & Security → Windows Update → Check for updates. Install all critical and cumulative updates.
4. Restart the computer.
5. If the problem persists, try disabling and re-enabling the Hyper-V feature:
   • Control Panel → Programs and Features → Turn Windows features on or off.
   • Uncheck Hyper-V → restart.
   • After boot, check the box again and restart once more.

Prevention

To avoid recurrence of error 0x80070005:

• Always work with Hyper-V folders as an administrator. When creating a new folder for VMs, configure permissions immediately as described in Method 1.
• Configure proper exclusions in any installed antivirus before starting work with Hyper-V.
• Avoid installing "heavy" system optimizers and registry cleaners, which might accidentally reset ACLs.
• Regularly update Windows and drivers, especially for the chipset and storage controller (SATA/AHCI/RAID).
• When using disk encryption (BitLocker), ensure the disk containing VM files unlocks automatically at boot (via TPM key or PIN in pre-boot).