Valorant VAN Error Codes

Valorant VAN error codes – quick help

Nothing is more frustrating than firing up Valorant and being greeted by a cryptic VAN error code instead. Whether the game refuses to start, kicks you out mid-match or won’t connect – behind almost every one of these codes is a specific, often easily fixable cause. On this page, you’ll find a big overview of the most important Valorant error codes (VAN and VAL), 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 VAN 1067, we also have a detailed guide of its own, which we link to at the right spot.

57 VAN and VAL error codes at a glance

The table contains the same 46 VAN and 11 VAL codes as the finder above – each with Riot’s short meaning and the steps Riot recommends in the support article for that code, in Riot’s order. Launch the game after each step; if the error persists, Riot recommends submitting a ticket with your logs. Rarer codes are in Riot’s full list of Vanguard error codes.

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:

• Vanguard startup and connection problems: Vanguard doesn’t start cleanly or loses its connection or session (e.g. VAN 0, VAN 1067, VAN 68, VAN -81). Riot’s steps start with Vanguard and Windows; your network comes last.
• PC security settings: Vanguard can require TPM 2.0, Secure Boot and other Windows protections – on Windows 11, Riot lists TPM 2.0 and Secure Boot as mandatory. They have their own codes (VAN 9001, VAN 9003, VAN 9005, VAN: RESTRICTION).
• Interfering software, system checks and virtual machines: background programs can interfere with Vanguard (Riot then recommends a clean boot), VAN 128 reports a failed system trust check, VAN 138 a virtual machine.
• 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, it’s worth running through a short standard routine. A surprising number of 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 your whole PC and open Valorant again. Vanguard will then start up cleanly along with it. This simple step fixes a large share of random, one-off errors.

2. Refresh your network

If you’ve already worked through Riot’s Vanguard steps for your code and suspect your network, it helps to unplug your router or modem for about 30 seconds and restart it. You can also clear the DNS cache in Command Prompt by running ipconfig /flushdns. Also temporarily disable any VPN or 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. Some security programs wrongly block the anti-cheat software. A clean boot of Windows, where only essential services run, also helps 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 end or on Riot’s. In that case, all you can do is wait.

TPM 2.0 and Secure Boot: VAN 9001, VAN 9003 and more

A separate group of VAN errors depends on the security features TPM 2.0 and Secure Boot: without TPM 2.0, Vanguard reports VAN 9001; without Secure Boot, VAN 9003. VAN 9005 requires TPM 2.0, Secure Boot and Memory Integrity, VAN 9090 reports a TPM that couldn’t initialize, and VAN: RESTRICTION asks for a Windows update or a specific protection feature. On Windows 11, Riot lists TPM 2.0 and Secure Boot as mandatory – it often hits players who just moved to Windows 11 or built their own PC, because these options aren’t always on out of the box. VAN 1067 doesn’t belong to this group: Riot describes it as a general Vanguard startup error and mentions neither TPM nor Secure Boot in its steps.

The fix is in your motherboard’s BIOS or UEFI. That’s where 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, you’ll find every menu path in our guide enable Secure Boot & TPM 2.0; the error-code finder links to it right at VAN 9001, 9003, 9005 and 9090. VAN 1067 has its own guide with Riot’s steps.

🔐 The full step-by-step guide with BIOS paths for ASUS, MSI, Gigabyte and ASRock, MBR to GPT and every code from VAN 9001 to VAN:RESTRICTION is here: Valorant: enable Secure Boot & TPM 2.0.

When software or conflicts are to blame

Some VAN errors happen 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. That’s why Riot recommends a clean boot for many codes (e.g. VAN 0, 57, 128 and 1067). The fix is to close suspicious programs or uninstall them for testing and perform a clean boot. If Valorant runs afterward, 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, regular Windows installation. No workaround helps here – only switching to a regular system.

Bans: VAN 152 and more

