StarWind Software

I am converting a VM from a Hyper-V 2012R2 to a Hyper-V 2022. The VM itself was also 2012R2 and worked with .vhdx files. After the transfer to the new Hyper-V i saw that the .vhdx files were converted to .vhd. Is that normal?

Hi,

When converting a VM it looks at its boot loader and automatically picks generation. Please convert Disks separately to avoid the them getting VHD.

That means that i convert the vm (from 2012 Hypervisor) to its new destination (2022 Hypervisor). That includes automatically the conversion of the old vhdx files to vhd and transferring that to the new hypervisor. After that i delete these vhd files and convert the vhdx files in origin to vhdx which will then be transferred to the newly created vm?

You can convert the disks and recreate the VM in the destination.

Look at the VM configuration on the original Hyper-V 2012 R2 host. Were the virtual disks .vhdx there?

StarWind V2V can convert VHDs too.

It's not uncommon to see .vhd files after migrating from an older Hyper-V version. The automatic conversion to .vhd can happen if the VM's generation isn't set correctly. Check the VM settings post-migration to ensure everything's configured as needed.

VM Gen is set automatically during conversion and depends on the boot option tht source VM has.

@golf hit Hyper-V 2022 normally keeps disks in .vhdx, so seeing them converted to .vhd means the migration tool or export/import process likely forced a legacy format rather than preserving the original virtual disk type.

When converting the VM, the output format can be VHD. We are working on it.
To convert to VHDX with the current build, you can convert individual disks.