Free online VHDX to OVF converter

Hyper-V creates VHDX disks, but many VMware, VirtualBox, and appliance-import workflows require an OVF package. Converting is useful when moving a virtual machine between hypervisors or distributing it as a portable appliance.

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 user data.

Hyper-V Manager, Windows Server, Azure Stack HCI, and PowerShell commonly create VHDX files. A VHDX is a disk image only; it does not contain the complete virtual machine configuration, such as memory, virtual CPUs, firmware mode, network adapters, or controller assignments.

What the OVF format is

OVF, the Open Virtualization Format, describes and packages a virtual machine for import into virtualization software. An OVF export normally contains an XML descriptor, one or more virtual disk files such as VMDK, and optionally a manifest file with checksums. The descriptor records hardware settings, disk controllers, firmware details, memory, CPUs, and network interfaces.

OVF is useful for moving appliances between compatible VMware, VirtualBox, and other OVF-aware platforms. An OVA file is the same type of appliance distributed as one TAR archive; OVF itself is usually a group of files.

How to actually convert VHDX to OVF

The reliable desktop workflow is to convert the VHDX into VMDK, create a virtual machine around that disk, then export the configured machine as OVF. QEMU’s qemu-img and Oracle VirtualBox provide a cross-platform method.

1. Install QEMU and VirtualBox, and place the source disk in a working directory. Check its format and backing-file information with qemu-img info source.vhdx. If the VHDX depends on a parent disk, preserve the complete chain or merge it before conversion.
2. Convert the disk to VMDK:

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

   Use a different output filename if the source contains multiple disks. Ensure the destination has enough free space; conversion can create a large file even when the original VHDX is dynamically expanding.

3. Create a VirtualBox VM without adding a new disk:

   VBoxManage createvm --name ImportedVM --ostype Windows2022_64 --register
VBoxManage modifyvm ImportedVM --memory 4096 --cpus 2 --firmware efi
VBoxManage storagectl ImportedVM --name SATA --add sata --controller IntelAhci
VBoxManage storageattach ImportedVM --storagectl SATA --port 0 --device 0 --type hdd --medium converted.vmdk

   Choose --firmware bios instead if the Hyper-V guest used legacy BIOS. Set the guest type, memory, CPU count, network adapter, and controller type to match the original machine where practical.

4. Test the imported VM before exporting it. If Windows starts, it may detect different virtual hardware and install new storage or network drivers. Shut the VM down cleanly after testing.
5. Export the VM as OVF:

   VBoxManage export ImportedVM --output imported-appliance.ovf

   VirtualBox writes the OVF descriptor and its disk file or files to the output location. In the graphical interface, use Machine → Export to OCI only for cloud appliance workflows; for a local OVF export, use File → Export Appliance, select the VM, choose OVF 1.0 or OVF 2.0 when offered, and save the appliance.

For VMware-based environments, the same converted VMDK can be attached to a newly created VMware VM with matching firmware and controller settings, then exported with VMware OVF Tool. The source for ovftool is typically the VMware VM or .vmx configuration rather than the VHDX file itself.

If installing conversion software is not appropriate, 101convert.com provides a free online conversion option; upload the VHDX and download the generated OVF package if the service accepts the disk and package structure.

Quality, compatibility, and limitations

There is no direct one-file VHDX-to-OVF transformation: VHDX contains disk data, while OVF also requires virtual hardware metadata. A converter can preserve partitions and files but cannot infer every original Hyper-V setting from the disk alone.

Generation 2 Hyper-V guests normally use UEFI and may use Secure Boot. Preserve UEFI in the destination VM and disable Secure Boot temporarily if the target hypervisor does not provide compatible Microsoft or Linux keys. A Generation 1 guest normally requires BIOS mode.

Snapshots, differencing disks, pass-through devices, virtual TPM state, Hyper-V checkpoints, and host-specific integration services are not fully preserved by disk conversion. BitLocker-protected guests may require their recovery key after the virtual hardware changes. Remove or reconfigure Hyper-V Integration Services, synthetic network adapters, and static MAC-dependent settings when the destination platform uses different virtual devices.

After import, verify that the guest boots, its system and data partitions are present, network connectivity works, and applications do not depend on the old virtual hardware. Keep the original VHDX and all parent disks until the OVF appliance has been tested.