Windows 10: Export Hyper-V Virtual Machine in Windows 10

How to: Export Hyper-V Virtual Machine in Windows 10

How to Export Hyper-V Virtual Machines 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.

You can use Hyper-V's export and import functionality to quickly duplicate virtual machines. Exported virtual machines can be used for backup or as a way to move a virtual machine between Hyper-V hosts.

Import allows you to restore virtual machines. You don't need to export a virtual machine to be able to import it.

When creating an export of a virtual machine, all associated files are bundled in the export. This includes configuration files, hard drive files, and any existing checkpoint files.

This tutorial will show you how to export a single or all Hyper-V virtual machines (guests) on your Windows 10 PC (host).

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


CONTENTS:

• Option One: To Export Hyper-V Virtual Machine(s) using Hyper-V Manager
• Option Two: To Export All Hyper-V Virtual Machines using PowerShell
• Option Three: To Export a Single Hyper-V Virtual Machine using PowerShell

Video by: Kari in TF Video thread






OPTION ONE [/i] To Export Hyper-V Virtual Machine(s) using Hyper-V Manager
1. Open Hyper-V Manager.

2. Select the Hyper-V host (ex: "BRINK-DESKTOP") in the left pane you want to export a virtual machine from, select one or more virtual machine(s) in the middle pane to export, and click/tap on Export in the right Actions pane. (see screenshot below)

*note You can press and hold the Ctrl key and click/tap on any virtual machine(s) to select them to export, then release the Ctrl key when finished selecting.



3. Click/tap on Browse, navigate to and select the folder (ex: "My Virtual Machines") that you want to export to, click/tap Select Folder, and click/tap on Export. (see screenshots below)



4. The virtual machine(s) will now be exported. It may take a while to finish. (see screenshots below)






5. When finished, you can close Hyper-V Manager if you like.





OPTION TWO [/i] To Export All Hyper-V Virtual Machines using PowerShell
*note For more details about the Export-VM command used in this option, see: Export-VM
1. Open an elevated PowerShell.

2. Copy and paste the command below into the elevated PowerShell, and press Enter.
*Arrow Get-VM | Export-VM –Path 'Full path of folder to export to'

*note Substitute Full path of folder to export to in the command above with the actual full path of the folder location you want to export the virtual machines' files to.
3. When finished, you can close PowerShell if you like.


Note This may take a while to finish exporting the virtual machine(s) to the specified folder location.







OPTION THREE [/i] To Export a Single Hyper-V Virtual Machine using PowerShell
*note For more details about the Export-VM command used in this option, see: Export-VM
1. Open an elevated PowerShell.

2. Type the command below into the elevated PowerShell, press Enter, and make note of the name (ex: "w10 build 14379") of the virtual machine you want to export. (see screenshot below)
*Arrow get-vm




3. Type the command below into the elevated PowerShell, and press Enter. (see screenshot below)
*Arrow Export-VM -Name 'Name of virtual machine' –Path 'Full path of folder to export to'



Note Substitute Name of virtual machine in the command above with the name of the virtual machine from step 2 above.

Substitute Full path of folder to export to in the command above with the actual full path of the folder you want to export the virtual machine to.

For example: Export-VM -Name 'w10 build 14379' –Path 'D:\My Virtual Machines'





4. The virtual machine will now be exported. It may take a while to finish. (see screenshots below)






5. When finished, you can close PowerShell if you like.

That's it,
Shawn


Related Tutorials

• How to Setup and Use Hyper-V in Windows 10 for OS Virtualization
• How to Import Hyper-V Virtual Machines in Windows 10
• How to Move Hyper-V Virtual Machine in Windows 10
• How to Change Default Folder to Store Hyper-V Virtual Machines
• How to Change Default Folder to Store Hyper-V Virtual Hard Disks
• How to Rename Hyper-V Virtual Machine in Windows 10
• How to Delete Hyper-V Virtual Machine in Windows 10

:)

 

Import a virtual machine from server 2008 R2

I was wondering if it is possible to exporting a virtual machine that is being hosted on a Server 2008 R2 host, and importing it to a Windows 10 machine that is running Hyper-v?

 

