Keep VM configuration upgrades separate from Hyper-V host upgrades

Source facts

Microsoft explains that moving or importing a VM onto a newer Hyper-V host does not automatically upgrade its configuration version. Keeping the older version preserves the documented ability to move the VM back to an older host, while some newer features require an explicit upgrade. The source provides Get-VMHostSupportedVersion to inspect supported versions. An upgraded VM configuration version cannot be downgraded. Its upgrade procedure starts by shutting down the virtual machine. Microsoft Learn.

Applicability

Inventory the current VM configuration version and every host that might need to run it, including recovery destinations. Check those hosts against the source support table. Make the configuration-version decision separately from completing the host operating-system upgrade.

DSE recommendation

For each VM, write down the feature that requires an upgrade and the older-host return path that may still be needed. Have the virtualization and workload owners agree when that fallback requirement ends. Schedule the required shutdown and preserve a recoverable pre-change record. Do not advance every VM automatically just because a newer host offers the option.

Verification

After the approved upgrade, verify the reported configuration version and the specific feature that motivated it. Validate startup and the representative application transaction. Compare all intended placement destinations with the accepted compatibility plan, and document any destination that is no longer part of that plan.

Official references

Microsoft Learn: Upgrade virtual machine version in Hyper-V on Windows or Windows Server. Source reviewed September 8, 2026.