FIX: Hyper-V did not find Virtual Machines to import from location.
This guide contains instructions to resolve the following error in Hyper-V Manager when trying to import a virtual machine: "Hyper-V did not find virtual machines to import from location…Virtual machine could not be found. You might not have permissions to access it".
The error "Hyper_V did not find virtual machines to import from…", usually appears for one of the following reasons:
1. Missing or corrupted files: The virtual machine configuration files are missing or could not be read (e.g. when they are corrupted).
2. Lack of permissions: You do not have enough rights to import the virtual machine or you don't have permission on the folder where the virtual machine files are stored.
3. Unsupported Hyper-V configuration version: The virtual machine you are trying to import has been exported from a Hyper-V host running a newer version or Hyper-V. This typically means that you cannot import a virtual machine from a Windows 11 Hyper-V host to a Windows 10 host, or from a Server 2019 host to a Server 2016 host.
To troubleshoot the error "Hyper-V No virtual Machine files found", follow the steps below.
How to FIX: Hyper-V No virtual Machine files found from location.
Step 1. Export Virtual Machine again.
To import a virtual machine to another Hyper-V host, you must have exported the following virtual machine's files from the old host:
- Virtual Hard Disk:
(C:\ProgramData\Microsoft\Windows\Virtual Hard Disks) - Configuration files:
(C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines) - Checkpoints: (C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots)
So make sure you have moved in the new Hyper-V host the following folders:
- Virtual Hard Disks
- Virtual Machines
- Snapshots
If you have done this, try re-exporting the virtual machine from the old Hyper-V host and then doing the import again to make sure the files are intact.
Step 2. Verify Permissions.
Make sure you have administrative rights on the new Hyper-V host to import the virtual machine and you have enough permissions on the exported folder.
Step 3. Create a New VM and attach the Virtual Disk file (.VHD)
As mentioned above, you can import a virtual machine to a Hyper-V host running a newer version of Hyper-V, but you cannot import a virtual machine created on a newer version of Hyper-V to an older version of Hyper-V.
For example, if you have exported the virtual machine from a Windows 11 Hyper-V host and try to import it into Windows 10, you will get the error "Hyper_V could not find any virtual machines to import". You will also get the same error when trying to import into Server 2016 a virtual machine exported from Server 2016 or Server 2022.
To work around this problem, create a new virtual machine and attach to it the disk file of the virtual machine you want to import. To do that:
1. Copy all the contents of the "Virtual Hard Disks" folder of the virtual machine you want to import, to the following location/folder on the new host:
- C:\ProgramData\Microsoft\Windows\Virtual Hard Disks\
2. Then, open Hyper-V Manager and click New > Virtual Machine to create a new VM.
3. Click Next on the first screen, then type a name for the new virtual machine and click Next again.
4. On the next screen choose the machine's generation e.g. "Generation 1" in this example and click Next again.
5. Then specify the amount of memory to allocate to this virtual machine and click Next.
6. Now select Default Switch for networking and click Next.
7a. In 'Connect Virtual Hard Disk' screen, select Use an existing virtual disk and then click Browse.
7b. Now choose the VM's virtual disk file (.VHD or .VHDX) and click Open.
7c. Then click Next to continue.
8. Finally click Finish.
9. Finally, start the virtual machine and you're done!
That's it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
Frequently Asked Questions
Why does the error 'Hyper-V did not find virtual machines to import from location' occur?
The error usually occurs due to missing or corrupted files, lack of permissions, or an unsupported Hyper-V configuration version.
How can I verify permissions to resolve the import issue in Hyper-V Manager?
Ensure you have administrative rights on the new Hyper-V host and have enough permissions on the exported folder where the virtual machine files are stored.
What should I do if I cannot import a virtual machine due to an unsupported Hyper-V configuration version?
Create a new virtual machine on the target host and attach the existing virtual disk file (.VHD) from the virtual machine you want to import.
What are the essential folders to move when exporting a virtual machine to another Hyper-V host?
You must move the Virtual Hard Disks, Virtual Machines, and Snapshots folders to the new Hyper-V host.
- FIX: Device encryption is temporarily suspended and does not resume after the computer restarts (Windows 11). - May 5, 2026
- How to Install Chrome or any 'Line of Business' app on Intune Enrolled Windows Devices. - April 29, 2026
- How to Create a DDM Update Policy for iOS Devices in Intune. - April 23, 2026
