Forum Discussion
Server 2022 boot loops after Hyper-V role installation
Yes, i understand it is no official certificated hardware for Server OS although the processor meets all requirements to theoretically be able to run it, Especially as you consider the fact it worked fine using Server 2022 RTM build but no longer works after installing CU's is kinda weird, don't you think? Also I had no issues with enabling Hyper-V whatsoever when using Server 2019.
Same as with the Core isolation toggle (which also depends on Hyper-V components), worked fine on RTM but after installing CU's the toggle is reverted on bootup. Driver verifier reports no incompatible drivers.
You can try asking the hardware manufacturer if they have plans to certify for Server 2022, beyond that there's not much else you can do.
I don't think certification helps that much on it own, as it looks like a bug or something....how else you would explain everything worked as supposed to when using RTM build?
The other guy i linked to above has exactly the same problem with a Atom based processor, eg: worked fine on RTM but no longer after installing CU'sIt looks a bit like a similar issue some DELL systems had on Server 2019, https://social.technet.microsoft.com/Forums/en-US/3d7f61c1-807d-4ecc-b70e-496f4ba74c83/windows-server-2019-datacenter-boot-loops-after-enabling-hyperv?forum=winserverhyperv
https://www.reddit.com/r/sysadmin/comments/ae23zc/hyperv_2019_and_uefi_boot_loop_fix_yet/
Regardless the hardware has no support for Server 2022. Your only recourse is via the hardware manufacturer.
