The popup blames your connection. The evidence usually points somewhere else: a small Windows service called vgc that Vanguard cannot live without. Start it, unblock it and this error tends to fold quickly.
By Neeraj Singh ~9 min Updated Jul 2026 84% found this helpful
Error message
VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -81
Quick fix
Seeing “VALORANT has encountered a connection error” with code VAN -81? Do not reach for the router yet, this popup misleads. The usual culprit is the vgc service on your own PC sitting stopped or blocked. Press Win+R, run services.msc, set vgc to Automatic and start it. Method 1 walks you through it.
Service running but the code returns? Then something is blocking vgc, usually the firewall or antivirus. Methods 3 and 4 clear both.
Error appeared right after a Windows update? Classic. Updates flip vgc back to Manual and reset permissions, the same Method 1 undoes it.
Nothing on your side helps? A genuine Riot incident produces the same popup, thirty seconds on the Riot Games Service Status page rules that out before you dig deeper.
The connection error that usually is not one
Riot's support page files VAN -81 under connection errors, and the popup repeats it, which sends most players off to restart routers and test speeds. The evidence points closer to home. Vanguard runs its user-mode side through a Windows service called vgc, and when that service is stopped, set to Manual or walled off by the firewall, the game cannot complete its anti-cheat handshake, so it reports the only thing it knows: the connection failed. It did, but the snapped link sits inside the case, game to service, while the road out to Riot's servers is usually clear. That is why the service fix clears most cases in two minutes while network tinkering goes nowhere, and it is the whole reason this page starts at services.msc instead of your router.
Figure 1: where VAN -81 actually breaks
✓ How to fix it
Work top to bottom, the order follows how often each fix wins. Every method ends with its success sign.
Method 1
Set the vgc service to Automatic and start it
1Press Win+R, type services.msc and press Enter. Scroll the list to vgc.
2Double-click it, set Startup type to Automatic, click Apply, then click Start if the service is not already running and confirm with OK.
3Restart the PC and launch VALORANT. Reaching the login and lobby without the popup is your success sign, and this single method settles most VAN -81 cases, especially the ones that began after a Windows update flipped the service to Manual.
Method 2
Do the full restart chain
1If the service was already running, clear the stuck-state case: close the game, open Task Manager and end every VALORANT, Riot Client and Vanguard process you find.
2Because Vanguard was ended, restart the PC rather than relaunching straight away, its driver only loads cleanly at boot.
3Open the Riot Client as administrator while you test, restricted permissions have produced this code too, let it finish any update and start the game. A clean login after the reboot means a leftover process was holding the handshake, case closed.
Method 3
Allow vgc and the game through the firewall
1Search Allow an app through firewall, click Change settings and make sure VALORANT, Riot Client and vgc (shown on some systems as Vanguard user-mode service) are listed with both Private and Public ticked.
2Anything missing? Click Allow another app > Browse, and add vgc.exe from C:\Program Files\Riot Vanguard, then tick both network boxes for it.
3Relaunch the game. A stable login confirms the firewall was swallowing the service's traffic, the other common VAN -81 story besides the stopped service itself.
Figure 2: the firewall allow-list, both branches
Method 4
Clear antivirus and software conflicts
1Add the whole C:\Program Files\Riot Vanguard folder to your antivirus exclusions, third-party security tools interfere with vgc often enough that this is standard hygiene for Riot games.
2Check the quarantine while you are there and restore any Riot file the antivirus ate silently. Other anti-cheat software from different games and always-on VPN clients belong on the suspect list too, turn them off while you test, and if a VPN keeps interfering, uninstall it fully, their network drivers can linger even when disconnected.
3Launch the game. If the code only stays away while the conflicting tool is off, you have found your culprit, keep the exclusion in place or the tool retired during play sessions.
Method 5
Reinstall Vanguard cleanly
1For corrupted Vanguard files, do the deep clean: open Command Prompt as administrator and run sc delete vgc and sc delete vgk, then restart the PC.
2Delete the Riot Vanguard folder from C:\Program Files, launch VALORANT and let it reinstall Vanguard fresh, then restart once more so the driver loads at boot.
3Sign in and play a match. A fresh install that holds through a full session closes the corrupted-files case, and your progress and purchases are untouched throughout, they live with your account.
Method 6
Rule out Riot's side, then escalate
1Check the Riot Games Service Status page for your region, the same popup appears during genuine incidents, and waiting is the only fix for those.
2Status clean and the code still standing after Methods 1 to 5? Open a Riot Support ticket and list what you have done, service confirmed running, firewall entries in place, clean reinstall completed. That summary skips the first three replies of any support conversation.
3A reply that digs into your specific system, rather than restating the basics, is what that preparation buys you.
Keep the minus sign straight when searching: VAN -81 (this page) is the service-linked launch failure, while plain VAN 81 barely exists as a separate error, most guides use the two spellings interchangeably. The nearby codes that are genuinely different: VAN -1 and “Vanguard not initialized” have their own guide, and VAN 79 is this error's positive-numbered sibling.
Common causes of VAN -81
The vgc service stopped, or flipped to Manual by a Windows update or cleanup tool.
Windows Firewall blocking vgc, VALORANT or the Riot Client from connecting.
Antivirus tools quarantining Riot files or wrestling with the anti-cheat.
A stuck Riot or Vanguard process left over from a crash or forced shutdown.
Corrupted Vanguard files, or the rare genuine Riot-side incident.
Expert insight
“VAN -81 taught me to distrust error popups. It says connection error, and I have watched people spend an evening on router settings when services.msc would have ended it in ninety seconds. My first question is always what changed, and the answer is usually a Windows update that flipped vgc to Manual without asking. Set it to Automatic, start it, restart, done. The stubborn ones are nearly always a security tool sitting on the service, which is why the firewall boxes and the antivirus exclusions are steps two and three in my book, and the router is not in the book at all.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
Make sure this is the error you have
The service-failure family is crowded, so match your popup. A message saying “Vanguard not initialized”, or the Riot-documented VAN -1, belongs to the vgc initialization guide. VAN 79 is the positive-numbered sibling with its own service-first ladder in the VAN 79 guide. The transient trio VAN 0, 1 and 6 live in the VAN 0 / 1 / 6 guide, and mid-game drops with VAN 84 in the VAN 84 guide. This page is only for the launch-time connection popup carrying Error Code: VAN -81.
Frequently asked questions
What does VALORANT error code VAN -81 mean?
Riot lists VAN -81 as a connection error, but the usual cause sits on your PC: the vgc service, the Windows service Riot Vanguard runs through, is not running or is blocked from connecting. Start the service, clear anything blocking it and the error goes with it.
Is VAN -81 caused by my internet?
Rarely. Despite the connection-error wording, the failing link is usually between the game and the vgc service on your own machine, not between you and Riot. That is why service and firewall fixes clear it while router restarts mostly do not. A genuine Riot outage can produce it too, which a quick status-page glance rules out.
What is the vgc service?
vgc is the Windows service that runs Riot Vanguard's user-mode side. VALORANT will not start matches unless vgc is running, and Windows updates or cleanup tools sometimes flip it from Automatic to Manual or Disabled, which is exactly when codes like VAN -81 start appearing at launch.
What is the difference between VAN -81 and VAN 79?
They are close siblings: both strike at launch and both usually trace to the vgc service. The difference is mostly which popup and code Riot shows you. The fixes overlap heavily, service first, then firewall, then reinstall, so if one guide clears one code, its steps very likely clear the other.
Which firewall settings does VAN -81 need?
Allow VALORANT, the Riot Client and vgc through Windows Defender Firewall with both Private and Public ticked. If vgc is missing from the list, add it via Allow another app, it lives in C:\Program Files\Riot Vanguard. Third-party antivirus needs the same treatment, add the Riot Vanguard folder to its exclusions.
Will reinstalling Vanguard delete my progress or skins?
No. Vanguard is only the anti-cheat layer, and your progress, purchases and settings live with your Riot account, not inside Vanguard's folder. You can uninstall it, delete its folder and let the game reinstall it without touching anything you own.
Why did VAN -81 start after a Windows update?
Updates are the classic trigger: they can flip the vgc service back to Manual, leave it stopped after the restart or reset firewall permissions. Set vgc to Automatic, start it and re-check the firewall entries, that combination undoes what the update changed.
When should I contact Riot Support about VAN -81?
After the service is confirmed running, the firewall entries are in place and a clean Vanguard reinstall has not helped, and the status page shows no incident. At that point something deeper in the system is interfering, and a ticket describing what you have already done gets a faster, better answer.
Still not working?
If even a fresh Vanguard fails, reinstalling VALORANT itself is the final local step, slow but occasionally the one that works, with your progress safe on your account as ever. Before that, check what vgc does the moment the error fires: open services.msc, launch the game and watch whether the service stays Running or dies at the handshake, a service that keeps stopping usually has a security tool or corrupted install underneath, which points you back to Methods 4 and 5 with a suspect in mind. Browse the full set of Riot Vanguard error guides, or submit your error to us for a tailored fix.
