Not needed. Just put the VMs and the VHD in the same place they were, then stop the vmms service, then delete \ProgramData\Microsoft\Windows\Hyper-V and copy the same folder from the old system to the new one. start vmms service, and recreate the vitual switches with the same name you had in the old system and you're done. You don't even need to reboot.
25398.345 was released as CU only, windows11.0-kb5029518-x64.cab is missing is it possible to get it somehow? SHA-1 is b2ce05c465ee8e7be36ff5cab4bf31167efa0b31 maybe it's available on WSUS? @abbodi1406
Nice to share, But.. Do I really NEED it?? nah.. I already have Window Server 2022 Standard (Full Version paid License..) So, on my free time I will play around.. ATGPUD2003
It's not like you don't need a car because you own a cruise ship. There are use cases where HCI is invaluable.
Just delete the HciSvc service and nothing happens. BTW the bread and butter of HCI is to use it as a VM guest, not host (to make a [WIFI] router, a domain controller a file deduplicated storage on unsupported system and so on, using small storage space, and relatively small amount of RAM. As discussed earlier there isn't any other no GUI (Core, Acore, HyperCore) server that came with a such complete list of roles and features)