Last Updated on May 6, 2026
If you are looking for an easy and cheap way to get into the world of virtual machines, then using one of the available desktop virtualization platforms is the way to go. There are many choices when it comes to the available software that you can use to create virtual machines on your desktop computer including VirtualBox, Parallels (Mac), VMware Player, VMware Workstation and Microsoft Hyper-V.
When you start using these virtualization programs, you might spend a lot of time configuring your machines only to realize you prefer a different software platform later. If this happens, you can easily export them from one platform and import them into another.
In this article, we will be showing you exactly how to convert a Hyper-V VHD or VHDX file into a VMware VMDK file.
Locating Your Hyper-V Virtual Disk File
To begin the conversion process, you will first need to know the exact location of your Hyper-V disk file. You can easily find this location by opening the settings of your virtual machine and locating the path for the virtual hard disk.
The tool we are going to use to convert the Hyper-V VHDX disk file to a VMDK format is called QEMU Disk Imager. This incredibly useful program can be downloaded completely for free from their official website.
Once you download QEMU and extract the zip file, you will need to open a Windows command prompt. From there, simply navigate to the directory where you saved the extracted files.
Checking Virtual Disk Information via Command Prompt
If you want to view detailed information about your virtual disk file before converting, you can run a quick command. The command structure looks like this:Â qemu-img.exe info “Path to disk file”
For our example, we will be checking the info for a file called Windows 11 Quick.vhdx. If your specific file path contains any spaces, you will definitely need to use quotes at the beginning and end of the path.
qemu-img.exe info “D:\Hyper-V VMs\Windows 11 Quick.vhdx”
As you can see in our results, our disk file has a vhdx format, is 24 GB in physical size, and has a virtual size of 127 GB.
Converting the VHDX File to a VMDK File
To successfully convert the VHDX file into a usable VMDK file, we will need to use a slightly different command. The structure for the conversion command is:Â qemu-img.exe convert -p “Path to VHDX file” -O vmdk “Path and name for the converted VMDK file.vmdk”
You will need to add the entire path and file name of the source file, followed by the destination path and file name of your new converted disk file. Be absolutely sure to put the .vmdk extension at the very end of your destination file name.
For our specific example, we will be keeping the location and file name exactly the same but just adding .vmdk at the end of the command.
The -p flag is used to show the live progress on your screen, and the -O flag tells the program to output the file to your specified format. Once again, be sure to use quotes if you have any spaces in your folder path.
qemu-img.exe convert -p “D:\Hyper-V VMs\Windows 11 Quick.vhdx” -O vmdk “D:\Hyper-V VMs\Windows 11 Quick.vmdk”
When the conversion command is actively running, you will be able to see its completion progress at the bottom of the window.
When the command is completely finished, you can then navigate directly to the directory where you told the tool to create the new VMDK file. As you can see in the image below, we now have our original VHDX file alongside our brand new VMDK file.
Creating a New Virtual Machine in VMware Workstation
To create a new virtual machine in VMware Workstation using this exported Hyper-V disk file, you will need to start the standard new virtual machine creation process.
Since our newly exported disk file already has the Windows operating system installed on it, we will choose the option to install the operating system later.
Next, you will need to carefully choose the specific OS that matches your exported virtual disk. In our specific case, we will be selecting Windows 11 x64.
You can then give the new virtual machine a descriptive name, which will be used to automatically create the folder where all the virtual machine files will be stored. You also have the option to manually create this folder first and move your VMDK file inside so it stays perfectly organized with your other files.
If you are importing a modern Windows 11 virtual disk, you will likely need to enter an encryption password to satisfy the Trusted Platform Module (TPM) requirements.
Configuring Firmware, RAM, and Virtual Hardware Settings
Next, you can choose your preferred firmware type between BIOS or UEFI. For any newer operating systems, you will almost certainly want to choose UEFI.
Then you can assign the new virtual machine one or more processor cores depending on your host computer’s capabilities. You can also easily change the RAM settings if you want to increase or decrease the suggested memory amount.
Next, you can choose your desired networking type, which will most likely be left on the default NAT setting.
Then you can safely choose your SCSI controller type, where the default recommendation should work perfectly fine.
You will then be prompted to choose a disk type, and once again, sticking with the recommended option should be completely fine.
Attaching the Converted VMDK File and Booting Windows
On the next crucial step, you will need to select the option to use an existing virtual disk. This is where you will browse and select the newly created VMDK file we converted earlier.
If VMware prompts you to convert your attached disk to a newer format version, you can simply click on the Convert button to do so.
You can then finally start your new virtual machine. Windows may need a few moments to automatically configure the operating system for its new hardware environment since you just switched platforms from Hyper-V over to VMware.
For Windows 11 users, you might encounter a prompt stating that your PIN is no longer available due to a recent change in the security settings on the device.
This happens entirely because Windows has successfully detected brand new virtual hardware. You can easily resolve this by signing in with your Microsoft account and resetting your PIN to get right back into your Windows desktop.
For additional training resources, check out our online IT training courses.
Check out our extensive IT book series.
