How to Fix the Valorant VAN Error (All Codes, 2026 Guide)
You’re queued up, the Riot Client is loading, and then it happens: a VAN error pops up and kicks you straight back to the desktop. If you’re trying to figure out how to fix the Valorant VAN error, you’re dealing with one of the most common — and most misunderstood — problems in the game. VAN errors come from Riot Vanguard, Valorant’s anti-cheat system, and they can mean anything from “Riot’s servers are having a bad day” to “your BIOS settings need a fifteen-second change.”
The good news is that the vast majority of VAN errors follow predictable patterns. Once you know which category your specific code falls into, the fix is usually quick. This guide walks through what VAN errors actually are, how to tell whether the problem is on your end or Riot’s, and exactly how to resolve the most common codes — including the trickier TPM 2.0 and Secure Boot errors that trip up a lot of Windows 11 players. Everything here is based on Riot’s own support documentation combined with practical, hands-on troubleshooting steps that consistently work.
What Is a Valorant VAN Error?
Every error Valorant throws at you starts with a short prefix, and that prefix tells you where to look.
- VAN errors come from Riot Vanguard, the anti-cheat driver that runs alongside the game.
- VAL errors come from the Valorant game client or Riot’s game servers.
- RIOT-prefixed errors usually relate to your account or the Riot Client itself.
Mixing these up wastes time, because the fix for a client-side VAL error looks nothing like the fix for a Vanguard-level VAN error. If your error code starts with VAN, the problem lives specifically in how Vanguard is starting up, verifying your system, or staying connected — not in Valorant’s game logic itself. Riot maintains its own Vanguard error codes support hub, which is worth bookmarking since it’s updated as new codes get their own dedicated pages.
What Riot Vanguard Actually Does
Vanguard runs as a Windows service called vgc, alongside a kernel-level driver that loads very early in the Windows boot process — before most other software, and in some configurations before Windows itself finishes initializing security checks. That’s an unusual amount of access for a piece of gaming software, and it’s intentional. Riot built Vanguard this way specifically to catch cheat software that tries to load before user-mode anti-cheat tools would normally notice it.
This is also why “just restart Valorant” almost never fixes a VAN error. Since Vanguard’s driver is tied to the boot process, a simple relaunch of the game doesn’t reload it. You typically need a full PC restart to give Vanguard a clean slate — which is why that’s the first step in nearly every official fix.
Is the VAN Error on Riot’s Side or Yours?
Before changing a single setting on your PC, rule out the simplest explanation: Riot’s servers might just be having an outage.
- Check Riot Games’ Service Status page for your region. If there’s an active incident or scheduled maintenance, your VAN error is likely temporary, and no amount of BIOS tweaking will fix it faster than Riot’s own timeline.
- Check Downdetector or social channels for a spike in reports. If thousands of players are suddenly hitting the same error at the same time, it’s almost certainly server-side.
- Try a different game or app that uses your same internet connection. If everything else works fine, the problem is more likely specific to Valorant/Vanguard rather than your broader network.
| Signal | Likely Cause | What To Do |
|---|---|---|
| Error started suddenly, affects many players | Riot server-side issue | Wait, check status page |
| Error is consistent every time you launch | Client-side / local config | Work through the fixes below |
| Error only happens after a Windows Update | Local — Vanguard/Windows conflict | Jump to the Windows Update section |
| Error only happens on one specific PC | Local hardware/firmware issue | Check TPM/Secure Boot section |
If Riot’s status page is clear and no one else seems to be reporting the same thing, it’s time to work through the fixes below — starting with the specific code you’re seeing.
Most Common Valorant VAN Error Codes and How to Fix Them
VAN error codes generally fall into four buckets: connection/sync errors, startup and trust errors (TPM/Secure Boot related), installation or file-integrity errors, and ban-related errors. Here’s how to handle the ones you’re most likely to run into.
VAN 68 — Connection/Sync Error
VAN 68 usually means your connection lost sync with Riot’s servers mid-session or during login. It’s one of the more common network-side VAN codes.
Fix it:
- Fully close Valorant and the Riot Client, then restart your PC (not just the app).
- Flush your DNS cache: open Command Prompt as administrator and run
ipconfig /flushdns. - Temporarily disable any VPN or proxy — Riot’s servers are sensitive to routing changes mid-session, and a VPN can trigger repeated resyncs.
- Whitelist Valorant, the Riot Client, and Vanguard (
vgc.exe) in Windows Firewall, since an overzealous firewall rule can interrupt the sync handshake. - If your setup uses IPv6 and the issue persists, try disabling IPv6 on your network adapter — some ISPs handle Riot’s traffic more reliably over IPv4 only.
If it clears up after a restart but comes back repeatedly, the underlying issue is almost always network stability rather than anything wrong with the game files themselves. If your connection is generally unstable, it’s worth reading through a broader guide on fixing high ping while gaming, since the same routing issues that cause VAN 68 often show up as lag in other games too.
VAN -104 — Vanguard Connection Error
This one shows up as “VALORANT has encountered a connection error” and typically means Vanguard is struggling to start, stay connected, or finish its readiness checks while the game is launching. Riot’s own VAN -104 support page walks through this exact sequence.
Fix it, in order:
- Restart your PC — this alone resolves a large share of VAN -104 cases because it gives Vanguard a completely fresh startup.
- Check your Windows date, time, and time zone settings using Microsoft’s official guide. Incorrect system time can break the secure handshake Vanguard uses to verify your session, and Windows won’t always warn you when it’s wrong.
- Perform a clean boot to rule out a conflicting background app (steps below).
- Reinstall Valorant if the above steps don’t help — this replaces any corrupted or missing files that might be blocking Vanguard from finishing its checks.
- If none of that works, treat it as a connection issue and work through a full network troubleshooting pass.
VAN 84 — Vanguard/Authentication Connection Failure
VAN 84 typically means your client couldn’t establish a secure connection to Riot’s authentication servers through Vanguard. It became especially visible after recent patch cycles, with reports spiking during periods of server instability.
Fix it:
- Check the service status page first — a real share of VAN 84 reports line up with regional outages.
- Power-cycle your full network stack: shut down your PC, unplug your modem and router, wait about 30 seconds, then power the modem back on first, followed by the router, then your PC. This clears stale network state that a simple reboot alone might not touch.
- Restart the Vanguard service manually via
services.mscif it appears stopped. - If problems continue only on your account, and not for players around you, escalate to Riot Support rather than continuing to guess.
VAN 216 — Unexpected Vanguard Error
VAN 216 is a general “something unexpected happened and Vanguard is closing the client” error. Because it’s broad, Riot’s own recommended order is worth following exactly rather than skipping ahead to reinstalling.
Fix it:
- Restart your PC.
- Verify Windows date/time settings.
- Run a clean boot to isolate background software conflicts.
- Reinstall the game if the error persists after a clean boot.
- Move on to a full connection troubleshooting pass if reinstalling doesn’t help.
VAN 1067 — Grouped Configuration Error
VAN 1067 doesn’t point to one single cause — Riot groups several different triggers under this code, including pending Windows Updates, altered security settings, and corrupted game files.
Fix it:
- Check for and install any pending Windows Updates before doing anything else, since a partially applied update is a common trigger.
- Repair Valorant through the Riot Client: open the client, select Valorant, and choose Repair from the settings menu.
- Review your Windows security settings for anything that might be blocking Vanguard (see the security/firewall section below).
- Fully restart your PC after any changes — Vanguard needs a clean boot cycle to pick up new settings.
- Close background apps like Discord overlays while troubleshooting, since they’ve been known to interfere with this specific error.
VAN 152 — Hardware ID Flag (Not Always a Bug)
VAN 152 is different from the other codes on this list: it’s frequently tied to a hardware ID (HWID) flag rather than a simple technical glitch. If you’re seeing VAN 152 and haven’t used any third-party software that touches game memory, it’s worth trying a clean boot and Vanguard reinstall first, since misfires do happen. But if the error persists and you have reason to believe it’s a genuine flag, this isn’t something firewall changes or DNS flushes will resolve — it requires contacting Riot Support directly.
Note: Riot has publicly acknowledged incidents where its anti-cheat system flagged accounts in error. If you believe you were wrongly flagged, submit a support ticket with your system logs attached rather than attempting workarounds — unofficial “unban” tools are a security risk and can make your situation worse.
VAN 138 — Virtualized Environment Detected
If you’re trying to run Valorant inside a virtual machine, a sandboxed environment, or certain remote desktop configurations, Vanguard will block it outright with VAN 138. This isn’t a bug — Vanguard’s entire trust model depends on verifying the real hardware and boot chain, which a VM can’t provide in a way Vanguard accepts. The only real fix is running Valorant on a standard, non-virtualized Windows installation.
VAN: STATUS_VMD_9001 — Intel Volume Management Device Conflict
This more specific error points to a conflict with Intel’s Volume Management Device (VMD) storage controller, common on newer laptops and some Intel-based desktop boards.
Fix it:
- Identify your exact motherboard or laptop model.
- Download the correct Intel Rapid Storage Technology (RST) or VMD driver directly from the manufacturer’s support page — not a generic download site.
- Install the driver and restart your PC.
- Run Windows Update afterward to catch any related optional driver updates.
Warning: Do not change your storage controller mode (AHCI/RAID/VMD) in BIOS as a casual troubleshooting step. Switching modes incorrectly can prevent Windows from booting at all. If you’re not confident about this setting, get the correct driver first before touching BIOS storage settings.
VAN 9001 / VAN 9003 / VAN 9090 — TPM 2.0 and Secure Boot Errors
These three codes are common enough, and complex enough, that they get their own full section below.
Quick-Reference Table
| Code | Category | Most Likely Cause | Fastest First Step |
|---|---|---|---|
| VAN 68 | Connection/Sync | Network routing, VPN, firewall | Restart PC, flush DNS |
| VAN -104 | Vanguard connection | Startup failure, wrong system time | Restart PC, check time settings |
| VAN 84 | Auth connection | Server-side or Vanguard service stopped | Check status page, power-cycle router |
| VAN 216 | General Vanguard failure | Background app conflict | Clean boot |
| VAN 1067 | Grouped/config | Windows Update, corrupted files | Repair via Riot Client |
| VAN 152 | Hardware ID flag | Anti-cheat flag (sometimes false positive) | Contact Riot Support |
| VAN 138 | Virtualization block | Running in a VM/sandbox | Use a standard Windows install |
| VAN 9001/9003/9090 | Startup trust (TPM/Secure Boot) | TPM 2.0 or Secure Boot disabled | See TPM/Secure Boot section |
| VAN: STATUS_VMD_9001 | Storage driver conflict | Missing/outdated Intel VMD driver | Update RST/VMD driver |
Fixing TPM 2.0 and Secure Boot VAN Errors (Windows 11)
If you’re on Windows 11 and hit VAN 9001, VAN 9003, or VAN 9090, this is almost always a firmware-level trust issue rather than a network or file problem. Riot publishes a dedicated troubleshooting page for these three codes, and the steps below follow that same sequence with extra context on where players tend to get stuck.
Why Vanguard Requires This
TPM (Trusted Platform Module) 2.0 and Secure Boot are Windows 11 security features that verify your system’s boot chain hasn’t been tampered with before the operating system fully loads. Vanguard checks for both because they establish what Riot calls a “trusted state” — hardware-backed proof that nothing suspicious loaded before Vanguard itself did. If either feature is off, Vanguard can’t confirm that trust, and Valorant won’t launch. This isn’t Riot being arbitrary; it directly targets the kind of pre-boot cheat tools that user-mode anti-cheat can’t see.
How to Check Your Current Status
- Press Windows key, type
tpm.msc, and press Enter. Look for “The TPM is ready for use” and confirm it lists Specification Version 2.0 — not just that a TPM is present. - Press Windows key, type
msinfo32, and press Enter. In System Information, check the Secure Boot State field — it should read On.
How to Enable Both in BIOS/UEFI
- Restart your PC and enter BIOS/UEFI setup (usually Delete, F2, or F10 during boot — check your motherboard manual for the exact key).
- Find Secure Boot, usually under a Boot or Security tab, and set it to Enabled. You may need to set Boot Mode to UEFI (not Legacy/CSM) first, since Secure Boot requires UEFI.
- Find TPM, which may be listed as TPM, fTPM (AMD), or PTT/Intel Platform Trust Technology (Intel), and set it to Enabled.
- Save changes and exit — this will trigger a full restart.
- Recheck both settings using
tpm.mscandmsinfo32after Windows finishes booting.
“I Enabled Both, But Valorant Still Won’t Launch”
This happens more often than you’d expect, and it usually comes down to one of these:
- Fast Startup is interfering. Windows’ Fast Startup feature can preserve parts of the old boot state instead of fully reinitializing after a BIOS change. Disable it under Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup,” then fully restart (not just sign out).
- The BIOS change didn’t fully apply. Some firmware needs a complete power-off-and-on cycle, not just a restart, for security settings to take effect. Shut down completely, wait a few seconds, then power back on.
- Your motherboard genuinely lacks TPM 2.0 support. If there’s no TPM/fTPM/PTT option in BIOS at all, your board doesn’t support it, and you’d need newer hardware to meet Vanguard’s requirement — there’s no software workaround for genuinely absent hardware.
Important: Don’t permanently disable Secure Boot or TPM as a way to “get past” this error. Doing so doesn’t fix the underlying issue — it just changes which error Vanguard throws, since these checks aren’t optional for Valorant on Windows 11.
Network-Related Causes of VAN Errors
A large share of VAN errors — especially the ones with numbers in the 60s and low 200s — trace back to something in your network path getting between your PC and Riot’s servers.
- Firewall blocking Vanguard or the Riot Client. Open Windows Security → Firewall & Network Protection → Allow an app through firewall, and make sure both Valorant and Vanguard (
vgc.exe, usually inC:\Program Files\Riot Vanguard\) are allowed on both private and public networks. - Third-party antivirus interference. Some antivirus suites are more aggressive than Windows Defender about blocking low-level services like Vanguard. If you’re running third-party security software, check its logs for blocked connections related to Riot or Vanguard.
- VPN and proxy conflicts. Riot recommends disabling both fully while troubleshooting, since routing changes mid-session can trigger repeated authentication failures.
- DNS cache issues. A stale or corrupted DNS cache can point your client toward outdated server information. Flushing it (
ipconfig /flushdns) is quick and low-risk. - IPv6 conflicts. On some networks, disabling IPv6 on your adapter (Network Connections → your adapter → Properties → uncheck Internet Protocol Version 6) resolves sync issues that IPv4-only troubleshooting doesn’t touch.
- A full router/modem power cycle. This clears more state than a simple Wi-Fi toggle and is worth doing properly: power off, unplug both devices, wait 30 seconds, then bring the modem up first, followed by the router.
If VAN errors keep resurfacing specifically during matches rather than at launch, it’s also worth ruling out broader connection instability — a guide on fixing packet loss in online games covers diagnostic steps that apply well beyond Valorant.
Riot Vanguard Installation and File Issues
Sometimes the problem isn’t your network or firmware — it’s the Vanguard or Valorant installation itself.
- Repair through the Riot Client first, since this is the least destructive option: open the Riot Client, select Valorant, and click Repair. If everything checks out, you’ll see a message confirming your game is already up to date.
- Check the Vanguard service directly. Press Windows key + R, type
services.msc, and look for vgc. If it’s stopped, right-click and start it; if it’s missing entirely, that points to a broken Vanguard install. - Full uninstall and reinstall, if a repair doesn’t resolve things: uninstall Valorant through Windows Settings → Apps, then also uninstall Riot Vanguard separately if it’s listed (it sometimes persists after the game is removed). Reinstall Valorant fresh afterward, which will also reinstall Vanguard.
- Windows Update conflicts. Occasionally a Windows Update changes a security policy or driver signing requirement in a way that breaks Vanguard until a matching Vanguard update rolls out. If your VAN error started right after a Windows Update and nothing else has changed, check Riot’s status page and community channels for reports of the same issue — sometimes the fix is simply waiting for Riot’s next Vanguard patch.
If your game files are frequently getting corrupted rather than this being a one-off, it may be worth working through a broader guide on fixing corrupted game installation files, which covers disk-level causes beyond Valorant specifically.
Driver, Overlay, and Background App Conflicts
Vanguard’s low-level access means it’s more sensitive to background software than most games.
- Overlays and injection-style tools. Discord’s overlay, RGB lighting software, and performance overlays like MSI Afterburner have all been reported to trigger VAN errors in specific configurations, since they hook into processes in ways that can resemble the behavior Vanguard is designed to flag.
- Outdated GPU or network drivers. Keep both updated through your GPU manufacturer’s tool and Windows Update rather than relying on outdated drivers bundled with old installers.
- Running a clean boot to isolate the culprit: press Windows key + R, type
msconfig, go to the Services tab, check “Hide all Microsoft services,” then disable everything remaining and restart. If Valorant launches fine, re-enable services in small batches to find the specific conflict.
Advanced Diagnostics for Persistent VAN Errors
If you’ve worked through the relevant code-specific fix and the network section above with no luck, it’s time to dig a little deeper before contacting support.
- Check Windows Event Viewer for entries related to the Vanguard service around the time the error occurs — look under Windows Logs → System, filtered for Service Control Manager events mentioning
vgc. - Locate Vanguard and Valorant logs on your system, which Riot Support will typically ask for if you open a ticket.
- Contact Riot Player Support directly if you’ve tried the relevant fixes above without success. Attach your logs up front — this is the single biggest thing you can do to speed up a real response instead of a generic “have you tried restarting” reply.
- Distinguish a genuine ban from a technical error. If you consistently get VAN 152 or a similar code with zero prior third-party software use, and other troubleshooting steps make no difference, treat it as a support-ticket situation rather than something to keep troubleshooting solo.
Step-by-Step Troubleshooting Flow
If you’d rather skip the code-by-code breakdown and just work through this systematically, follow these tiers in order.
Tier 1 — Under 2 minutes
- Check Riot’s Service Status page for your region
- Fully restart your PC (not just the game)
Tier 2 — Under 10 minutes
- Flush DNS (
ipconfig /flushdns) - Disable VPN/proxy if in use
- Whitelist Valorant and Vanguard in Windows Firewall
- Run a clean boot to rule out background apps
Tier 3 — 15–30 minutes
- Check and enable TPM 2.0 and Secure Boot in BIOS
- Repair or reinstall Valorant through the Riot Client
- Update GPU and Intel RST/VMD drivers if applicable
Tier 4 — Escalation
- Pull Vanguard-related entries from Event Viewer
- Submit a Riot Support ticket with logs attached
Common Mistakes That Make VAN Errors Worse
- Permanently disabling Secure Boot or TPM instead of properly enabling them — this doesn’t fix the error, it just trades one blocked launch for another.
- Changing your storage controller mode (AHCI/RAID/VMD) in BIOS without knowing what it does — this can leave Windows unable to boot at all.
- Reinstalling Windows entirely before trying simpler, non-destructive fixes first.
- Ignoring the Service Status page and assuming every VAN error is something wrong with your PC, when a real share of them are server-side.
- Using unofficial “Vanguard bypass” tools. These are a genuine security risk, and using them can get your account flagged or banned outright — they are never worth it.
How to Prevent Future VAN Errors
- Keep Windows and drivers on a regular update schedule rather than only updating reactively when something breaks.
- Avoid running Valorant on virtual machines, ARM-based Windows devices, or heavily sandboxed setups — Vanguard simply isn’t built to trust those environments.
- After any BIOS update, recheck your TPM and Secure Boot status, since firmware updates occasionally reset these settings to defaults.
- Re-add firewall and antivirus exceptions for Valorant and Vanguard any time you reinstall or switch security software.
- Bookmark Riot’s Service Status page so you can rule out server-side issues in seconds next time.
Frequently Asked Questions
What does a VAN error mean in Valorant?
A VAN error means Riot Vanguard — Valorant’s anti-cheat system — failed to start, verify your system, or maintain a connection. It’s distinct from VAL errors, which relate to the game client or servers directly.
Is the Valorant VAN error a server or client problem?
It can be either. Codes tied to connection and authentication (like VAN 68 or VAN 84) are frequently server-side, especially during outages. Codes tied to TPM/Secure Boot, drivers, or file corruption are almost always client-side.
Why do I need TPM 2.0 and Secure Boot to play Valorant?
Vanguard uses both as hardware-backed proof that your system’s boot process hasn’t been tampered with before Vanguard itself loads. Without them, Vanguard can’t establish that trusted state, and Valorant won’t launch on Windows 11.
Does reinstalling Valorant fix VAN errors?
Sometimes. It’s most effective for file-integrity-related codes like VAN 1067, but it won’t help with server outages, TPM/Secure Boot issues, or genuine hardware ID flags.
Can antivirus software cause VAN errors?
Yes. Third-party antivirus and security suites can block Vanguard’s low-level service in ways Windows Defender typically doesn’t. Checking your antivirus logs for blocked Riot or Vanguard processes is a useful diagnostic step.
How do I know if the Vanguard service is running?
Open services.msc and look for a service named vgc. If it’s stopped or missing, that’s a strong sign your Vanguard installation needs a restart or repair.
What’s the difference between a VAN error and a hardware ban?
A VAN error is a technical failure that’s usually fixable through the steps in this guide. A hardware ID ban is an anti-cheat enforcement action. Riot has acknowledged isolated cases of incorrect bans, so if you believe you were flagged in error, contact Support directly rather than attempting a workaround.
Will disabling Secure Boot let me play without errors?
No — disabling it removes one of the requirements Vanguard checks for, so Valorant will still refuse to launch, or you’ll simply hit a different Vanguard error referencing the missing security feature.
Conclusion
- VAN errors come specifically from Riot Vanguard, not the Valorant game client itself.
- Always check Riot’s Service Status page first — a meaningful share of VAN errors are temporary and server-side.
- Full PC restarts matter more than simple game relaunches, because Vanguard’s driver loads during boot.
- TPM 2.0 and Secure Boot are non-negotiable requirements on Windows 11 — enabling them properly (and ruling out Fast Startup issues) resolves the VAN 9001/9003/9090 family.
- Network-level fixes (firewall whitelisting, DNS flush, disabling VPN/proxy) resolve most connection-category codes like VAN 68 and VAN -104.
- When in doubt, work through the tiered troubleshooting flow in order rather than jumping straight to a full reinstall or BIOS changes.
