Deadlock’s Kernel Anti-Cheat Panic Was Really About What Other Games Were Already Doing To PCs
Deadlock never needed to ship its own kernel-driver disaster for players to panic. By May 2026, cross-game anti-cheat conflicts and FACEIT-style requirements were already doing the rhetorical work for it.
"notorious piece of shit kernel level anti-cheat Vanguard… has been reported to be blowing up Deadlock"
Deadlock’s kernel anti-cheat story is messy because it was never just about Deadlock itself. It was about the entire atmosphere around invasive anti-cheat software by 2026.
The clearest flare-up came in early May, when a Vanguard-related complaint spread from Reddit into Valve’s own Deadlock forum. The allegation was that Riot’s kernel-level anti-cheat had locked up or damaged Deadlock files after a crash, turning a theoretical argument about deep system access into a concrete cross-game headache.
FACEIT’s own support documentation only reinforced the vibe. It confirmed that its anti-cheat uses a kernel-mode driver loaded at boot, which is exactly the kind of sentence that makes players who already feel trapped by modern PC gaming instantly more hostile.
So the real story was not Valve secretly forcing a new driver onto machines. It was the growing belief that competitive PC games keep asking players to trade system trust for marginally cleaner matches, and Deadlock was never going to escape that argument once people started imagining the same future for it.