Secure Boot Unsupported

skitlesas · November 1, 2021

Hello. I just installed Windows 11. And I have problems with Faceit:

In the Windows 10. I don't get this error.. I tried to fix it myself. Like convert an MBR disk into a GPT disk. but I still get Secure Boot State Unsupported and in BIOS, I can't find the function to change Secure Boot..

LogicalDrm · November 2, 2021

Your hardware is too old essentially. Besides of your CPU being 5 generations older than what Win11 officially supports, your mobo is so old (or low-end), it doesn't even have slot for adding TPM module.

Go back to Win10 and hope they relax requirements. Or save up for upgrade. Those are your options.

GoodBytes · November 3, 2021

On 11/1/2021 at 6:04 AM, skitlesas said:

Hello. I just installed Windows 11. And I have problems with Faceit:

In the Windows 10. I don't get this error.. I tried to fix it myself. Like convert an MBR disk into a GPT disk. but I still get Secure Boot State Unsupported and in BIOS, I can't find the function to change Secure Boot..

While you have a 2nd gen Intel Core i series CPU, where UEFI was (finally) introduced to DIY space in masses, your motherboard doesn't come with a UEFI. Being the early days of UEFI, only the more premium boards comes with one. As your system doesn't support UEFI, it doesn't support Secure Boot.

Your game anti-cheat wants Secure Boot to run under Windows 11. Secure Boot, ensures to the game anti-cheat system that the OS is really the only one that has supervisor role at the CPU level (means it can do what it wants.. allowing the OS to.. well.. operate the system, hence its name). CPUs are by nature dumb, the first piece of software is loads, assumes it is the OS. This is why you have malware of type: rootkit, which took advantage of this flaw by setting itself as the first thing to boot, and then loads the OS and passthrough all calls, so the OS has no idea something is wrong. It can check, but the rootkit, having CPU visor role, can play with the OS memory and code, and fool it to not detect anything, it also fools A/Vs and all other security software, and typically steal everything of value from your system. No way to detect it. Secure Boot aims to add a barrier to make it very hard for rootkits to install themselves. Your anti-cheat software wants to be sure that no cheating device rootkit isn't used on the system to fool the OS, and game (and hopefully that is what where it stops, for our own sakes).

Allingham · November 9, 2021

Hi, I'm just coming from a system much like yours: i7-2600K on Gigabyte: GA-Z68XP-UD3.

So, same generation as you, but a more premium motherboard. This motherboard originally came with legacy BIOS but was upgradable to UEFI. I did the upgrade way back and have been running UEFI boot ever since. BUT, I was never able to enable Secure Boot in the UEFI bios. That would completely break the system and I had to removed my graphic card and reset CMOS jo to get into the BIOS again. My point here being that the Secure Boot feature in this early Gigabyte motherboard was very bad! So, you should not get your hopes up ever getting it to work on you machine.

FYI, my point about removing the graphic card: If you have an old graphics card like Geforce 600 series or older, they don't have UEFI OPROM with makes Secure Boot impossible. A requirement for Secure Boot is that all PCIe devices have an UEFI OPROM on board.