Welcome to Microsoft Q&A!
Thank you for taking the time to provide the detailed information and screenshots.
Based on the information provided, this error does not necessarily mean that your signed-in account or the SYSTEM account lacks permission to H:\Recovery.
When Hyper-V exports a virtual machine, Hyper-V needs to read the VM configuration files, virtual hard disks, and any checkpoint files before writing the exported files to the destination. Therefore, having Full control on the destination folder alone does not confirm that Hyper-V can access every source file required for the export.
A likely cause is an NTFS permission issue affecting one of the VM's source files or folders, such as the .vhdx, checkpoint .avhdx, or VM configuration files.
Hyper-V also uses a VM-specific security identity in the following form:
NT VIRTUAL MACHINE\<VM-ID>
Microsoft documents a related 0x80070005 scenario where Hyper-V cannot access a virtual disk because the VM-specific security identity does not have the required permission. Although that documentation describes a VM startup scenario rather than an export failure, it demonstrates why checking only the destination folder permissions may not be enough.
As a focused isolation test, please create a new empty folder on a local NTFS drive on the Hyper-V host, for example:
C:\HyperVExport
Grant SYSTEM and Administrators Full control on this folder and then try exporting one affected VM to the new location.
You can also perform the same test from an elevated PowerShell session:
Export-VM -Name "VMName" -Path "C:\HyperVExport"
If the export still fails with 0x80070005, check the permissions on that VM's source folder, VHDX, checkpoint files, and configuration files. In particular, verify whether permission inheritance has been changed or whether the VM-specific NT VIRTUAL MACHINE\<VM-ID> identity is missing the required access.
If the export still fails when using the clean local folder, please check Event Viewer for Hyper-V VMMS/Worker events recorded at the same time as the failure. These events may identify the specific file or path for which access is being denied.
If the export succeeds to C:\HyperVExport, this will indicate that the VM can be exported successfully and that the investigation should instead focus on the original destination and any permissions or access controls affecting it.
Moreover, I also want to be transparent about what we can reliably investigate through the forum.
Microsoft Q&A is a community-based support platform, so I can review the information you share and provide troubleshooting guidance based on documented behavior. However, I do not have direct access to your Hyper-V host or the ability to remotely inspect the effective NTFS permissions, VM files, Hyper-V configuration, system state, or complete diagnostic logs.
Because 0x80070005 is a general Access is denied error, determining exactly which security identity or file is causing the failure may require examining the host and its diagnostic data directly. Without that access, I would not want to speculate about the exact root cause or ask you to make additional permission changes without sufficient evidence.
For this reason, if the issue continues after the local export test and the Hyper-V event logs do not identify the object returning Access Denied, I may not be able to provide further reliable troubleshooting through the Q&A forum alone. At that point, I recommend opening a Microsoft Support case, where the support engineer can work with you to collect and analyze the necessary diagnostic information from the affected environment.
I hope the local export test helps narrow down whether the issue is associated with the VM's source files or the original export destination.
References:
Export and import virtual machines
Hyper-V virtual machine doesn't start with error 0x80070005
Troubleshoot Hyper-V Installation, Configuration, and Operational Failures - Windows Server | Microsoft Learn
If you find it useful, please click Accept Answer.
Thank you for choosing Microsoft Q&A.