Applies to: Windows Server 2019, Windows Server 2022, and Windows Server 2025.
Processor compatibility can support migration between different CPU generations at the cost of hiding newer processor features.
Prerequisites
- Administrative access and an approved change window.
- A verified backup and documented rollback plan.
- A pilot environment or low-risk target for validation.
Step-by-step procedure
- Confirm migration requirements and cluster support.
- Shut down the selected VM.
- Enable migration compatibility for the processor.
- Start and test the workload before migration.
Commands
Stop-VM -Name "APP01"
Set-VMProcessor -VMName "APP01" -CompatibilityForMigrationEnabled $true
Start-VM -Name "APP01"
Get-VMProcessor -VMName "APP01"Verification
The VM starts normally and the compatibility property is enabled before migration testing.
Rollback
Shut down the VM and disable the compatibility property if it is no longer required.
Security notes
- Use least privilege and record the change.
- Review relevant event logs after implementation.
- Test before production rollout.
Understand the CPU boundary before scheduling migration
Processor compatibility masks selected CPU capabilities so a VM can move between supported hosts with differing processor generations. It does not convert an Intel VM host into an AMD-compatible live-migration target or guarantee that every CPU and application combination is supported. Validate the host pair and migration method first.
The configuration in the example requires a guest shutdown. Coordinate application downtime and confirm a usable guest backup. Record the previous processor settings and review software that depends on particular instruction sets or vendor-supported CPU features.
Newer Hyper-V versions provide additional compatibility modes in supported cluster scenarios. Do not copy a parameter for that mode onto a host or VM configuration version that does not support it. Consult the current host documentation and Get-Help for the installed module before extending the basic example.
After enabling compatibility and starting the VM, test the application and perform a controlled migration during the pilot window. Verify the guest on the destination and test the return path. Restore the original setting only through an approved shutdown and after considering where the VM may need to move next.
Reference: Microsoft processor compatibility configuration.
Related resources
Canadian Windows VPS and RDS hosting: managed Windows VPS hosting. Refer to Microsoft Windows Server documentation.