Valorant VAN-81 Error Code: What It Is and How to Fix It

What Is the VAN 81 Valorant Error?

Staring at VAN 81 again? Yeah, I’ve fought the VAN 81 Valorant error more times than I want to admit. The popup reads “VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -81.” Only button: Quit. Which. Rude.

Here’s what most guides skip. VAN 81 gets tagged as a “connection error” on Riot’s support page, but your internet is almost never the problem. What’s actually broken is the VGC service, which is the background worker Vanguard needs to function. When VGC can’t boot up, can’t phone home to Riot, or gets slapped down by something on your PC, boom, VAN 81. Happens after Windows updates, new antivirus installs, power outages mid-patch… sometimes for no reason you can trace.

Still a common headache in Season V26 Act 2 as of April 2026. Riot hasn’t touched the core of how Vanguard works, so the fixes from prior seasons still apply to this year’s build.

Detail	Info
Error code	VAN -81 (also written VAN 81)
Error message	VALORANT has encountered a connection error
Root cause	VGC service (Riot Vanguard) not running or blocked
Platform	PC only (Windows)
Most common fix	Set VGC service to Automatic startup
Affected versions	All Valorant versions including Season V26

30-Second Diagnostic: Which Fix Do You Actually Need?

Most guides dump every possible fix on you and say good luck. Waste of time. Find the scenario below that sounds like yours, jump straight to that fix.

• Error started after a Windows update: your VGC startup type got flipped. Jump to Fix 2.
• Error since the day you installed Valorant: firewall or AV is blocking Vanguard. Fix 3 or Fix 6.
• Error after installing new antivirus software: there’s your culprit. Fix 6.
• Error is random and sporadic: stuck processes or background conflicts. Start at Fix 1.
• Error appeared out of nowhere on a stable PC: usually a Vanguard update that didn’t finish. Try Fix 5.
• Error only when you use a VPN: well. Turn off the VPN.
• Error with “Windows could not start the vgc service”: Vanguard files are fried. Fix 5.

Nothing above matches your situation? Just go through all six fixes from top to bottom. I sorted them by how often they actually work, so the earlier ones have better odds.

Why the VAN 81 Valorant Error Happens

Pretty much every VAN 81 Valorant error post on r/VALORANT boils down to one of five causes. Knowing which bucket you’re in saves you 20 minutes of random troubleshooting, so here they are, most likely first.

VGC Service Isn’t Running (Top VAN 81 Valorant Error Cause)

By a wide margin, the most common cause. VGC is a Windows service, basically a background worker, that Vanguard needs alive to do anything. If its startup type is anything but Automatic, it won’t fire up when you click play. What makes this sneaky is Windows updates silently flipping it back to Manual. You’ve been playing fine for weeks, one Patch Tuesday rolls through, and suddenly VAN 81. Seen this one a lot.

Windows Firewall Is Blocking Vanguard

Your firewall gets weirdly paranoid about Vanguard. When you first installed Valorant, Windows almost definitely popped a dialog asking if you wanted to allow the Riot Client through. Click No, dismiss it, or tab away too fast? Firewall might still be choking VGC’s traffic to Riot’s servers. Windows updates also love resetting firewall rules. Love that for us.

Third-Party Antivirus Interference

Third-party AV is a whole saga with Vanguard. Avast, Norton, Kaspersky, Bitdefender, Malwarebytes, all of them look at Vanguard installing a kernel-level driver and go “nope.” Which, to be fair, makes perfect sense from a security angle. Kernel access is extremely sus by default. But Vanguard needs that access. So the AV and Vanguard fight, VGC loses, you get VAN 81.

Corrupted Vanguard (Tricky VAN 81 Valorant Error Cause)

Rarer but nasty. Could be a power cut during a Vanguard update. Could be an interrupted install. Could be some sketchy “PC optimizer” tool that stomped on files it shouldn’t have. In these cases VGC usually shows as Running in Services, yet still can’t talk to Riot. Annoying to diagnose because everything looks fine on paper.

Riot’s Servers Are Down

Does happen, not often. New patch rollouts, backend issues, occasional DDoS… VGC can’t verify with Riot’s servers and the VAN 81 Valorant error pops up. Always peek at status.riotgames.com before you go tearing into your PC. Took me way too many hours the first time I hit this to realize it was a Riot-side problem.

Quick Checks Before You Start Fixing

Three things to verify before you go digging into services and firewalls. Takes 60 seconds, saves you from spiraling.

One, server status. Open Riot’s status page, find your region’s Valorant line. Anything red or yellow? Close the guide, wait it out. Not your problem to fix.

