I can confirm that this seems to be a bug in HyperV 2022 component.
We even cannot livemigrate via VMM 2019:
"The virtual machine "YYYY" cannot be migrated or cloned by VMM because the version "10.0.20348.320" of the virtualization software on the target host "xyz.XXX.de" is not compatible with the version of the virtualization software on the source host "10.0.14393.1358".
How can we avoid shutting down all the machines?
Edit:
source host 2016 server:
Get-VMHostSupportedVersion
Name Version IsDefau
Microsoft Windows 8.1/Server 2012 R2 5.0 False
Microsoft Windows 10 1507/Server 2016 Technical Preview 3 6.2 False
Microsoft Windows 10 1511/Server 2016 Technical Preview 4 7.0 False
Microsoft Windows Server 2016 Technical Preview 5 7.1 False
Microsoft Windows 10 Anniversary Update/Server 2016 8.0 True
target host 2022 server:
Get-VMHostSupportedVersion
Name Version IsDefault
Microsoft Windows 10 Anniversary Update/Server 2016 8.0 False
Microsoft Windows 10 Creators Update 8.1 False
Microsoft Windows 10 Fall Creators Update/Server 1709 8.2 False
Microsoft Windows 10 April 2018 Update/Server 1803 8.3 False
Microsoft Windows 10 October 2018 Update/Server 2019 9.0 False
Microsoft Windows 10 May 2019 Update/Server 1903 9.1 False
Microsoft Windows 10 May 2020 Update/Server 2004 9.2 False
Microsoft Windows 10 (Manganese) 9.3 False
Microsoft Windows Server 2022 10.0 True
All source VMs are hardwarelevel 8.0