Community Manager
Yes... I get the whole idea of stopping drivers that aren't signed by Microsoft from being installed. But again.... SecureBoot is only involved with preventing malicious code from being executed during the boot sequence.... Which I'm pretty sure is well before any sort of driver initialization would make it remotely useful. It's not a Windows-based security measure, but more of a hardware one (seeing as it's a BIOS setting, not a "feature" of Windows that needs to be installed or anything)
Sabather I've read that if cheat developers can get the Windows kernel to load their driver first during the boot process. Then their driver gets control over all the other drivers that load after it, including anti-cheat drivers.
It's basically a race to see who can get their driver to load first during the boot process. The cheat driver or the anticheat driver.
Whichever driver loads first wins and has control over all the drivers that load after it.