Two, test your net. Load YouTube or whatever in a browser. Works fine? Your internet is not the issue. Still, if you’re leaning on a Wi-Fi signal that drops every 20 minutes, grabbing an ethernet cable is a solid move for Valorant in general.

Three, system tray. Bottom right corner, near the clock. See a little shield icon? That’s Vanguard. Missing? Then VGC didn’t start with Windows, and honestly you can just skip ahead to Fix 2.

How to Fix the VAN 81 Valorant Error: 6 Working Methods

Going from fastest and easiest to most annoying. Stop when something works, no need to do all six.

This video from TechTutor walks through the same VAN 81 fixes if you’d rather follow along visually.

VAN 81 Valorant Error: Fix Success Rates and Timing

Not rigorous science, but after reading hundreds of posts on r/VALORANT and the Riot Discord tech-support channel, these percentages feel about right. Use them to pick your priorities.

Fix	Time	Success Rate	Requires Restart
Restart Everything Properly	2 min	~40%	Yes
Set VGC to Automatic	2 min	~65%	Yes
Whitelist in Firewall	3 min	~35%	Yes
Run as Administrator	1 min	~20%	Yes
Reinstall Riot Vanguard	10 min	~50%	Yes (twice)
Add Antivirus Exclusions	3 min	~30%	No

Percentages total over 100% because these fixes overlap in what they patch up. Fix 2 alone works? Great, done. If not, Fix 2 plus Fix 3 together cover roughly 85% of every case I’ve seen.

Fix 1: Restart Everything Properly

Yes yes, IT Crowd joke. Just hear me out, there’s a right way.

Closing Valorant isn’t enough. Hit Ctrl + Shift + Esc to pull up Task Manager. Search “Riot” in the top. End Task on every single one you find: Riot Client, RiotClientServices, RiotClientUx, Vanguard, all of it. Now reboot your PC. Full reboot, not sleep, not hibernate. When you’re back on the desktop, give things 30 seconds before you relaunch Valorant.

Why this actually works: the Vanguard kernel driver only initializes at boot. Last session died weird? Leftover process fragments can block the driver from loading cleanly next time. A real restart nukes all that baggage.

Fix 2: Set the VGC Service to Automatic

The fix that probably solves your problem. Like two out of three times, this is the one that clears the VAN 81 Valorant error for good.

1. Hit Win + R to pop the Run dialog
2. Type services.msc and enter
3. Scroll down until you spot vgc
4. Right-click vgc, pick Properties
5. Change Startup type to Automatic
6. Status showing Stopped? Hit Start
7. Apply, then OK
8. Reboot, launch Valorant

Get a message like “Windows could not start the vgc service on Local Computer. Error 1: Incorrect function”? Your Vanguard install is cooked. Jump to Fix 5.

Fix 3: Whitelist Valorant and Vanguard in Windows Firewall

Firewall can silently kill Riot’s traffic without bothering to tell you. Open it up and double-check manually.

1. Hit Win + S, search “Windows Defender Firewall”
2. Click Allow an app or feature through Windows Defender Firewall
3. Hit Change settings (admin password prompt may show up)
4. Scan the list for Valorant and Riot Client
5. Both Private and Public checkboxes ticked? They should be
6. Missing from the list? Click Allow another app and browse to them

Where do those files live? Defaults are C:\Riot Games\VALORANT\live\VALORANT.exe for the game itself and C:\Riot Games\Riot Client\RiotClientServices.exe for the client. Installed to a different drive? Look there instead. Add both.

Reboot after, yes I know you’ve restarted like four times by this point. Firewall rules need a fresh network session or they don’t actually kick in. After the reboot, the VAN 81 Valorant error should be gone if the firewall was your issue.

Fix 4: Run Valorant as Administrator

Sometimes VAN 81 is just a permissions thing. Admin rights can clear it up in a minute.

1. Right-click your Valorant desktop shortcut
2. Pick Open file location
3. Right-click VALORANT.exe in the live folder, hit Properties
4. Switch to the Compatibility tab
5. Tick Run this program as an administrator
6. Apply

Repeat the same routine for RiotClientServices.exe in the Riot Client folder. Reboot.

Fix 5: Reinstall Riot Vanguard

Did Services throw you an “Incorrect function” error when you tried to start vgc? Your Vanguard install is toast. Good news is you only need to reinstall Vanguard, not the whole game. Way faster.

