Originally Posted by GridIroN
Originally Posted by kiwiasian
Had this error earlier today, fixed it by going into BIOS and enabling SecureBoot (was disabled for whatever reason). Fairly straightforward fix in my case.
Even if users want to use the feature, this doesn't fix the issue. Secure Boot essentially reads codes from the hardware to make sure machines haven't been tampered with. If you've built your computer, as 99.99999999999999999999% of OC.net users have, as opposed to bought it, you'll get an error telling you your graphics card isn't valid and the feature must be turned off, keeping the watermark.
Nope, it should work. I assume it uses the same math as encryption with private and public keys. The BIOS comes with public keys and checks a signature on everything that gets executed at boot. The signature can only be created by Microsoft as only they have the private keys. The security basically depends on those Microsoft keys staying secret.
When I experimented with it, I made a mistake and forgot to put the feature into Setup mode before installing a fresh Windows. The PC wouldn't boot after the installation. Apparently the boot loader area was blocked somehow, the Windows installation program couldn't put a boot loader on it.
Why that happened, I don't quite know. The way I understood it, it shouldn't have blocked writing a new boot loader onto the drive, just check if it's Microsoft code or a virus.