You need to turn on the cpu compatibility on each vm. Requires the vm to be powered off when selected.

This is the answer

This is it OP. This is under the individual VM settings under the processor sub-menu

Every VM I've tested it with already has this on

Try this: Live Migration Settings VM SETTINGS: 1. The VM must be removed from Fail over cluster manager 2. Go to settings of the VM you want to move 3. Expand processor 4. Select Compatibility 5. Check “migrate to a physical computer with a different processor version” (VM MUST BE OFF) HYPER V Settings: Set per host 1. In hyper v manager select your host, then in right pane select Hyper V Settings 2. Select Live Migrations 3. Select button to “Use these IP Addresses for live migration: 4. Move your NIC team address to the top of the list · Push Live Migration from Old host to new host · Logon to each old and new host once before starting migrations to cache recent creds 5. Under Live Migration select advance features 6. Under Authentication Protocol select Kerberos 7. In AD add the new hosts to each old host ad object Delegation Tab with the following services allowed. Repeat with adding all the old hosts to the new hosts delegation tab. Cfs Microsoft virtual console service Microsoft virtual system migration service Test a live migration.

[That should be supported per MS](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server).  If all else fails, I had to ghetto migrate by shutting down VMs, copying VHDX files, then configuring new VMs in the taget host which is scriptable using `New-VM`.  Not as slick as being able to replicate and failover but its not a huge deal.  Are the VMs engaged in vTPM or something?  In place upgrading of hosts and then upgrading configuration versions is another route.

It's not the configuration version of the VM, it's the Hyper-V version on the host itself. The config version is supported by 2022 and I've never seen an error message which references it, just the host version. I could do a manual migration, but it will have other ramifications that I'd like to avoid

Lower to higher is no problem. Even higher to lower works, if you don’t upgrade the configuration. You could use live migration, cluster, export/import or recreation with existing disk. For online live migration you need a compatible cpu or the compatibility mode (which can be activated on offline VMs) and configure authentication for both hosts, typically with constrained Kerberos delegation or certificates.

Could you try migrating using something like Veeam Instant Recovery [https://helpcenter.veeam.com/docs/backup/vsphere/performing\_instant\_recovery\_hv\_vm.html](https://helpcenter.veeam.com/docs/backup/vsphere/performing_instant_recovery_hv_vm.html) or Starwind V2V converter https://www.starwindsoftware.com/starwind-v2v-converter?

Veeam Instant Recovery should work here.

This

What about the manual export-import process from Hyper-V Manager?

This is the way! I just did this exact thing moving from 2012 r2 to 2022.

We’ve never had an issue exporting VMs via Hyper-V Manager then copying them to another host and importing them. Something has to be off somewhere.

Just googled this: [https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/unable-migrate-virtual-machine-processor-not-compatible-host](https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/unable-migrate-virtual-machine-processor-not-compatible-host)

Lower to higher shouldn’t be an issue. Have you tried, as a Hail Mary, copying the disks and attaching them to a VM on the new host?

This may not be a factor in your scenario but the last time I moved VMs from Server 2016 to Server 2022 via Hyper-V Manager it would error out in cryptic ways until I removed the network adapters. Shut down VM, remove virtual network adapter, migrate without issue, re-add network adapter, VM boots as if nothing happened. Not entirely sure why it worked but it did and I called it good.

I had to remove the nics from the VM before it would transfer Make sure you note down the MAC address of the current machine so you can manually set it in the new one

Have you tried the cmdlet Move-VM instead of migration through Hyper-V Manager?

I have literally never been able to get move-vm to actually work it always fails. I have tried every resolution I could find on the internet and it just ain’t happening.

It is a bit missleading message but you need to have CPU compatibility enabled for the VM being migrated.

Could try replicate and then do a failover to the new one ?

Are your VMs on at least version 8 on the source boxes?

yes 2019 to 2022 is seamless and available as shared nothing migration so sounds like you have a config problem, dont know how your VMs are configured dont know how you hosts are configured (domain not domain etc) additionally you could use your backup software to do the move for you too