Export Hyper-V Virtual Machine in Windows 10  

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 27,162
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #10

    cereberus said:
    That does not work for digital licences.
    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.
      My Computers


  2. Posts : 15,441
    Windows10
       #11

    Cliff S said:
    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.
      My Computer


  3. Posts : 27,162
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #12

    cereberus said:
    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.

    Thanks for the information Martin:)
    Good I only did it that once(and it's the only time I wanted/"needed" to do it).
      My Computers


  4. Posts : 70
    Windows 10 Pro, Ubuntu 18.04 LTS
       #13

    cereberus said:
    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.
    .
    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!?
      My Computers


  5. Posts : 27,162
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #14

    GalaxyGe said:
    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.
    Export Hyper-V Virtual Machine in Windows 10-image-001.png

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


  6. Posts : 15,441
    Windows10
       #15

    GalaxyGe said:
    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!?
    I am afraid you need a valid licence for Insider Testing - MS had to introduce that as many would have installed Insider versions to avoid buying a licence, but not actively participated in Programme. You can bet your life, these same persons would whinge like hell if they were affected by any bugs.

    You can run Insider versions unactivated without any major issue except you cannot personalise it. A lot do not mind being unable to personalise in a VM, as it is for testing purposes only.
      My Computer


  7. Posts : 70
    Windows 10 Pro, Ubuntu 18.04 LTS
       #16

    Export Hyper-V Virtual Machine in Windows 10


    cereberus said:
    I am afraid you need a valid licence for Insider Testing - MS had to introduce that as many would have installed Insider versions to avoid buying a licence, but not actively participated in Programme. You can bet your life, these same persons would whinge like hell if they were affected by any bugs.

    You can run Insider versions unactivated without any major issue except you cannot personalise it. A lot do not mind being unable to personalise in a VM, as it is for testing purposes only.
    That does make sense then, thanks for the explanation!

    I won't bother to activate my Insider Build testing vms then, they are really just to check out new features early and being able to comment on them.. no need to personalize I'd say.

    I did activate (yay - Win 7 OEM key worked!) my new FCU RTM vm though, as this one will have a slightly different purpose, e.g. for testing of programs and customizations. [emoji4]
      My Computers


  8. Posts : 31,465
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #17

    I find I cannot export any VM created by Macrium 7 viBoot. Using the Hyper-V Manager or Powershell the export goes to 99% then fails with:
    Export-VM : Failed to copy file during export.
    Failed to copy file from 'C:\ProgramData\Macrium\viBoot\{1E1C75AE-0529-4535-BC46007B6006DF5E}\657FA20E53586408.01791D81.vhdx' to 'D:\VMs\Exported\viBoot_VM\Virtual Hard Disks\657FA20E53586408.01791D81.vhdx': There is not enough space on the disk. (0x80070070).

    The 'not enough space' error doesn't seems to be the true reason for the failure. The destination drive has 130GB free, more than enough. Also, similar VMs that are not made by viBoot export without a problem to the same destination.

    I have found a workaround (of sorts). Open the Settings for the viBoot VM. Edit the hard drive, Merge it to make a new .vhxd, then in Hyper-V Manager create a new VM using that new .vhdx as the virtual disk. This VM can be exported.

    It seems a bit of a cludge and a lot of work just to be able to export the VM. Just what is it about a viBoot VM that causes this problem? Is there a more elegant way to fix it?
      My Computers


  9. Posts : 70
    Windows 10 Pro, Ubuntu 18.04 LTS
       #18

    are you sure the virtual disk within the vhdx is not bigger than 130 GB. Not sure about Macrium but I did have similar issues due to virtual hard disks being expanded when copying or extracting.
    Only way to solve its reducing size of the disk within the vm.
    Bree said:
    I find I cannot export any VM created by Macrium 7 viBoot. Using the Hyper-V Manager or Powershell the export goes to 99% then fails with:
    Export-VM : Failed to copy file during export.
    Failed to copy file from 'C:\ProgramData\Macrium\viBoot\{1E1C75AE-0529-4535-BC46007B6006DF5E}\657FA20E53586408.01791D81.vhdx' to 'D:\VMs\Exported\viBoot_VM\Virtual Hard Disks\657FA20E53586408.01791D81.vhdx': There is not enough space on the disk. (0x80070070).

    The 'not enough space' error doesn't seems to be the true reason for the failure. The destination drive has 130GB free, more than enough. Also, similar VMs that are not made by viBoot export without a problem to the same destination.

    I have found a workaround (of sorts). Open the Settings for the viBoot VM. Edit the hard drive, Merge it to make a new .vhxd, then in Hyper-V Manager create a new VM using that new .vhdx as the virtual disk. This VM can be exported.

    It seems a bit of a cludge and a lot of work just to be able to export the VM. Just what is it about a viBoot VM that causes this problem? Is there a more elegant way to fix it?
      My Computers


  10. Posts : 7,871
    Windows 11 Pro 64 bit
       #19

    I experimented exporting a VM before uninstalling Hyper V. The export files just replicate the folder tree I had already designated in another location. On reinstalling Hyper V, the original VM was found in its original location and the VM worked OK.
      My Computers


 

Tutorial Categories

Export Hyper-V Virtual Machine in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
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.

© Designer Media Ltd
All times are GMT -5. The time now is 10:51.
Find Us




Windows 10 Forums