Windows 10: Motherboard change to support Secure Boot

I recently upgraded my Motherboard for one that supported secure boot, I have made appropriate changes in EUFI Bios, the system booted and win activated.MS info shows Bios Mode as Legacy.Is a win10 repair or clean win install required to enable EUFI bios mode?And if so I may have a problem, my Win 10 Pro was via a free MS upgrade from win7 many years ago, and as such when I access my MS Account, of which for some reason I have two on one it shows a 2016 Access component as a service, but nothing else. And nothing on the other, In Devices on both it shows Win 10 Pro but no serial# and gives th

:)

 

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.