1. Hit Win + R, type appwiz.cpl, enter
2. Find Riot Vanguard in the program list
3. Right-click, Uninstall
4. Reboot
5. Launch Valorant through the Riot Client
6. Valorant sees Vanguard is gone, auto-reinstalls it
7. Reboot one more time after Vanguard finishes setting up

Side note on VPNs: turn them off. Riot’s own support confirms VPNs can conflict with Vanguard. Ran into this myself with NordVPN a while back, it was auto-connecting on startup and I had no clue for like an hour why VAN 81 wouldn’t go away.

Fix 6: Add Vanguard to Antivirus Exclusions

Running third-party antivirus (not Windows Defender)? Add these paths to your AV’s exclusion list:

• C:\Program Files\Riot Vanguard\
• C:\Riot Games\VALORANT\
• C:\Riot Games\Riot Client\

Quick diagnostic trick: disable your antivirus entirely, try Valorant. If it boots up clean, your AV was the problem. Now add those exclusions and flip protection back on. Don’t leave AV off forever, obvious reasons.

VAN 81 vs Other VAN Errors: What’s the Difference?

Valorant has a whole zoo of VAN errors and they blur together. Different causes though, so knowing which you’re facing matters. Don’t waste time throwing VAN 81 fixes at a VAN 9001 problem.

Error Code	Primary Cause	Key Fix
VAN 81	VGC service not running or blocked	Set VGC to Automatic, whitelist firewall
VAN 57	Vanguard didn’t initialize on boot	Restart PC, reinstall Vanguard
VAN 68	System locale/region mismatch	Set system locale to match your region
VAN 9001/9003	Secure Boot or TPM 2.0 disabled	Enable Secure Boot and TPM in BIOS
VAN 1067	Vanguard crashed during startup	Reinstall Vanguard, update Windows
VAN: RESTRICTION	System doesn’t meet security requirements	Enable required BIOS settings (HVCI, etc.)

Hitting multiple Valorant error codes at once? The underlying issue is almost always a deeper Vanguard problem. Clean reinstall of both Vanguard and Valorant is your move.

Advanced Fixes: Command-Line Methods

This section is for anyone comfortable popping open Command Prompt. Handles stuff the Services UI can’t touch. You’ll need admin cmd: Start menu, type cmd, right-click the result, Run as administrator. Yes that exact click sequence or it won’t work.

Reset the VGC Service via Command Line

Services window crashes or vgc doesn’t even show up there? Force-register it manually:

sc config vgc start= auto
sc start vgc

That space after start= is not a typo. Windows quirk, been there since Server 2003, whatever. “Access denied” means your cmd isn’t actually running as admin.

Reset Windows Network Stack

VAN 81 can come from a corrupted TCP/IP stack, even when browsing feels normal. Flush it:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Reboot once you’ve run all five. Kind of a nuclear option but totally safe on Windows 10 and 11.

Run System File Checker

Vanguard sometimes crashes because a Windows system file is corrupted. SFC plus DISM can repair that:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

SFC runs about 10 minutes. DISM can eat 20 or more but it catches deeper Windows corruption that SFC alone misses. Run both, reboot.

Common Mistakes That Make VAN 81 Worse

After lurking enough Discord support channels, these are the repeat offenders when people try to fix the VAN 81 Valorant error. Either they stretch the fix out forever or actively make things worse.

Deleting Vanguard Files Manually

Do not go digging into C:\Program Files\Riot Vanguard\ and yeet random files. Vanguard flags this as tampering and you can genuinely get your account banned. Uninstall the legit way through Add/Remove Programs or not at all.

Disabling Vanguard Because “It’s Intrusive”

Some guides out there tell you to turn off Vanguard when you’re not gaming. That’s a one-way ticket to VAN 81. Leave it on. If the privacy angle bothers you enough, the real answer is uninstalling Valorant, not hobbling the anti-cheat.

Running Old Vanguard Bypass Tools

Any third-party tool promising to “fix” Vanguard by patching it is going to HWID-ban you. No such thing as a safe bypass, full stop. The only legitimate fixes are right here in this guide.

Skipping the PC Restart (Top VAN 81 Valorant Error Mistake)

Every fix here says reboot for a reason, I’m not padding. Vanguard’s kernel driver loads at boot, period. Skip the reboot and your “fix” just… doesn’t apply. This is the single biggest reason people claim “nothing works.” The fix usually worked, they just never restarted.

Running Valorant Before Vanguard Loads

After a reboot, give Vanguard like 30 seconds to wake up. Clicking Play the second your desktop appears can hit VAN 81 even when you did everything right, because VGC is still initializing. Patience pays.

What If Nothing Works?