Not every VAN code is a technical problem. VAN 152 stands for a hardware ban (HWID ban). This blocks not just the account but the hardware itself – usually as a result of serious rule violations such as cheating. Riot gives no fixed duration; according to Riot, reinstalling, restarting or switching your connection won’t lift it. 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 shady software – that only makes things worse and violates the Terms of Service.

Reinstall Vanguard completely – the last resort

When individual fixes don’t work and an error stubbornly persists, a clean reinstall of Vanguard is often the last but very effective step. To do this, uninstall Vanguard via the Windows app list (it’s listed as "Riot Vanguard"), restart your PC and then open Valorant. On launch, Vanguard reinstalls itself automatically, which resolves many errors caused by corrupted files. Before you start, make sure no interfering software is running in the background so the reinstall isn’t disrupted. After another restart, Valorant should start normally again in most cases.

🖥️ VAN 9001 or 9003? The PC check covers TPM 2.0, Secure Boot and your hardware in one go.

How to cleanly reinstall Vanguard and download Valorant only from official sources is shown in our guide Valorant download & Vanguard reinstall. If you want to remove Valorant together with Vanguard and the Riot Client completely, follow our guide how to uninstall Valorant.

Frequently asked questions about Valorant error codes

Why won’t Valorant start anymore after a Windows update? Check the exact code first: for VAN 0, VAN 1067 and similar startup errors, Riot’s steps help – finish installing updates and restart, set “vgc” to “Automatic”, reinstall Vanguard. If you see VAN 9001 or VAN 9003, check in the BIOS whether TPM 2.0 and Secure Boot are still on; a BIOS update or reset can switch them off.

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. Just restarting the client often isn’t enough.

Are VAN and VAL errors the same thing? Both come from Valorant. VAN codes come from the Vanguard anti-cheat, VAL codes from the Riot Client or the game itself. The fixes overlap a lot, though, which is why we also list the most important VAL codes here.

What if no fix helps? Then contact official Riot Support and give your exact error code along with the steps you’ve already tried. In its code articles, Riot also asks for your logs, which you collect with the Riot Repair Tool. The more precise your details, the faster they can help you.

Errors during update or patch

A separate type of problem occurs when Valorant won’t update properly. If patching hangs, aborts or you get a message that the update failed, it’s often due to an unstable connection or corrupted update files. Here, too, the first step is to restart the client and the router. If that doesn’t help, try running the Riot Client "as administrator" – just right-click the shortcut. This gives the client the permissions it needs to write files to 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 worry that the Vanguard anti-cheat hurts performance or causes stutters. In practice, the impact on frame rate is minimal – Vanguard is designed to run in the background using as few resources 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. If a VAN error shows up exactly when your system is under heavy load, closing memory-hungry apps may already help.

Understanding ping, lag and connection drops

Not every time you get kicked from a match is there a classic error code behind it – often it’s simply an unstable internet connection, which shows up as lag or a disconnect. For VAN 68, by the way, Riot lists the connection only as the last step – restart, system time and the Vanguard steps come first. High ping or sudden lag spikes point to problems with your 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 have to use Wi-Fi, it helps to move closer to the router and pause other bandwidth-hungry devices in your household while playing. Updating your motherboard’s network drivers can work wonders too. If you regularly struggle with connection problems, also check whether automatic downloads or cloud backups are running in the background and hogging your bandwidth. A stable connection is the best prevention against lag and disconnects.

How to prevent error codes

Many VAN errors can be prevented before they even happen. 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 Vanguard doesn’t report VAN 9001 or VAN 9003. 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 or the game itself. According to Riot’s list, VAL 5 means your account was logged into elsewhere – signing out of all devices helps here. VAL 43 reports that a system timed out, VAL 51 a problem creating a party; for both, Riot recommends restarting the Riot Client. VAL 62 means no game servers can be reached – according to Riot, something is wrong with your network; restart the Riot Client and submit a ticket if it persists. VAL 39 and VAL 46 stand for an unavailable server or planned maintenance – then waiting is the only fix. Riot itself notes that its VAL list is partly out of date. You’ll find every VAL code on this page in the error-code finder above as well – just type in the number.

