Windows 10: Lost Windows activation after secure boot

A while ago about 5-6 months, I was suggested to enable the 'secure boot' option to fix an issue I had with launching a game called Valorant that suddenly stopped working because apparently, it was a solution to my crashing - and it was. I had no problem after. I mean, after all, the option would protect my computer more, I guess.Yesterday, in the evening, my BIOS settings were completely fine, and I safely turned off my computer, additionally, I did not download any files externally except for trusted software like Xbox or Steam. Today, an unusual happened this morning - the BIOS configurat

:)

 

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.