Hyper-V → Proxmox
VHDXQCOW2
VHDX is Hyper-V’s disk: dynamic or fixed, 512e or 4K, sometimes a differencing chain. Proxmox does not mount that natively. Converting to QCOW2 is the usual bridge when a Windows VM is leaving Hyper-V.
No account on the public uploader. Guest jobs stay within five conversions and 250 MB per day. Business rates start at €0.80/GB for OST → PST.
Describe what you want, then continue to convert.
Exporting a Generation 2 VM from Hyper-V often yields a VHDX and a pile of XML you will not reuse. The disk is the part Densem converts. Hardware generation, Secure Boot and synthetic NICs stay a Proxmox configuration problem.
This page is that disk step. It is not a full VM importer and not VHD (the older format) — use the home converter for .vhd if that is what you actually have.
A dynamic VHDX can look small on disk and expand on convert. Differencing disks that still need their parent will fail identification or validation rather than invent missing extents.
We would rather stop than hand you a QCOW2 that boots to chkdsk forever.
After conversion we check that the output is a QCOW2 image, not an empty file and not a renamed VHDX. Guest jobs expire after delivery; keep your own copy.
Both can convert. Dynamic images may grow toward provisioned size during conversion — watch the Free size limit.
Same destination, different source container and Hyper-V-specific failure modes. Use the VMware guide for .vmdk.
A checkpoint chain is not a single guest upload. Merge in Hyper-V first, or use Business for a structured export.
