Windows 10: Enabling Secure boot causes system failure. How to fix?

Hello everyone,I have a computer with an MSI motherboard, and Windows 11. I have enabled secure boot through my bios TPM 2.0 already enabled. It clearly says BIOS Mode UEFI and Security Boot State: On. After saving and exiting the BIOS my computer booted to windows troubleshoot mode, and wont even boot to safe mode. Attempted to scan all my drives with chkdsk, and my computer sfc scannow. It also will not allow me to start a repair over the cloud nor locally. However, there seems to be a deeper problem I'm guessing was caused when I had to reset Factory Default Keys for secure boot. This is

:)

 

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.

 

BSOD - Kernel Security Check Failure

Hi Ashton,

There's a lot of reason for booting in to a BSOD, like problems with the driver for your display adapter or the
video output is being sent to an unexpected port. KERNEL SECURITY CHECK FAILURE error is usually caused by Memory or Driver incompatibility issues or corruption of system data.
In order for us to efficiently assist you, we just have few questions for you:

• Were there any changes made to your computer prior to the issue?
• What troubleshooting steps have you done so far?

Regards.