Import Hyper-V Virtual Machine in Windows 10

Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems (aka: guests) can be used and managed just as if they were physical computer systems, however they exist in a virtualized and isolated environment.

Import allows you to restore virtual machines. You don't need to export a virtual machine to be able to import it. Import will try to recreate the virtual machine from whatever is available. Importing a virtual machine registers the virtual machine with the Hyper-V host. A virtual machine export can be imported back into the host from which it was derived or new host.

This tutorial will show you how to import a Hyper-V virtual machine (guest) on your Windows 10 PC (host).

You must be signed in as an administrator to be able to import a Hyper-V virtual machine.

Note

Hyper-V is only available in the Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education editions.

6. Select (dot) an import type you want to perform, click/tap on Next, and go to step 7 or step 8 below depending on what import type you selected. (see screenshot below)

Import Type

Description

Register the virtual machine in-place

The current location of the Export files is where the virtual machine will be run from. When imported, the virtual machine has the same ID as it did at the time of export. Because of this, If the virtual machine is already registered with Hyper-V it needs to be deleted before the import will work. When the import has completed, the export files become the running state files and cannot be removed.

Restore the virtual machine

You are given an option to store the VM files in a specific location or use the locations default to Hyper-V. This import type creates a copy of the exported file and moves them to the selected location. When imported, the virtual machine has the same ID as it did at the time of export. Because of this, if the virtual machine is already running in Hyper-V it needs to be deleted before the import can be completed. When the import has completed the exported files remain untouched and can be removed and / or imported again.

Copy the virtual machine

This import type is similar to the Restore type in that you select a location for the VM files. The difference is that when imported the virtual machine has a new unique ID. This allows for the Virtual Machine to be imported into the same host multiple time.

The current location of the Export files is where the virtual machine will be run from. When imported, the virtual machine has the same ID as it did at the time of export. Because of this, If the virtual machine is already registered with Hyper-V it needs to be deleted before the import will work. When the import has completed, the export files become the running state files and cannot be removed.

You have the option to store the VM files in a specific location or use the locations default to Hyper-V. This import type creates a copy of the exported file and moves them to the selected location. When imported, the virtual machine has the same ID as it did at the time of export. Because of this, if the virtual machine is already running in Hyper-V it needs to be deleted before the import can be completed. When the import has completed the exported files remain untouched and can be removed and / or imported again.

A) Type the command below you want to use into the elevated PowerShell, press Enter, and go to step 6 below. (see screenshot below)

Substitute Full path of .vmcx file in the commands above with the actual full path of where the virtual machine .vmcx file you want to import is located.

Substitute Full path of folder to copy .vhdx file in the second command above with the actual folder path where you want to copy the virtual hard disk .vhdx file of the virtual machine you want to import.

Substitute Full path of folder to copy .vhdx file in the second command above with the actual folder path where you want to copy the virtual machine .vmcx file of the virtual machine you want to import.

This import type is similar to the Restore type in that you select a location for the VM files. The difference is that when imported the virtual machine has a new unique ID. This allows for the Virtual Machine to be imported into the same host multiple time.

A) Type the command below you want to use into the elevated PowerShell, press Enter, and go to step 6 below. (see screenshot below)

Substitute Full path of .vmcx file in the commands above with the actual full path of where the virtual machine .vmcx file you want to import is located.

Substitute Full path of folder to copy .vhdx file in the second command above with the actual folder path where you want to copy the virtual hard disk .vhdx file of the virtual machine you want to import.

Substitute Full path of folder to copy .vhdx file in the second command above with the actual folder path where you want to copy the virtual machine .vmcx file of the virtual machine you want to import.

@Brink,
I just had to use this today:)
Thanks to you and @Kari, I started exporting my VMs a short while ago(specially now that my Insider and Windows 8.1 VMs are licensed) and never needed to import.

Today I did something really, really dumb!

I was deleting my checkpoint sub trees totally on all three of my VMs(to recover what space, and all machines are/were working perfectly(yes, even the insider build)), and on my 3rd(insider build) I accidentally deleted it!

Well, I'm now reimporting it...

So I posted this to thank you & Kari, and also to show Hyper-V Geeks why it is very important to export!

My ComputersYou need to have JavaScript enabled so that you can use this ...

Folder Structure, Organizing

@Brink
Lots of valuable info, kudos both you & Kari.
This prolly aint the place, but in regards to 'keepin it clean' (file structure). I have all created/dynamic data on a different partition from OS (Win10P64); is there any recommended format w/regards to Hyper-V that could be advantageous? Have a top level for all VM's, /VMname with everything under (.vhdx, .vmcs, .vmcx) & don't know if this would be detrimental down the road...?
A tad different than a full-blown hyperVisr (ESXi) & now it seems this build on 10 is pretty sweet, thus curious on structure cleanliness.
...behavior mods for me - 'Save' 'Shutdown' & 'Turn Off' had to play with as no one said anything (yes I read Ben Armstrong's Virt Blog on turning off a VM here, referenced several times over the years ).

Wish there was a way to 'Save' while using an RDP session (not using VM connection).
Sorry if this appears as cross-post . But I'll keep looking around, thx all fer sharing info...!

My ComputerYou need to have JavaScript enabled so that you can use this ...

How to Create Shortcut of Hyper-V Virtual Machine in Windows 8 and 10
There's nothing wrong in running the Hyper-V Manager and launch your virtual machines from there. However, creating a shortcut for each vm you have you can start them fast...

How to Add or Remove a Physical Hard Disk for Hyper-V Virtual Machine
Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems (aka: guests) can be used and managed just as if they were physical...

How to See if Hyper-V Virtual Machine is Generation 1 or Generation 2
Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems (aka: guests) can be used and managed just as if they were physical...

UPDATE:
Problem solved.
See post #14's "long story" for steps that led to the findings above as the same steps can aid in hunting down this type of issue if neither of the above applies.
Hello,
I recently did an in place upgrade to Windows...

How to Remove Floppy Disk Drive in Windows Hyper-V Virtual Machine
Hyper-V enables running virtualized computer systems on top of a physical host. These virtualized systems (aka: guests) can be used and managed just as if they were physical...

About Us
Windows 10 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 10" and related materials are trademarks of Microsoft Corp.