Vanguard and Valorant Cheats: What It Checks and What It Does Not
Vanguard is the reason Valorant cheat setup starts in BIOS. What it actually checks why it demands TPM and Secure Boot and where the real risk sits.
Vanguard is the most written about anti-cheat in gaming and most of what is written is either marketing or panic. It is worth knowing what it actually does because in Valorant the anti-cheat decides what kind of cheat is even possible.
The build and requirements and the setup article are the practical companions to this one.
What it is
A kernel-level driver that loads at boot with Windows before Valorant and before most of your other software. Kernel level means it sits below user mode where it can inspect things a normal process cannot. It also runs continuously rather than only while the game is open which is why people notice it in Task Manager.
Why it demands TPM and Secure Boot
Both are Windows 11 requirements so on a compliant machine they are already on and invisible. They exist to establish a trusted boot state meaning the system that Vanguard is inspecting has not been tampered with before it started. Riot support pages are blunt about it. If either is off on Windows 11 Valorant will not launch and you get VAN9001 or VAN9003. There is no workaround and no override.
That is also why the cheat setup for Valorant begins in firmware. Our build needs HVCI Core Isolation TPM and Secure Boot because Cloud DMA does and Vanguard needs two of the four anyway. One checklist serves both.
What it catches
- Signed and unsigned drivers loading into the kernel
- Process handles and memory reads from user mode
- Injected modules and manual mapping
- Mouse input patterns which is how aimbot humanization gets caught rather than how the aim looks
- Hardware fingerprints which is how hardware bans happen
That last one is the important one. Vanguard builds a composite fingerprint from disk serials motherboard UUID MAC addresses GPU identifiers and more and it persists after a format. Formatting does not clear a ban and a VPN does not either. Hardware bans cover the recovery path. The HWID spoofer is the matching product.
Where it is weaker
It is a detection race not a wall. Vanguard and cheat developers update against each other. Cheats work then a patch breaks them then they are updated. That cycle is the actual state of play. Reads that happen outside the game process are harder to see than reads inside it which is the whole reason hardware DMA and now cloud based DMA exist. Our stack runs through Cloud DMA for exactly this reason: reads happen in a Hyper-V environment rather than inside the client.
The honest risk statement
No cheat is permanently safe. Ours describes active maintenance and updates within hours of patches and both are true as descriptions of maintenance. Neither is a guarantee for the next Tuesday. Read the product page before you play after a patch. Do not queue ranked on an out of date loader. Do not play eight hours a day every day on the same account. Do not run a free build alongside a paid one.