All articles
Troubleshooting
7 min read
2026-11-09
Valorant first-person overlay used while diagnosing a loader that will not draw

Valorant Cheat Not Working: VAN Errors and Patch Day Failures

VAN errors are not cheat errors. They are Vanguard refusing your firmware. Patch failures are a different thing. Identify which one you have before you touch anything.

"Not working" covers three unrelated problems in Valorant and they have three different fixes. A Vanguard error code a menu that will not draw and a game that launches but the account will not log in. Start by naming which one you have then work the relevant list.

The correct setup order and what Vanguard checks sit next to this article. Hardware bans have their own page.

Case 1: VAN9001 or VAN9003

These are Vanguard refusing to launch because TPM 2.0 or Secure Boot is off or because it cannot verify them. They have nothing to do with the cheat and they happen on vanilla installs too.

  • Secure Boot on in firmware. If the option is greyed out CSM or legacy boot is on and has to be turned off first
  • TPM enabled. PTT on Intel fTPM on AMD or a discrete module. Check tpm.msc reads ready
  • Virtualization enabled since the build needs it too
  • Reboot then confirm all three in Windows before launching
  • If Vanguard still refuses run the Riot Vanguard repair and reboot

Case 2: VAN 152

VAN 152 is the hardware ban error. The account is fine and the machine is flagged. Any account you log into on that PC hits it. No amount of reinstalling fixes it. Read the hardware ban article because that one has its own process.

Case 3: The menu will not draw

This is a build problem and it is usually a patch. Check the changelog first. If an update is posted install it. If the patch landed in the last few hours and nothing is posted wait. Then check your loader version. Old loader against new client gives you a window with no overlay. Then check Windows. A cumulative update can reset Memory Integrity or virtualization state. Then check the desktop. A new overlay capture tool antivirus or monitoring utility can hook the client. Then the config. Menu up and nothing drawing is a corrupt config. Delete it relaunch to rebuild defaults and reload profiles one at a time.

What not to do

Do not disable Secure Boot to fix a launch. Vanguard requires it and you land back on the same error. Do not run two loaders. Do not reinstall the stack during a patch window. Do not spam attach attempts. Do not assume a ban. A ban shows as a login failure or VAN 152 not as a menu that fails to draw.

FAQ

Questions about this page

Answers for this page. The FAQ page holds the rest.