Riot Games pushed a May 2026 update to its Vanguard anti‑cheat that blocked DMA cheating devices and, according to reports, left some of those devices unusable until owners reinstalled their operating systems.
The change strengthened Vanguard’s IOMMU enforcement, and users and observers say the tightened checks caused FPGA‑based cheat setups paired with physical or emulated SSDs to stop working — sometimes appearing to “brick” the attached hardware. Riot punctuated the move on X with one-line gloating: "Congrats to the owners of a brand new $6k paperweight."
Reports from players who run such hardware said the apparent damage was reversible; reinstalling Windows and, where applicable, flashing different FPGA firmware restored the cards and SSDs to service. A technology outlet that examined the incident said ordinary Valorant players were not affected and that only users running cheats via special FPGA hardware and associated SSDs experienced problems.
Vanguard is a kernel‑level anti‑cheat that loads at boot and runs 24/7 in the background; over the years, cheat developers found another use for DMA cards to bypass anti‑cheat software by moving cheat code off the PC and into external hardware. Those hardware‑level cheats rely on PCIe DMA devices loaded with custom FPGA firmware and paired with a physical NVMe or SATA SSD, or an emulated SSD, so the game client cannot see the cheat code directly.
By tightening IOMMU enforcement in May 2026, Riot closed a path that those DMA devices used to reach game memory. The enforcement change appears to have either blocked the devices from attaching cleanly or triggered firmware and SSD behaviors that made the devices stop responding until the host system was rebuilt. The outlet that reviewed the issue said damage to FPGA firmware or associated drives could be reversed by reflashing firmware and reinstalling Windows, and that normal, non‑cheating players continued to play Valorant without interruption.
The episode sharpened long‑running complaints about Vanguard’s design. Some users called the anti‑cheat intrusive and described it as borderline malware because it operates at kernel level from the moment a PC boots. That criticism collided with Riot’s public posture: the company celebrated the disruption to cheating hardware even as the community debated the ethics and risks of software that watches systems 24/7.
That collision is the story’s tension. Riot aimed a technical countermeasure at an entrenched form of cheating and appears to have degraded the specialized hardware that enabled it. But the approach also risks collateral consequences and fuels a principled argument about whether anti‑cheat software should have such deep access to personal systems. The picture is messier still because the technical fixes users report — firmware flashing and OS reinstalls — suggest the company’s action did not permanently destroy hardware, only raised the bar to get it running again.
The immediate outcome is clear: the May 2026 update will make it harder for DMA‑based cheats to operate, at least until cheat developers adapt their hardware. For players who use or rely on such hardware, the practical step is recovery by reflashing firmware and reinstalling Windows, which observers say returns the devices to life. For Riot and the broader PC gaming community, the update hardens the frontline against a specific cheat vector while guaranteeing continued debate about the cost of that hardening.
In plain terms, Riot’s update will likely curb this corner of the cheat market — but it does so by leaning on an anti‑cheat that runs 24/7, and that tradeoff ensures the controversy over how much access anti‑cheat software should have is not going away.
