0x80070005 in Hyper-V export commonly indicates a file permission problem on the VM’s files, especially the virtual hard disk or checkpoint files.
Check these items:
- Identify whether the VM has checkpoints or AVHD/AVHDX files.
- Export includes the VM configuration, VHD/VHDX, and checkpoint files.
- If permissions are wrong on any
.vhd,.avhd, or related files, export can fail.
- Verify the VM’s ID and file permissions.
- The VM has a unique Virtual Machine ID.
- If that VM identity is missing from the security permissions on the
.vhdor.avhdfile, Hyper-V operations can fail with0x80070005.
- Add the VM identity back to the affected disk or checkpoint file.
- Open an elevated Command Prompt.
- Use the VM ID shown in the error or retrieve it from Hyper-V/PowerShell.
- Grant Full Control to the VM identity on the affected file:
icacls <Path of .vhd or .avhd file> /grant "NT VIRTUAL MACHINE\<Virtual Machine ID>":(F)
Example:
icacls "E:\VMs\VMName\Disk0.vhd" /grant "NT VIRTUAL MACHINE\5FC5C385-BD98-451F-B3F3-1E50E06EE663":(F)
- Retry the export.
- In Hyper-V Manager, right-click the VM and select Export.
- Or use PowerShell as Administrator:
Export-VM -Name <vm name> -Path <path>
- If the VM is part of a guest cluster using shared VHDS and the error appears during backup/export-related checkpoint activity, also check folder permissions.
- The folder holding the VHDS files and snapshot files may need additional permissions for the VMMS process.
This is usually not just about the signed-in user account. It is often the Hyper-V VM identity or VMMS process lacking access to one of the VM disk or snapshot files.