All six fixes done and the VAN 81 Valorant error still blocking you? Couple more things to try before bothering support.

Run a Windows file integrity check. Open cmd as admin, type sfc /scannow. Looks for corrupted Windows files that could be knocking Vanguard’s driver around. 10 minutes or so.

Update Windows fully. Settings > Windows Update, install everything that’s pending. Vanguard enforces minimum Windows builds, and old builds cause compatibility weirdness.

Check BIOS settings. On Windows 11, Vanguard needs Secure Boot and TPM 2.0 enabled. Either one off means you’ll get VAN 81 or a VAN: RESTRICTION message. How you enable those depends entirely on your motherboard, so check the manufacturer’s docs.

None of that helping? Submit a ticket through Riot’s support system. System specs, what you tried, screenshots of the error. Riot support can peek at server-side logs you can’t see.

What to Include When Reporting the VAN 81 Valorant Error

Tickets move faster when you front-load the info. Put this stuff in the ticket:

• Windows version and build (Win + R, winver)
• CPU, GPU, RAM (Task Manager > Performance)
• Exact error text and a screenshot
• When the error started (after what patch or install)
• What you already tried (copy from this guide, saves everyone time)
• Your antivirus (brand, version)
• VPN usage (which one, if any)
• Secure Boot and TPM status (System Information shows both)
• Your Valorant Riot ID

A ticket this detailed usually gets a human response within a day or two. The vague “my game is broken plz help” tickets either drag for a week or close without anyone actually reading them.

Community Resources for the VAN 81 Valorant Error

Before you even submit that ticket, check these spots. Sometimes a super-specific fix for a recent patch already got posted by another sufferer:

• r/VALORANT: search “VAN 81” on the sub, sort by new
• Riot Games Discord: #tech-support has volunteer helpers who solve stuff fast
• @RiotSupport on Twitter/X: they post when widespread issues are live
• status.riotgames.com: official outage reporting, real-time

From what I’ve read across hundreds of Reddit threads, roughly 80% of VAN 81 posts get resolved by one of the six fixes above. The remaining 20% are almost always Secure Boot or TPM issues on fresh Windows 11 installs, which means BIOS time.

How to Prevent the VAN 81 Valorant Error from Coming Back

Once you’ve fixed it, couple of habits will stop this error from crawling back.

Keep VGC on Automatic startup. After big Windows updates, it’s worth a 30-second check in services.msc to confirm nothing got reset. Updates love stealthily flipping services back to Manual.

Leave Vanguard alone. Some “make your PC faster” guides online tell you to disable services you don’t recognize. VGC looks like one of those vague services, and killing it guarantees you hit VAN 81 on your next launch.

Installing new AV software? Add Vanguard exclusions before your first Valorant launch, not after. Preventing a conflict takes 30 seconds, debugging one takes an hour.

Setting up a ranked-ready Valorant account on a fresh PC? Run through these steps before you even log in. Nothing more frustrating than grabbing a Valorant smurf account and then being stuck at an error screen for an hour before you get to play.

FAQ

What does VAN 81 mean in Valorant?

It’s a connection error caused by Vanguard’s VGC service either failing to start or getting blocked from reaching Riot’s servers. Full message on screen: “VALORANT has encountered a connection error. Please relaunch the client to reconnect.”

How do I fix VAN 81 in Valorant?

Fastest fix: set VGC to Automatic startup. Win + R, type services.msc, find vgc, right-click Properties, Startup type to Automatic, reboot. That alone fixes about two-thirds of cases. Didn’t work? Next step is whitelisting Valorant and Vanguard in Windows Firewall.

Is VAN 81 caused by internet problems?

Almost never. The word “connection” in the error message throws people off. In reality VAN 81 comes down to VGC either not running or getting choked by your firewall or antivirus. Your actual internet is fine 95% of the time.

Can antivirus software cause VAN 81?

Yep. Third-party AV (Avast, Norton, Kaspersky, etc.) sometimes blocks VGC because it runs at kernel level. Either add Riot Vanguard to your AV’s exclusion list or flip the AV off temporarily to test.

Do I need to reinstall Valorant to fix VAN 81?

Usually no. Most players clear it up by enabling VGC or fixing firewall rules. If files are actually corrupted, reinstalling just Riot Vanguard (not the whole game) is enough. Full Valorant reinstall is the last thing to try, not the first.

Does VAN 81 happen on console or only PC?

PC only. The error comes from Riot Vanguard, which runs as a kernel driver on Windows. Console Valorant doesn’t use Vanguard at all, so PlayStation and Xbox players never see this one.

Last updated: April 2026