Riot Vanguard Is Being Blamed For Crashing Deadlock And Locking Deadlock.exe

On May 6, 2026, @nealCS put a fresh match under one of PC gaming’s oldest gasoline cans: kernel anti-cheat. The post pointed to a Reddit report claiming Riot’s Vanguard anti-cheat crashed Deadlock, then kept a lock on Deadlock.exe so Steam could not repair or reinstall the game.

That is the kind of sentence that makes every PC player in the room immediately check what is running in the tray.

The underlying report came from Reddit user u/Akita_Attribute on r/DeadlockTheGame, with a parallel thread also appearing on r/riotgames. The user said Deadlock crashed mid-match, Steam got stuck showing content as downloading, and a reinstall attempt failed near the end with a “Content File Locked” error. Their claimed diagnosis was that Riot’s vgc.exe service was holding the file handle. Their claimed fix was blunt: kill the VGC service or reboot, then repair the Deadlock install.

There are two important caveats. First, this is still a player report, not a confirmed Riot or Valve incident report. Second, file locks can happen for boring software reasons. A process holding a handle does not automatically prove malice, sabotage, or the funniest possible conspiracy theory in the replies.

But this particular claim landed because Vanguard is not just any background program. Riot’s own support page describes Vanguard as security software made of a client plus a kernel-mode driver, and Riot’s security team has separately explained that the driver runs at startup so cheats cannot load first and hide from it. Riot’s support docs also say Vanguard can be disabled from the system tray, but turning it back on for Riot games requires a restart.

That is the tradeoff players are arguing about. Riot frames Vanguard as a competitive-integrity tool built to fight cheats at the level modern cheats operate. A lot of players hear something simpler: software installed for one company’s games can still be present when they are playing somebody else’s game, and if something goes wrong, they are the ones staring at Steam’s repair button while their match history catches fire.

The Deadlock forum picked it up almost immediately. A thread titled “Apparently Vanguard tries to smother Deadlock” linked the Reddit post and wondered whether Vanguard might explain some performance reports with no obvious cause. That is not proof either, but it shows how fast a single credible-looking technical post becomes community lore when it fits a fear people already had.

The comments did the rest. Some players said they had both Vanguard and Deadlock installed with no issue. Others claimed Vanguard had caused unrelated problems with development tools, other games, or system stability. Then the conversation did what Deadlock conversations do: it escalated from a file-lock report into VAC comparisons, Riot distrust, Valve tribalism, and the usual “delete everything from the company you hate” sermon.

The real story is not that Riot definitely broke Deadlock on purpose. There is no public evidence for that, and pretending otherwise turns a useful technical warning into forum cosplay. The real story is that kernel anti-cheat has a trust problem that never actually went away. Every weird crash becomes a referendum. Every locked file becomes a character witness. Every workaround involving Task Manager makes the software feel less like protection and more like a roommate with admin privileges.

For affected players, the practical takeaway is narrow: if Deadlock crashes and Steam starts throwing “Content File Locked” or stuck-download behavior, Vanguard’s VGC service is now one of the things worth checking. For everyone else, the takeaway is bigger and more annoying: the PC anti-cheat arms race keeps making games feel like they are fighting each other on your machine.

Deadlock already had enough drama inside the match. It apparently did not need Riot’s background security software becoming a side lane.