About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A virtual machine (VM) will not move to another host, and the migration wizard rates the target host at zero with the words "the processor is not compatible with the host". The two hosts differ in processor manufacturer, architecture, virtual server version or processor family. The SCVMM page that carries this message gives a workaround for a VM with a saved state: delete its checkpoints and shut it down before migrating. For VMM 2008 R2 it also names a VM property, "Allow migration to a virtual machine host with a different processor", which can be set only while the VM is stopped. Microsoft's separate Hyper-V page describes processor compatibility mode for moving VMs between hosts with different processors; that page does not mention this message.
Before you change anything, record the VM's current processor settings and make sure you have a backup or an export. Each fix below is marked with its impact and how to undo it.
What the error means
The message comes from a Microsoft page about the Migrate Virtual Machine Wizard in the System Center Virtual Machine Manager (SCVMM) 2008 console. It reads: "Unable to migrate the virtual machine" followed by the VM name, "because the processor is not compatible with the host" and the host name. The wizard shows it under "Rating Explanation", where the rating was zero. That page is about SCVMM 2008 and VMM 2008 R2, so it does not say what a current VMM or Hyper-V Manager prints.
For VMM 2008 R2 the same page says: "you can set the Allow migration to a virtual machine host with a different processor property to allow a virtual machine to run on a host that has a different processor version than the host on which the virtual machine was created. The virtual machine must be stopped to set this property." Its Important note adds that the setting "reduces the functionality of the virtual machine's processor", so it should be used "only when necessary". Microsoft's current Hyper-V page describes processor compatibility mode, the Hyper-V setting for moving VMs between hosts with different processors; the SCVMM page does not link the two.
According to that page, a VM with a saved state is checked before it can move between hosts, or be deployed from a library to a host. It compares the manufacturer (for example Intel against AMD), the processor architecture (x86 against x64), the virtual server version, and the family of the processor. If any value differs between the two hosts, "that host isn't valid to do a saved state migration".
The target host can still look healthy. The page lists "Overall Status: OK", "Connection status: Responding" and the box "This host is available for placement" as ticked. A healthy host does not mean a compatible one.
Microsoft's current page on Hyper-V says processor compatibility mode "limits the processor features available to a virtual machine (VM) to ensure compatibility when moving VMs between hosts or clusters with different processors". It applies to Windows Server 2025, 2022, 2019 and 2016, plus Windows 11 and Windows 10.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Hosts have different processor generations or families | Wizard rating is zero for one host; other hosts rate above zero | Compare host features with Coreinfo on each host |
| Different manufacturers (Intel and AMD) | The page says that host is not valid for a saved-state migration | Compare the processor line on both hosts |
| VM has a saved state or checkpoints | A saved-state migration is refused when the host checks fail | VM state and checkpoints with Get-VMSnapshot |
| Compatibility mode is off in a cluster of mixed processor generations | Microsoft's Hyper-V page says such a cluster needs compatibility mode left on for live migration to work | The Compatibility box in the VM's processor settings in Hyper-V Manager |
| Move from newer processors to older ones | The page says this move needs MinimumFeatureSet |
Compatibility setting currently on the VM |
Prove the cause before changing anything
These commands read information only. Run them in an elevated PowerShell on the Hyper-V host that holds the VM.
Get-VM -Name app01
Get-VMProcessor -VMName app01 | Format-List -Property *
Get-VMSnapshot -VMName app01
Get-VM, Get-VMProcessor and Get-VMSnapshot are documented Hyper-V cmdlets; their pages give the examples Get-VM, Get-VMProcessor TestVM and Get-VMSnapshot -VMName TestVM. Keep the output of the second command as a record of the current processor settings. Microsoft's Get-VMProcessor page does not show a compatibility property in its examples, so also record the compatibility setting where Microsoft's Hyper-V page shows it: in Hyper-V Manager, select the VM, then Settings, then Hardware, Processor, Compatibility, and note whether the box "Migrate to a physical computer with a different processor" is checked. A mode set with PowerShell or Windows Admin Center (MinimumFeatureSet or CommonClusterFeatureSet) may not be shown by that box, so write down who set it and which value, from your change records. The back-out steps below depend on this record.
Then compare what each host offers. Microsoft's page says you can run Coreinfo from Sysinternals on a host or a Windows VM, with .\Coreinfo.exe -f. Each line is a processor feature and "an asterisk (*) indicates that the feature is available". Run it on the source host and the target host and compare the two lists. A feature with an asterisk on one host and a dash on the other is the difference the migration is tripping on. Also note the manufacturer, since the page lists Intel against AMD as a mismatch.
If the VM sits in a cluster, list its role and the owner node:
Get-ClusterGroup
The Get-ClusterGroup page says this lists "the state and owner node of each clustered role".
Fix
Pick the fix that matches the cause. Do the safety step first on each.
Example (illustrative): at contoso.com.au, VM app01 runs on hv01, a node of an older cluster with an older Intel processor generation. A new cluster has a node hv02 with a newer generation. Moving app01 to hv02 works, and the compatibility page says a VM moved to a cluster with newer processors "receives the latest calculated capability of the destination cluster" when it is restarted. Moving it back towards older processors needs the minimum feature set, which the page says is set with MinimumFeatureSet. The administrator turns on compatibility mode for app01 while it is off, then migrates in either direction.
Fix A: turn on processor compatibility mode (VM must be off).
Safety step first: keep the processor and compatibility record from above and export the VM so you can bring it back.
Export-VM -Name app01 -Path D:\Exports\
The Export-VM page shows Export-VM -Name Test -Path D:\, which exports a VM to its own folder under that path. To bring the VM back from the export, the Import-VM page shows Import-VM -Path pointing at the .vmcx configuration file in the export folder, and a second form with -Copy -GenerateNewId that imports a copy under a new identifier.
Disruptive step: shut the VM down. This stops the services inside the VM and every user of it. Back-out: start the VM again with Start-VM -Name app01.
Stop-VM -Name app01
The compatibility page says the VM must be off: "Processor compatibility mode can't be enabled or disabled while the VM is running". Stop-VM shuts the guest down through its operating system.
Disruptive step: change the processor feature set of the VM. This hides newer processor features from the VM, so software that relies on them may run slower or fail. Back-out: if compatibility mode was off before (the box unchecked), stop the VM with Stop-VM -Name app01 and run Set-VMProcessor -VMName app01 -CompatibilityForMigrationEnabled $false, the disable command on Microsoft's compatibility page, then start the VM again; or uncheck the Compatibility box in Hyper-V Manager with the VM off. If a mode had already been set with PowerShell or Windows Admin Center, use the recorded value in the same cmdlet (-CompatibilityForMigrationEnabled $true -CompatibilityForMigrationMode with MinimumFeatureSet or CommonClusterFeatureSet).
If the VM is a clustered role, stop and start it through the cluster tools you already use for it, not with Stop-VM and Start-VM on the node alone, and do the change on the node that owns the role.
Set-VMProcessor -VMName app01 -CompatibilityForMigrationEnabled $true
Start-VM -Name app01
That command matches Microsoft's compatibility page: "To enable processor compatibility mode with the default value of the minimum feature set for migration". On Windows Server 2025 for VMs with configuration version 10.0 or later, the page also describes dynamic mode, -CompatibilityForMigrationMode CommonClusterFeatureSet, which uses features common to all cluster nodes. The page's guidance is to enable compatibility mode only during migration and disable it afterwards, with one exception: "If you have a cluster with different processor generations, you need to leave processor compatibility mode enabled for live migration to work."
Fix B: VM has a saved state or checkpoints. The workaround on the SCVMM page is: "you can delete the Snapshots/Checkpoints and shutdown the VM. Once you do this, you should be able to migrate it from one host to another."
Safety step first: export the VM, as in Fix A, because a deleted checkpoint cannot be brought back.
Export-VM -Name app01 -Path D:\Exports\
Disruptive step: shut the VM down. This stops the services inside the VM and every user of it. Back-out: start the VM again with Start-VM -Name app01.
Stop-VM -Name app01
The Stop-VM page describes the example as shutting a VM down "through the guest operating system".
Risk: deleting a checkpoint removes the point you could return to. There is no way back from a deleted checkpoint except the export you took above. List first, delete by name, never with a wildcard you have not listed:
Get-VMSnapshot -VMName app01
Remove-VMSnapshot -VMName app01 -Name "Before patching"
The Remove-VMSnapshot page shows Get-VM TestVM | Remove-VMSnapshot -Name Experiment*, which deletes every checkpoint whose name starts with that text, so the exact name above is safer.
Fix C: different manufacturers. The Windows Admin Center option on the compatibility page says the minimum feature set lets you move a running VM "to other Hyper-V hosts outside the cluster as long as they have the same CPU manufacturer". A move between Intel and AMD is not covered by that sentence, and the page describes no way across two manufacturers.
Confirm the fix
- Open the VM's processor settings in Hyper-V Manager again, as in the record step. The Compatibility box should show the new setting. Rerunning
Get-VMProcessor -VMName app01 | Format-List -Property *and comparing it with your saved copy shows whether anything else changed; Microsoft's cmdlet page does not document a compatibility property, so rely on the box for the setting itself. - Run Coreinfo inside the VM. The page says that with compatibility mode on, "some features aren't available (indicated by a dash -)" compared with the host.
- Risk: the migration in this step moves the running workload to another host; do it in a maintenance window. Migrate the VM to the target host and confirm it is running there with
Get-VM -Name app01. To undo it: migrate the VM back to the source host, which the compatibility setting you just made allows.
What to watch afterwards
- Applications that use newer processor instructions, such as encryption or analytics software. Compatibility mode removes features from the VM, so measure response times on the VM before and after.
- A VM moved from a cluster with older processors to newer ones receives the newer capability on its next restart, according to the page. If you later move it back, you need the minimum feature set again.
- New hosts added to the cluster. Compare their Coreinfo output with the existing hosts before you plan a live move.
Read next
Related articles you may want next.
- CloudLeaving VMware for Hyper-V: failover clustering, CSV and live migration in depthHow failover clusters decide who survives, how Cluster Shared Volumes handle I/O, what limits live migration, and which conversion route fits.Read article
- VMwareCannot enable EVC: the host or a powered-on VM uses features above the EVC modeEVC will not enable? Find the running VMs above the EVC mode, the vCenter VM in the cluster, or the host CPU and BIOS features the mode needs.Read article
- TroubleshootingFailover cluster node in Quarantine: why Windows keeps it out and how to clear itA cluster node shows Quarantine and will not host VMs. Read the events, fix the cause, then clear quarantine with Start-ClusterNode -ClearQuarantine.Read article
Risks and limits
These commands have not been run or lab-tested.
The error text comes from a SCVMM 2008 page. If you see a differently worded message in current Hyper-V Manager or VMM, the same causes may apply, but Microsoft's page does not say so. The compatibility mode page does not state a performance figure, so any slowdown has to be measured on your own VM. Microsoft's page on compatibility does not cover moves between Intel and AMD.
Sources
- Unable to migrate virtual machine from one host to another — Microsoft Learn, page dated 2026-02-12, accessed 20 November 2026
- Configure processor compatibility in Hyper-V virtual machines — Microsoft Learn, page dated 2025-08-11, accessed 20 November 2026
- Set-VMProcessor — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-VMProcessor — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-VMSnapshot — Microsoft Learn, date not shown, accessed 20 November 2026
- Remove-VMSnapshot — Microsoft Learn, date not shown, accessed 20 November 2026
- Export-VM — Microsoft Learn, date not shown, accessed 20 November 2026
- Import-VM — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-VM — Microsoft Learn, date not shown, accessed 20 November 2026
- Start-VM — Microsoft Learn, date not shown, accessed 20 November 2026
- Stop-VM — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-ClusterGroup — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .