Valorant VAN Error Codes

Valorant VAN error codes – quick help

Nothing is more frustrating than eagerly wanting to launch Valorant and being met with a cryptic VAN error code instead. Whether the game refuses to start, kicks you out mid-match or denies the connection – behind almost every one of these codes lies a specific, often easily fixable cause. On this page you’ll find a big overview of the most important Valorant VAN error codes, each with its cause and the matching solution. Use the error-code finder above to enter your code directly – or read through the general solutions, which cover the majority of all problems.

The goal of this page is simple: to get you back into the game as fast as possible. That’s why the solutions are deliberately kept short and practical. For the especially common code VAN 1067 we also have a detailed guide of its own, which we link to at the right spot.

What is Vanguard – and why do VAN errors appear?

The abbreviation "VAN" stands for Vanguard, Riot Games’ own anti-cheat system. Vanguard runs deep in the system and makes sure that nobody plays Valorant with cheats or manipulations. For this to work, Vanguard places certain requirements on your PC and monitors whether everything runs cleanly. A VAN error code is basically Vanguard’s way of saying: "Something is wrong here." The causes can be divided into a few large groups:

• Connection problems: Vanguard or the client can’t establish a clean connection to the Riot servers (e.g. VAN 0, VAN 1, VAN 68).
• PC security settings: On Windows 11 Vanguard requires TPM 2.0 and Secure Boot to be enabled (e.g. VAN 1067, VAN 9001, VAN 9003).
• Interfering software or system conflicts: Other programs, overlays or virtual machines throw Vanguard off (e.g. VAN 128, VAN 135, VAN 138).
• Account or hardware bans: Rule violations trigger bans (e.g. VAN 152, VAL 61).

Once you know which group your code belongs to, the solution is usually within reach. The finder above sorts the codes exactly by these categories.

The general fixes that almost always help

Before you dive into detailed solutions, a short standard routine is worthwhile. Surprisingly many VAN errors disappear after just these steps:

1. Restart Vanguard and Valorant completely

Close Valorant and Vanguard completely. You can spot Vanguard by the small shield icon in the bottom right of the taskbar – right-click it and choose "Quit". Then it’s best to restart the whole PC and open Valorant again. Vanguard then boots up cleanly along with it. This simple step fixes a large portion of all sporadic errors.

2. Refresh your network

For connection codes it helps to unplug the router or modem from power for about 30 seconds and restart it. Additionally you can clear the DNS cache in the command prompt by running the command ipconfig /flushdns. Also temporarily disable any VPN and any proxy – both are among the most common causes of connection errors.

3. Check firewall and antivirus

Allow Valorant, Vanguard and the Riot client through your firewall and antivirus program. Some protection programs wrongly block the anti-cheat software. A clean boot of Windows, in which only the most essential services run, additionally helps to rule out interfering background programs.

4. Keep an eye on the server status

Not every error is down to your PC. When the Riot servers are under maintenance or having problems, connection errors pile up. A look at the official server status tells you whether the problem is on your side or on Riot’s. In that case, only waiting helps.

TPM 2.0 and Secure Boot – the most common Windows 11 hurdle

A whole block of VAN errors (above all VAN 1067, but also VAN 9001 and VAN 9003) has the same cause: on Windows 11 Vanguard requires the security features TPM 2.0 and Secure Boot to be enabled. If they aren’t, the anti-cheat refuses to start. This especially affects players who have recently switched to Windows 11 or built their PC themselves, because these options aren’t always active out of the box.

The solution lies in the BIOS or UEFI of your motherboard. There you enable the TPM – on Intel boards the option is often called "PTT" (Platform Trust Technology), on AMD boards "fTPM". Secure Boot is usually found in the boot menu; for it to be enabled, the boot mode must be set to UEFI and not Legacy/CSM. Because the exact wording varies from one motherboard manufacturer to another and a wrong click in the BIOS can be annoying, we have created an illustrated step-by-step guide of its own for the classic VAN 1067. You’ll find the link to it in the error-code finder right next to VAN 1067.

When software or conflicts are to blame

Some VAN errors arise because other programs get in Vanguard’s way. Typical culprits are overclocking and monitoring tools like MSI Afterburner, aggressive antivirus programs, certain overlays or optimization software that digs deep into the system. Codes like VAN 128 or VAN 135 often point to such conflicts. The solution is to close suspicious programs or uninstall them for testing and perform a clean boot. If Valorant runs afterwards, you can re-enable the programs one by one to find the exact culprit.

A special case is VAN 138: this code appears when you try to launch Valorant in a virtual machine. That isn’t allowed for anti-cheat reasons – Valorant must run on a real, normal Windows installation. No trick helps here, only switching to a regular system.

Bans: VAN 152 and co.

Not every VAN code is a technical problem. VAN 152 stands for a hardware ban (HWID ban). Here not only the account but the hardware itself is blocked – usually as a consequence of serious rule violations such as cheating. Such a ban is generally long-term and can’t be circumvented with technical tricks. The only legitimate route is a support ticket with Riot Games, in which you describe your case and ask for a review. The same applies to account bans like VAL 61. Important: never try to "bypass" a ban with dubious software – that only makes things worse and violates the terms of use.

