
VALORANT error VAN -81 is a Riot Vanguard connection error. Riot’s official first step is to restart the PC and the Riot Client. If the same code returns after a full restart, reinstall Riot Vanguard and VALORANT through normal Windows controls, then contact Riot Support if a clean installation still fails.
Last verified: , during VALORANT Patch 13.05.
Riot classifies VAN -81 as a connection error involving Vanguard. The leading minus sign is part of the official code. It is different from a VAL client code and from named Vanguard security errors such as VAN 9001, VAN 9002, or VAN: RESTRICTION.
The message does not prove that your home internet is broken. The failed connection can sit between the Riot Client, Vanguard, Windows, and Riot’s services. That is why the most useful first step is a complete restart rather than changing random network or BIOS settings.
If the Riot Client is stuck downloading rather than showing VAN -81, use the separate VALORANT update troubleshooting guide. Fix the symptom you actually see instead of combining unrelated procedures.
Reinstallation is the final self-service step in Riot’s VAN -81 guidance, not the first. Use Windows’ installed-app controls and Riot’s official installer:
Do not manually remove Windows services, copy Vanguard files from another PC, or run cleanup software against the registry. If Windows cannot install to the selected drive, stop and diagnose that separate issue with our VALORANT install-path guide.
Because Riot labels VAN -81 a connection error, rule out a local network interruption before reinstalling:
Do not turn the firewall or antivirus off as a blanket test. If security software reports a specific block, verify the file is Riot-signed and follow Riot’s official exception guidance or contact the product’s support team.
Similar-looking errors have different resolutions. Write down the full message or take a screenshot that excludes private account details. For example, VAN 57 identifies a different Vanguard-not-running condition, while VAN 9001 and VAN 9003 relate to specific Windows security checks.
If the message changes after a restart, follow the current code—not the one you saw earlier. Do not apply TPM, Secure Boot, virtualization, or exploit-protection instructions unless Riot’s page for the exact code tells you to.
Submit a Riot Support ticket when VAN -81 survives a complete restart and clean official reinstall, or when Windows reports a driver, installer, or security error you cannot safely interpret. Include:
Download diagnostic tools only from Riot Support. Never attach passwords, multi-factor codes, recovery codes, or payment details to a ticket.
Riot lists the code as VAN -81, with a minus sign. People commonly search for “VAN 81,” but recording the exact code helps prevent it from being confused with another error.
A service incident can create connection symptoms, so check Riot’s regional status first. The code alone does not prove an outage or a local network failure.
Riot’s published VAN -81 instructions do not require a manual service edit. Restart first, then use the official reinstall route if necessary. Avoid scripts and registry changes from an unknown guide.
No. Do not broadly disable security software. Investigate a specific block with official Riot guidance and the security vendor instead.
Your VALORANT inventory and rank are tied to the Riot Account, not the local game installation. Make sure you sign back into the correct account after reinstalling.
For VAN -81, check Riot’s status, restart the PC and Riot Client, finish official updates, and test the normal connection. If the exact code persists, reinstall Vanguard and VALORANT through Windows and Riot’s installer. Stop before making security or registry changes and send Riot Support the code and logs instead.
Posted On: February 3rd, 2026