Windows 10 guest virtual machine on a Surface Pro 4 using Hyper-V.

There is no such permit in the Windows 10 End User License Agreement. You will need to purchase an additional license to install in Hyper-V just like you would for a virtual machine.

Setup a Virtual Machine with Windows 10 Hyper-V - groovyPost

also

Share Your Network Connection with Hyper-V in ... - groovyPost

 

@Brink & @Kari,
I just saw this new post: Windos just Trashed 1TB data External HDD - Windows 10 Forums and I am sooooo glad that after the tutorial and the video, plus Kari explain to me, how important a back up to an external disk is, and not just using Export to move the folders to another or new disk is.
Thanks again you Over Geeks*Thumbs



Information ***(this was also posted with the link, to show others, why this is so important)***
Don't delay VM geeks, do it today, if you don't have a backup, or else, you could end up like this poor member

 

Thanks guys,
I managed to export my vm using option [3]. For some reason option [1] does not work for me. When I try to export using Hyper-V Manager, I can browse to the target folder on my local drive and click export. Then the mmc.exe including the Export thread goes to (Not Responding) and I can only kill the the whole mmc process.
I have recorded a dump file if anybody would be willing to have a look.

 

You really might want to think about exporting, to either a 2nd internal, or much better; an external USB for backing up.

 

No worries Cliff, I did export to local but then copied it to my NAS backup for safety. But as you say it's so critical I will do another copy to my out-of-house second USB treasury chest...
I will have to read the article above.. is there absolutely no way to get ones Windows activation back if that UUID is lost? What if I just take a note of the UUID on a piece of paper... could one not call MS and get the key unlocked?

 

@Kari, @Superfly, or @Brink can answer those questions netter than me.
But that taking note of your UUID/GUID, doesn't work like that,
It's a 128 bit number generated by Windows to identify your "hardware" be it bare metal or virtual. You can't just enter it somewhere, and call it a day.

As for calling Microsoft, about the key if you lose your VM, the above three members, I mentioned above, can clarify that.
But it would just be easier to have a backup, and if you wish to get rid of the VM and start over, deactivate the key using Code: slmgr /upk [/quote] then deleting the machine, and re-creating one(this also works if you buy a new PC and prefer to use the retail key on the new one, and let the old PC revert to the OEM version).

 

then deleting the machine, and re-creating one(this also works if you buy a new PC and prefer to use the retail key on the new one, and let the old PC revert to the OEM version).[/quote] That does not work for digital licences.

 

Actually, the export tool does not do anything more sophisticated than copying the vhds and the vm file (.vmcx files). You can manually back the up using file explorer.

 

To get the digital license, he needs a retail key first, for a VM doesn't he?
Serious question, as that#s the only way I have done it.
The digital license, can be reactivated with another key, if one still has the machine.
I did that swapping a Pro for a Pro N before, and then using the Pro on another machine.

 

In general yes, but there are cases where you have a digital licence e.g. an install activated with a 7/8 oem key. bought 10 direct from MS Store, or you activated by transferring digital licence from another VM etc.

If key is retail standalone, you can use telephone activation if necessary to transfer a licence - I personally avoid the slmgr /upk method, as in past it seems to get tangled now and then i.e. new pc thinks it is still on old pc, but when you try telephone activation, it fails for some reason. Anyway, Windows normally lets you reactivate a standalone key up to five times anyway without objecting.

 

*Shock*Eek
Thanks for the information Martin*Smile
Good I only did it that once(and it's the only time I wanted/"needed" to do it).

 

What I was planning to do is try to activate my new vm of Win 10 16299.15 RTM with one of some never used before Windows 7 OEM keys. So, if this works at all, I will not be able to go over activation by phone. Good reason to keep a good backup of the vm them.
Will I also need another key for establishing another Windows Insider testing vm? That would be insane, of Microsoft to bill beta testers of it's software!?

 

Officially you need a key or digital license for each instance of Windows 10, any other answer is a very dark gray zone.




To read the license terms: Find Microsoft End User License Agreement (EULA) in Windows 10 General Tips Tutorials