How to tackle a VAN error methodically

Tackling an error code methodically saves you a lot of time and frustration in the end. First, write down the exact number before you close the window – only then can you look up the right fix. After that, always start with the simplest step and only work your way up to the more involved ones when needed. Does the error already disappear after a clean restart of the PC? Then you’re done. If it stubbornly persists, your next step is to clarify what kind of problem it is: does the code point to the connection, to your system’s security settings, or to interfering software? That determines which steps even make sense. You’ll find a compact overview of common repairs in our Tech-Fix.

It’s important to change only one thing at a time and test briefly afterward. If you disable the VPN, open the firewall and reinstall Vanguard all at once, you won’t know which change actually helped – and you may end up keeping an unnecessary change. If, on the other hand, you proceed step by step, you’ll spot the real culprit and can remember it for next time. This calm, methodical approach is the fastest way back into the game for almost every error code.

Keep drivers and Windows up to date

A surprisingly large share of problems can be traced back to outdated drivers and an out-of-date Windows. So keep especially your graphics, network and chipset drivers up to date. Graphics drivers are best obtained directly from the manufacturer of your graphics card, network and chipset drivers from your motherboard manufacturer. Also check Windows Update regularly, because security and system updates not only close security holes but often also improve compatibility with anti-cheat software like Vanguard. An up-to-date system is the best foundation for Valorant to start and run reliably.

Up-to-date drivers pay off twice over: they not only prevent error codes but also give you smoother visuals and a more consistent frame rate. Anyone who is fine-tuning their setup anyway can use this moment to optimize their own settings too – for example with our pro settings or the sensitivity converter, with which you transfer your mouse sensitivity cleanly. That way, you turn an annoying bit of troubleshooting into a quick tune-up for your system.

When and how to contact Riot Support

Some errors simply can’t be solved on your own despite all your effort – for instance with an account or hardware ban, or when a code stubbornly persists even though you’ve gone through every sensible step. In that case, your next stop is official Riot Support. Describe your exact error code there, briefly outline your system, and list which solutions you’ve already tried. The more complete and factual your details are, the faster and more precisely they can help you. Avoid submitting the same request multiple times – that tends to delay processing rather than speed it up.

If individual terms from the support contact or from error messages are unclear to you, a look at our Valorant glossary helps. Anyone who is completely new and simply wants to get their bearings first will find an easy-to-understand foundation in the beginner’s guide. With this toolkit it’s easier to phrase a support ticket precisely and to interpret the answers correctly.

Patience instead of risky shortcuts

As tempting as a supposed miracle fix from the internet may sound – stay away from shady “repair tools” or programs that promise to bypass bans. Such software usually causes more damage than it fixes and violates the terms of service. The vast majority of VAN errors can be fixed in a few minutes using the official steps described here. So stay calm, work through the proven solutions one after another, and give your system the chance to restart cleanly after each change.

And if you do have to wait a few minutes for a restart or an update, the time can be put to good use: fine-tune your crosshair with the crosshair generator, refresh your map knowledge on the current maps, or get an overview of the ranks. That way you’re perfectly prepared right after the restart and can get straight back in without any detours.

Conclusion

Most Valorant VAN error codes look more threatening than they are. According to Riot’s articles, most codes come down to Vanguard not starting cleanly or losing its connection, a missing Windows protection such as TPM 2.0 or Secure Boot, or interfering software. Work through Riot’s steps for your code in order – usually updating Windows, the Vanguard service, reinstalling Vanguard and a clean boot – and launch the game after each step. Use the error-code finder above to find your specific code and its solution instantly, and for VAN 1067, turn to 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.