Windows 10: I cant activate secure boot and I cant find KeyPK in BIOS

Hello. Me and my friend want to play Valorant but he can't use it because his secure boot isn't enabled. So I took him to BIOS and we couldn't find Secure Boot anywhere unless we searched it up. We searched for Secure Boot in BIOS and tried to enabled it but it says: "Secure boot can be enabled when system is in user mode. Repeat after re-enrolling platform KeyPK" So I have tried to solve this problem so many ways and with so many different articles/websites. I can't find anything that says Change Platform Key or anything. Please help. I want to enable secure boot.

:)

 

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 Feature: Not So Secure?

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

 

CSM/Secure Boot BIOS setting change causes Windows 8 to de-activate

I have a Windows 8 BIOS (non-UEFI) installation on a motherboard with UEFI and Secure Boot support. The installation was running smooth for over a month until I was tinkering with the Secure Boot settings. I changed CSM from "enabled" (which lets it gel with non-UEFI devices) to "auto"; and although Secure Boot was disabled, it had some default platform keys loaded. I cleared those keys.

The following reboot took longer than usual, and to my horror, Windows was no longer activated. Activate by Internet doesn't work because I've used up my key across two motherboards (unlock limit), and Microsoft India support has a lazy Monday-to-Friday work week. Is there anything I can try in the meantime? I've tried setting CSM back to "enabled," and loaded whatever default Secure Boot keys the setup program had.