@Microsoft Which change did you make in Settings ???
I do not see any change: Secure boot, TPM2, hardware virtualization, DMA protection for VBS, HSTI info from tyhe UEFI BIOS are still NOT recognized at boot...
And the same message is there: Windows still reports FAKE information in Security Settings: when we perform the actual check (including with your ADK), all is OK, including processor capabilities !
FIX YOUR BUGS in your compatibility checker program used before installation (making false assumptions NOT based on actual testing) and in your new version of "booloaderfw.efi" for Windows 11 (that you installed in the GPT ESP partitition).
I just wonder if Windows 11 will boot (correctly) with the latest (supported) version for Windows 10 of this broken "booloaderfw.efi".
Or may be you've forcibly disabled some settings arbitrarily in my registry for your test flight in the Dev channel, so that the PC looks to be "non compatible".
Also I have not seen any change related to the new (FAKE) "requirements" for Windows 11 in the ADK (still published for Windows 10). How do you think that manufacturers can pass the WHQL and certifty their machines as being "Windows 11 compatible" ? Just by trusting them and requiring them to pass the test again so that they get a new endorsement signature by Microsoft Labs (actually not performing ANY test?)???
Note that my machine also works perfectly with vmWare on Windows 11, with its windows 10 compatiblity drivers (Hyper-V however crashes now when trying to boot any version of Windows).
Could "vmWare Workstation Pro" causing this apparent compatibility problem?