Windows Server / Hyper-V & Failover Clustering
Check VM configuration compatibility before moving between hosts
A VM configuration version can prevent a move to an older host even when the VHD is accessible. Compare the actual supported versions.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-VM -Name 'APP01' | Select-Object Name, Version
Get-VMHostSupportedVersionRead the result
Run on the relevant hosts with Hyper-V tools. The VM version and supported-version list describe configuration compatibility, not full workload migration readiness.
Resolve and verify
Compare source and destination versions with the approved compatibility matrix. Select a supported migration or rebuild plan and validate guest and storage dependencies.
Before changing production
Do not upgrade configuration version casually; it can remove the ability to run the VM on older hosts.