Windows 10: No input control after enabling secure boot

This is a very weird problem I've been having. I have a MSI B450 Pro Carbon AC motherboard with TPM 2.0 capabilities and secure boot capabilities as well, and am on the latest version of the BIOS and Windows 11. I have UEFI, TPM 2.0, and Legacy device support enabled on the motherboard with no problems as far as I can tell and Windows recognizes the BIOS mode as UEFI too. My problem is, when I enable secure boot in my BIOS and boot into Windows, I lose input control. I still have input control in my BIOS and in Windows Recovery Environment. I'm starting to think my only option is ANOTHER cle

:)

 

Windows 8 Secure Boot Feature: Not So Secure?

So Linux is switching to secure boot also? Or they have to because of UEFI?

 

Windows 8 Secure Boot Feature: Not So Secure?

• Linux
• Linux
• Linux
• Linux
• Oh and OSX

Here is a statement from a Kernal Developer at Red Hat:

I'm not sure this exploits the legacy BIOS but rather it exploits the legacy boot method on MBR drives, injecting a signed key before the OS boots, which you are correct in that it has nothing to do with Windows 8. And the simplest fix would just be to require boot drives use GPT when Secure Boot is enabled in UEFI.

 

Windows 8 Secure Boot: Designed to Lock Out Linux?

from the article:

translation:

so if an oem manufacturer wants their firmware to enable secure boot with windows, it will be controlled and mandated by microsoft.

in order to allow secured boot, they will need to follow msofts rules. since the signed os bit is part of UEFI anyway, i'm not sure what rules microsoft will impose, but this is fancy speak trying to hide the fact that they WILL mandate and control firmwares that enable secured boot for windows.

not saying that does or doesn't make sense, they just deliberately tried to hide that point.