Reinstall Vanguard completely – the last resort

When individual fixes don’t take hold and an error stubbornly persists, a clean reinstall of Vanguard is often the last but very effective step. To do this you uninstall Vanguard via the Windows program list (it’s called "Riot Vanguard" there), restart the PC and then open Valorant. On launch Vanguard reinstalls itself automatically, and many errors caused by corrupted files are thereby resolved. Pause briefly beforehand and make sure no interfering software is running in the background so that the reinstall runs undisturbed. After another restart Valorant should, in most cases, start normally again.

Frequently asked questions about Valorant error codes

Why won’t Valorant start anymore after a Windows update? Larger Windows updates can scramble BIOS settings or drivers, suddenly causing TPM or Secure Boot errors. A look into the BIOS and the steps described above usually solve it.

Do I really have to restart my PC every time? With Vanguard errors it’s almost always worth it, because the anti-cheat only loads correctly on a clean system start. A mere client restart often isn’t enough.

Are VAN and VAL errors the same thing? Both belong to Valorant. VAN codes come from the anti-cheat Vanguard, VAL codes from the Riot client or the game itself. The solution approaches overlap strongly, however, which is why we also list the most important VAL codes here.

What if no fix helps? Then turn to the official Riot support and describe your exact error code as well as the steps you’ve already tried. The more precise your details, the faster you can be helped.

Errors during update or patch

A problem type of its own occurs when Valorant won’t update properly. If the patch process hangs, aborts or a message appears that the update has failed, it’s often due to an unstable connection or corrupted update files. The first step here too is a restart of the client and the router. If that doesn’t help, running the Riot client "as administrator" helps – a right-click on the shortcut is enough. This gives the client the necessary rights to write files in the program folder. In stubborn cases it’s worth clearing the patch cache or reinstalling the client without touching the large game directory. Also make sure there is enough free storage space on your drive – a full drive is a surprisingly common cause of failed updates.

Vanguard, performance and a smooth game

Some players fear that the anti-cheat Vanguard impairs performance or is responsible for stutters. In practice the impact on the frame rate is minimal – Vanguard is designed to work in the background as resource-friendly as possible. If you do notice performance drops, it’s usually down to other factors: outdated graphics drivers, graphics settings that are too high, or background programs that load the processor. Keep your drivers up to date at all times, close unnecessary programs before playing and make sure Windows isn’t just downloading large updates in the background. That way Valorant runs not only error-free but also smoothly. Should a VAN error occur precisely when your system is heavily loaded, closing memory-hungry applications can already provide relief.

Understanding ping, lag and connection drops

Not every ejection from a match is a classic error code – often there’s simply a fluctuating internet connection behind it, which then shows up as connection codes like VAN 68. A high ping or sudden lag spikes point to problems in the home network. A wired connection (LAN) is almost always superior to Wi-Fi for online gaming because it’s more stable and has lower latency. If you depend on Wi-Fi, it helps to move closer to the router and to pause other bandwidth-hungry devices in the household while playing. Updating your motherboard’s network drivers can work wonders too. Anyone who regularly struggles with connection problems should also check whether automatic downloads or cloud backups are running in the background and straining the line. A stable connection is the best prevention against a whole batch of VAN errors.

How to prevent error codes

Many VAN errors can be avoided before they even arise. A few habits help keep your system permanently Valorant-ready. Keep Windows and your drivers – especially graphics and network drivers – regularly up to date. Leave TPM 2.0 and Secure Boot permanently enabled in the BIOS so that no nasty surprises occur after a Windows update. Avoid dodgy "optimization tools" and cheat-adjacent software, which Vanguard blocks anyway. Restart your PC completely from time to time instead of just sending it to sleep – that keeps the system clean and prevents hung services. And keep some free disk space available so that updates run smoothly. Anyone who takes these simple points to heart will be slowed down by a VAN error far less often and can focus on what really matters.

The most important VAL codes at a glance

Alongside the VAN codes you’ll occasionally encounter VAL errors, which come from the Riot client itself. VAL 5, for instance, signals that no connection to the servers can be established – here the same network steps as for the VAN connection errors help, supplemented by signing out of all devices. VAL 43 points to a timeout or corrupted game files; a client restart and repairing the game files usually solve it. VAL 51 concerns the party system and can often be fixed by a restart and briefly disabling the antivirus. And VAL 62 resembles the connection codes: restarting the modem and clearing the DNS bring you back online. Because the causes overlap so strongly with the VAN codes, you’ll find the most important VAL codes in the error-code finder above as well – just type in the number and the matching solution appears.

Conclusion

Most Valorant VAN error codes look more threatening than they are. Behind the majority lie three things: connection problems, disabled security features on Windows 11, or interfering software. With the standard routine of restarting, refreshing the network, checking the firewall and – if necessary – reinstalling Vanguard, you get almost every problem under control. Use the error-code finder above to find your specific code and its solution instantly, and for VAN 1067 fall back on our detailed step-by-step guide. That way, in the vast majority of cases, you’re back in the game within a few minutes – and can focus again on what matters: your next rank-up with your favorite agent.