Convert a VMware Workstation VMDK file to Hyper-V VHDX format offline

Today I've been working with Hyper-V on a desktop Windows 8.1 environment as an alternative to VMware Workstation.

There seem to be a myriad of options when it comes to converting the virtual hard disks from VMDK to the new(ish) VHDX format.

After trying various ones the information seems to be confusing and contradictory some don't support VHDX, some support VHDX such as Microsoft Virtual Machine Converter 3.0 graphical interface, however require you to be running VMware ESXi and vSphere, whereas I'm using VMware workstation.

The best solution I've found is to use the PowerShell commands for Microsoft Virtual Machine Converter 3.0,


  1. Download Microsoft Virtual Machine Converter 3.0
    http://www.microsoft.com/en-gb/download/details.aspx?id=42497
  2. Open PowerShell as an administrator


  3. Type C:
  4. cd "\Program Files\Microsoft Virtual Machine Converter"
  5. Import-Module .\MvmcCmdlet.psd1
  6. To see the available commands type
    get-command -module mvmc*
  7. The command we want is ConvertTo-MvmcVirtualHardDisk

    ConvertTo-MvmcVirtualHardDisk [-SourceLiteralPath] <string> [[-DestinationLiteralPath] <string>] [[-VhdType] <VhdType> {DynamicHardDisk | FixedHardDisk}] [[-VhdFormat] <VhdFormat> {Vhd | Vhdx}]  [<CommonParameters>]
  8. Here's the completed command line
    ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "D:\VirtualMachines\source.vmdk" -DestinationLiteralPath "D:\VirtualMachines\destination.vhdx" -VhdType DynamicHardDisk -VhdFormat Vhdx






Comments

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.