After being pinged by Niall Brady on X (Twitter) today, I started to play around a bit with Hyper-V in Windows 11 24H2 on a few ARM64 Devices from Microsoft, HP, and Lenovo. Here are my notes:
1. Windows 11 24H2 has a new guest VM configuration version: 12.0, compared to 11.0 in Windows 11 23H2. I haven't yet found any documentation on what really changed between version 11 and 12, but I did notice a few new parameters in the Windows 11 24H2 Hyper-V PowerShell module (compared to Windows 11 23H2). If anyone knows what they are for, please let me know 🙂
- Command Debug-VM has new parameter: ManagementVtl
- Command New-VM has new parameter: SourceGuestStatePath
- Command Set-VMMemory has new parameter: BackingType
- Command Set-VMProcessor has new parameter: PhysicalAddressWidth
2. Virtual TPM finally works when using Hyper-V on ARM64 devices, but only for new VMs. The VM fails to boot if enabling TPM on an existing VM, even after upgrading their configuration version. It fails with Event ID 12030 (Hyper-V-Worker-Admin event log).
3. After upgrading an ARM-based Hyper-V Host to Windows 11 24H2, you can't restore any VM with saved state. You must discard the state and boot up "clean" again. If not, you'll get an error message saying: The virtual machine 'VM NAME' is not compatible with physical computer 'HOST PC NAME'
4. Apparently WinNAT is now supported also for ARM (thanks Marc-André Moreau for letting me know).