Windows Server 2022 - devices not booting when Secure Boot enabled (KB5022842)

As always, I am a little late to the party, but here goes nothing. Running into the boot failure issue with Server 22 STD bare metal and Hyper-V installation boot failure when KB5022842 is present at the time Hyper-V is loaded or when the KB is loaded after Hyper-V is already present. Yes, I understand that Server OSs are not meant to run on certain hardware platforms. In my case the ASUS Prime B760M-A D4 (Bios 0807) and Prime B660M-A D4 (BIOS 2212). Both with (2) 2TB SATA III HDD in a RAID 1 using Intel VMD. These are for small businesses that want server class functionality on a budget. I have a long history of building "servers" with Hyper-V on non-server platforms without significant problems. I have done the dance with Intel and ASUS and they have both come back with, we don't test things that are not in the recommended build parameters. OK, I get that. I am not blaming MS for floating a bad update - yet. So, Alban1998, you can kindly leave your unhelpful comments at your keyboard. For the rest of us who live and work in the real world of servicing budget-minded clients, we need these non-standard builds, that have worked in the past, to continue to work going forward. That is why we have these discussions. When I started experiencing this issue, I thought it had something to do with the new Intel VMD RAID (Sub-set of Intel Virtual Raid on Chip - VRoC) for non-Xeon systems because I saw it first on the B760 chipset. Then, I saw it on the B660 chipset and have heard others comment about it on the 500 series chipset. Further testing and reading lead me to MS updates, specifically KB5022842. I still have a lingering suspicion that something in KB5022842 is glitchy with the IRSTe and VMD drivers as they relate to Hyper-V, but I cannot put my finger on anything. I suspect that because of where the boot failure happens. My system will POST, hand-off to the OS and then hang at the blue window splash screen like it is hanging on a driver. From the article I have read though, it seems that secure boot and this KB are the oil and water we are dealing with. I suspect that MS is waiting to see how much neg press is generated by this issue and the technical feed back from various event logs being posted before they do anything. This is going to affect a lot of small business operations that recently dropped thousands of $s to upgrade their 12R2 systems only to have their "server" crash due to an MS update. The March updates are out, So I will see if there is a fix in the mix.