VAN Errors in Valorant: What They Mean and How to Fix Them

Valorant has a peculiarity: it uses an anti-cheat that runs alongside Windows, Vanguard. That makes the game better protected and, at the same time, creates an entire family of errors that does not exist in other games.

The codes change over time and Riot adjusts the messages with each update. So instead of memorising numbers, it pays to understand the error families — because the fix is the same within each group.

Family 1: Windows 11 security requirements

The most famous errors in this group are VAN 9001 and VAN 1067. They appear when Valorant runs on Windows 11 and cannot find two security features Riot requires on that version of the system: TPM 2.0 and Secure Boot.

How to fix: both are enabled in the BIOS, not in Windows. TPM appears under different names depending on the manufacturer — on Intel boards it may be listed as PTT, on AMD boards as fTPM. Secure Boot has another requirement: it only works if the disk uses the GPT layout. If your PC was installed in legacy mode, it will need converting first.

This is the case where most people give up and reinstall Windows unnecessarily — the conversion exists and does not erase data, but it requires care.

Family 2: Vanguard did not start

This covers messages such as "Vanguard was not initialised" and codes like error 57 and 128. The game opens but refuses to enter a match.

Almost always the cause is the anti-cheat service not starting with Windows. The fixes, in order:

• Restart the PC. It sounds basic, and it is the fix in most cases — Vanguard only loads properly during system startup.
• Check whether another program is blocking it. Third-party antivirus software and hardware monitoring utilities are the most common conflicts.
• Reinstall just the anti-cheat. You can remove Vanguard and keep the game installed; next time you open it, it reinstalls clean.

Family 3: connection and session

These appear mid-match or when queueing, with messages about losing connection to the server. Here the origin is rarely the game.

• First check whether the problem is widespread, on Riot's official status page — no point touching your PC if the server is down
• Test with a cable instead of Wi-Fi, even if only for diagnosis
• Flush the DNS cache and restart the router
• If you use a VPN or route optimiser, turn it off and test — sometimes it is the cause

One important point: network jitter is worse than high ping in this game. A steady 60 ms ping bothers you less than a 25 ms one that jumps to 120. If the connection only drops occasionally, measure the variation, not the average.

Family 4: hardware ban

VAN 152 indicates a ban tied to the machine, not the account. There is no technical trick here: it is a case for Riot support. If you bought a used PC, be aware the ban may have come from the previous owner.

An honest warning

There is a lot of content telling people to disable Windows services en masse or use modified systems to "fix Vanguard errors". That usually makes things worse: the anti-cheat verifies system integrity, and a tampered Windows is exactly what triggers more blocks. If your problem started after using an aggressive optimiser, that is probably the cause.