Every Valorant Error Code and How to Fix It Fast
Valorant error codes come in two families: VAL codes for client, connection and account problems, and VAN codes from Riot Vanguard, the anti-cheat. Most VAL codes clear after restarting Valorant and the Riot Client; VAN codes such as VAN 81 or VAN -81 usually need a PC restart or a Vanguard reinstall. VAL 61 is a ban and VAN 152 a hardware ban, which no setting fixes.
VAL vs VAN Valorant error codes: what is the difference?
VAL codes come from the game client and Riot’s services: connection to the servers, the Riot Client, your account, the store. VAN codes come from Riot Vanguard and mean the anti-cheat could not start, could not connect, or found something it will not allow. Restarting the client usually fixes the first family. The second? Often a full PC restart, because Vanguard loads with Windows. Knowing which family you are in saves time, so look at the three letters before the number first.
Riot’s own support page lists the codes and their fixes. Riot also notes that the list can lag behind new issues, so if your code is not explained anywhere, check Riot’s support banners and service status before assuming the problem is on your PC.
Most common Valorant error codes and fixes
Here are the codes players meet most, with Riot’s descriptions:
| Code | What it means | Fix |
|---|---|---|
| VAL 0, 1, 38 | Connection error | Restart Valorant and the Riot Client |
| VAL 5 | Account logged in elsewhere | Log out from all devices, then sign in again |
| VAL 7 | Could not connect to the session service | Check your email for a suspension; check Riot’s status banners |
| VAL 8 to 21 | Riot Client problems | Restart the Riot Client |
| VAL 29 | Network issue | Allow Valorant through your firewall |
| VAL 39, 46 | Server unavailable or platform downtime | Wait and try again later |
| VAL 43 | A system timed out | Restart the Riot Client |
| VAL 44, 45 | Vanguard not initialised, or reboot required | Restart; reinstall Vanguard if it repeats |
| VAL 51 | Problem creating a party | Restart the Riot Client |
| VAL 59 | Login queue token failure | Restart the client and check status banners |
| VAL 61 | Banned from playing Valorant | Submit a support ticket |
| VAN -81 | Vanguard service failed to start | Restart PC and client; reinstall Vanguard and Valorant |
| VAN 128 | Connection error | Restart PC and client; reinstall if it persists |
| VAN 138 | Virtual machine detected | Install and play on native Windows |
| VAN 152 | Hardware (HWID) ban | Submit a ticket; Riot says these typically last four months |
Riot’s list goes further, with codes for chat, voice, store and content services in the 49 to 70 range. Most of them share one fix: restart the client, then open a ticket if it keeps happening.
How to fix VAN 81 in Valorant
VAN 81, and the closely related VAN -81 (“Service Start Failed” in Riot’s list), point to Vanguard not starting or not connecting properly. The fix is the same ladder every time:
- Restart the PC with Restart, not Shut down, so Vanguard actually reloads.
- Open the Riot Client and start Valorant again.
- If it repeats, uninstall Riot Vanguard from Windows Settings, restart, and launch Valorant to reinstall it.
- Still failing? Uninstall both Vanguard and Valorant, restart, and reinstall both.
- Check that the Vanguard service (vgc) is set to start automatically.
If none of that works, something on the PC is likely blocking Vanguard: a driver it considers incompatible, a security suite, or a hardware monitoring tool. Thing is, the error message itself rarely names the culprit, so a clean boot (only Microsoft services plus Vanguard) is the quickest way to find out.
VAL 44, VAL 45 and other Valorant error codes at startup
VAL 44 means Vanguard has not initialised, and VAL 45 means Vanguard wants a reboot. A PC restart usually solves both, since Vanguard loads at startup. If they come back after every restart, reinstall Vanguard.
A related code, VAL 57 in some guides, also points to Vanguard not running. We cover that one in detail in our guide to Valorant error code 57.
VAN 9001 and VAN 9003 on Windows 11
On Windows 11, Vanguard requires TPM 2.0 and Secure Boot. VAN 9001 means TPM 2.0 is not enabled, and VAN 9003 means Secure Boot is off. You switch both on in your motherboard’s BIOS or UEFI setup, often under names like fTPM, PTT or Security Device for TPM, and in the Boot or Security section for Secure Boot.
The catch is that every motherboard’s menus look different. Check the board maker’s manual before changing boot settings. Secure Boot may require Windows to boot in UEFI mode from a GPT disk, which is a bigger change on older installs.
VAL 61 and VAN 152: bans, not bugs
VAL 61 says it plainly: Riot has banned the account from Valorant. Simple as that. Your email usually has the details, and an appeal goes through a support ticket. VAN 152 is a hardware ban on the PC, issued for serious cheating. Riot’s list says these typically last four months. No reinstall or new account changes either.
Bought a used PC and see VAN 152 on a fresh account? Open a ticket and explain. Our page on cheats for Valorant explains why hardware bans exist and how they work.
Seven steps that fix most Valorant error codes
- Check Riot’s service status and support banners for an outage.
- Restart Valorant and the Riot Client completely (exit from the system tray).
- Restart the PC.
- Allow Valorant and the Riot Client through your firewall and security software.
- Turn off VPNs and proxies, including browser-based ones that route all traffic.
- Reinstall Vanguard, then Valorant if needed.
- Submit a ticket with your logs attached.
Honestly, steps one to three solve the majority. Many players jump straight to network resets and reinstalls while the real problem is a server incident that clears on its own within the hour.
Valorant will not open at all
No error code, no window, nothing? Then start with the basics. Make sure the Riot Client is fully closed (check the system tray), restart the PC, and launch Valorant from the Riot Client rather than an old shortcut. If the client opens but Valorant does not, use the repair option in the Riot Client settings for Valorant.
Next, look at what else runs at startup. Overlays, RGB and fan control apps, hardware monitors and some anti-virus add-ons interfere with Vanguard more often than people expect (the small utility you forgot you installed is a classic). A clean boot with only Microsoft services and Vanguard tells you within ten minutes whether a third-party program is the cause.
Error codes after a patch
Patch days bring their own wave of codes. A new client version, a Vanguard update and a crowd of players logging in at once can produce connection and login errors that disappear within hours. Let the Riot Client finish updating. Restart after a Vanguard update. And check the status page before you start changing settings, because a patch-day error is usually shared by thousands of other players at the same moment.
If a code appears only after a patch and survives a full day, while friends on the same region play normally, repair the game first. Interrupted downloads are a common cause, and a repair replaces broken files without a full reinstall.
How to check Valorant server status
Riot posts outages and maintenance on its service status page for each region, and VAL 39 or VAL 46 usually line up with an incident there. Our Valorant server status page shows the current state too. Servers down? Wait. Nothing on your side will help, not even a fifth reinstall.
How to send a useful support ticket
Real talk: a ticket that says “error, help” gets a list of the same steps you already tried. A useful one includes the exact code, when it appears (login, agent select, mid-match), what you already did, your region and whether League or other Riot games work on the same PC. Attach the logs Riot asks for; the support site explains where to find them.
To be fair to support, many codes look identical from the outside and only the logs show the difference. Ten minutes spent on a complete first ticket usually saves days of back and forth.
Valorant error codes in ranked games
An error during a ranked match counts as a disconnect. Reconnect as fast as you can, because reconnecting usually lets you rejoin the match in progress. Repeated disconnects can lead to queue penalties, so fix a recurring code before queuing ranked again. For what it’s worth, a stable connection matters for more than errors; if fights feel off even without a code, our guide to desync in Valorant covers the network side.
FAQ
What is the difference between VAL and VAN Valorant error codes?
VAL codes come from the Valorant client and Riot’s services. VAN codes come from Riot Vanguard, the anti-cheat.
How do I fix VAN 81 in Valorant?
Restart the PC, then the Riot Client. If it repeats, reinstall Vanguard, and if that fails, reinstall both Vanguard and Valorant.
What does VAL 61 mean?
It means the account is banned from playing Valorant. Check your email for details and submit a support ticket to appeal.
How long does VAN 152 last?
Riot’s error list says hardware bans typically last four months.
How do I fix VAN 9001 and VAN 9003?
Enable TPM 2.0 (VAN 9001) and Secure Boot (VAN 9003) in your BIOS or UEFI settings on Windows 11.
Can I play Valorant in a virtual machine?
No. Vanguard detects virtual machines and shows VAN 138. Install Valorant on native Windows.
What does VAL 5 mean?
Your account was logged in elsewhere. Log out from all devices and sign in again.
