Converting virtual machines and disks from VMWare hosts to Hyper-V hosts and Windows Azure or convert computers and disks to Hyper-V hosts can be achieved by using Microsoft Virtual Machine Converter GUI or powershell cmdlet



  1. Microsoft Virtual Machine Converter 3.0
  2. dsfok toolset

VMWare virtual machines are in vmdk format which is not supported by Windows Hyper-V. Microsoft provide Microsoft Virtual Machine Converter for converting VMKD to VHD/VHDX format.

Microsoft Virtual Machine Converter (MVMC) provides native support for Windows PowerShell and can also be invoked through the Windows PowerShell command-line interface.

Converting VMDX to VHD/VHDX

  1. Open a powershell command line console in the folder where VMWar vmdk file is stored
  2. Execute following powershell command to import MVMC powershell commandlet
    Import-Module "C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1"
  3. Execute following command to begin the conversion process
    ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "file-to-be-converted.vmdk" -DestinationLiteralPath "<destination-folder-path>" -VhdType DynamicHardDisk -VhdFormat Vhd


  • SourceLiteralPath_ is the path to a VMware virtual disk that should be converted.
  • DestinationLiteralPath_ is the path to a directory where the virtual disk of the Hyper-V format should be saved.
  • VhdType_ defines the type of the virtual disk – either dynamically expanding or fixed.
  • VhdFormat_ defines the format of the Hyper-V virtual disk (VHD or VHDX).

Wait until the conversion process is finished. You will find the converted VHD/VHDX file in the folder path mentioned in DestinationLiteralPath parameter.


You might encounter following error when ConvertTo-MvmcVirtualHardDisk is execute

ConvertTo-MvmcVirtualHardDisk : The entry 4 is not a supported disk database entry for the descriptor.

Please note that the entry number can be any number.

To fix this, use dsfo and dsfi executables from dsfok toolset to update the vmdk descriptor information on the file. Use dsfo.exe to extract disk descriptor out of the VMDK file.

dsfo.exe "file-to-be-converted.vmdk" 512 1024 descriptor1.txt

The vmdk descriptore information is extracted into descriptor.txt. The content of this fill will be something like this:

# Disk DescriptorFile

# Extent description
RW 209715200 SPARSE "00054_C8PHS1096_151216-disk2.vmdk"

# The Disk Data Base 

ddb.adapterType = "lsilogic"
ddb.geometry.biosCylinders = "13054"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosSectors = "63"
ddb.geometry.cylinders = "13054"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "64d4e008b7227bcce8aa54995379bf0f"
ddb.toolsInstallType = "4"
ddb.toolsVersion = "10241"
ddb.uuid = "60 00 C2 96 f7 70 f2 fd-b5 02 9e 46 6c df 00 2e"
ddb.virtualHWVersion = "10"

Pay attention to the following line in the descriptor1.txt file

ddb.toolsInstallType = “4”

ConvertTo-MvmcVirtualHardDisk command fails as it doesn’t like this line. To resolve this issue, edit the descriptio1.txt file and command this line by adding a # infront of ddb.toolsInstallType line.

Now use dsfi.exe tool to reapply the descriptor to the vmdk file.

dsfi.exe "file-to-be-converted.vmdk" 512 1024 descriptor1.txt

Finally execute ConvertTo-MvmcVirtualHardDisk to convert vmdx to vhd/vhdx.

Import-Module "C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1"

ConvertTo-MvmcVirtualHardDisk -SourceLiteralPath "file-to-be-converted.vmdk" -DestinationLiteralPath "<destination-folder-path>" -VhdType DynamicHardDisk -VhdFormat Vhd


I have created this guide based the experience I had gained while converting a VMware virtual machine to Hyper-V and various articles I have read on Google. Any action you take upon the information provided in this article is strictly at your own risk and I will not be liable for any losses and damages in connection with the use of this article.