Free online VHDX to OVA converter

What the VHDX format is

VHDX is Microsoft's virtual hard-disk format for Hyper-V and related Windows virtualization tools. It stores a guest operating system's virtual disk, including partitions, boot files, applications, and data; it does not store the complete VM configuration.

Hyper-V Manager creates VHDX files when you create or configure a Generation 1 or Generation 2 virtual machine. Windows Server, Windows 10, and Windows 11 commonly use them. Hyper-V checkpoints can also create differencing .avhdx files, which depend on a parent VHDX and cannot be treated as independent disks.

What the OVA format is

OVA is a single-file Open Virtualization Appliance package. It is a TAR archive containing an OVF virtual-machine descriptor, one or more virtual disks, and sometimes a manifest with SHA checksums.

OVA is intended for moving a complete VM between OVF-compatible products such as VirtualBox, VMware products, and some enterprise virtualization platforms. It packages virtual hardware settings with the disks, so importing software can create the VM instead of attaching a disk manually.

How to actually convert VHDX to OVA

Using QEMU and VirtualBox

1. Shut down the Hyper-V VM. Do not convert a disk that is being written to.
2. Merge or remove any required Hyper-V checkpoints first. In Hyper-V Manager, use Checkpoint → Delete Checkpoint and wait for disk merging to finish. Keep the resulting parent VHDX and all backups until the imported VM has been tested.
3. Install QEMU for its qemu-img utility and install VirtualBox on the destination computer.
4. Convert the disk to VirtualBox's VDI format:

qemu-img convert -p -f vhdx -O vdi source.vhdx converted.vdi

Use the actual path if the file is elsewhere. Add -O vmdk instead of -O vdi when the intermediate disk will be attached to VMware or another product that prefers VMDK.

5. Create a new VM in VirtualBox with the guest's operating-system type, CPU count, memory, and network mode. Select Machine → New, skip automatic installation, and attach converted.vdi as the existing virtual hard disk.
6. Match the original Hyper-V firmware. Use BIOS for most Generation 1 VMs. Use EFI for Generation 2 VMs; in VirtualBox this is available under Settings → System → Motherboard → Enable EFI. If the guest used Hyper-V Secure Boot, temporarily disable it for the first boot or configure a compatible VirtualBox Secure Boot setup.
7. Start the VM and verify that the guest boots, its system disk is correct, and its network adapter is available. Install VirtualBox Guest Additions only if the VM will remain in VirtualBox.
8. Power off the VM, then select File → Export Appliance. Choose the VM, select an OVA output path, and start the export.

The equivalent VirtualBox command-line sequence is:

VBoxManage createvm --name MigratedVM --register
VBoxManage modifyvm MigratedVM --memory 4096 --cpus 2 --firmware bios --nic1 nat
VBoxManage storagectl MigratedVM --name SATA --add sata --controller IntelAhci
VBoxManage storageattach MigratedVM --storagectl SATA --port 0 --device 0 --type hdd --medium converted.vdi
VBoxManage export MigratedVM --output MigratedVM.ova

Replace --firmware bios with --firmware efi for a Generation 2 guest. Change the memory, CPU, network, storage-controller, and VM names to match the source system and destination requirements.

For a disk-only conversion, you can convert the file for free on 101convert.com without installing software. A disk converter does not reconstruct Hyper-V firmware, CPU, network, checkpoint, or Secure Boot settings, so a complete OVA still requires VM creation and export.

Quality, compatibility, and limitations

The conversion changes the virtual disk container; it does not convert the installed operating system's drivers or hardware assumptions. Windows may detect a new storage controller, network adapter, or virtual BIOS and require a reboot, driver installation, reactivation, or network reconfiguration.

Generation 2 guests use UEFI and commonly GPT partitioning. Exporting one with BIOS selected can produce a non-booting OVA. Linux guests may also need an initramfs or bootloader update if the virtual disk controller changes from Hyper-V SCSI to the controller presented by the destination hypervisor.

OVA compatibility is not identical across products. VirtualBox generally exports a VMDK inside the OVA, while VMware may expect a particular VMDK variant, virtual hardware version, or controller type. If the target is VMware, create or import the VM in VMware first and use File → Export to OVF or VMware OVF Tool rather than assuming every VirtualBox-generated OVA will import without adjustment.

Validate the exported file by importing it into the target hypervisor before deleting the original VHDX. An OVA may be large because it contains the allocated or converted virtual disk; packaging it as OVA does not guarantee compression or reduced storage use.