Valorant Error Codes
Valorant errors come from two places: Riot Vanguard (the VAN codes) and Riot's servers/client (the VAL and numeric codes). Here's what each common one means and how to clear it.
Error codes
VAN 9003
Vanguard requires TPM 2.0 / Secure Boot (Windows 11)
Cause: Riot Vanguard on Windows 11 needs TPM 2.0 and Secure Boot enabled, and they're currently off in your BIOS.
- Enable TPM 2.0 (or fTPM/PTT) in your BIOS/UEFI.
- Enable Secure Boot in the BIOS Boot menu.
- Restart the PC so Vanguard can load.
VAN 152
Your machine is HWID-banned by Vanguard
Cause: Vanguard banned the hardware ID on this PC, usually tied to a previous ban.
- If you believe it's a mistake, submit a ticket to Riot Support.
- A hardware ban is not fixed locally — appeal is the only route.
VAN 68 / VAN 81
Connection problem between the client and Vanguard/servers
Cause: A network drop or Vanguard failing to communicate, sometimes after a Windows update.
- Restart your PC so Vanguard restarts with it.
- Restart your router and flush DNS.
- Reinstall Riot Vanguard if it repeats.
VAN 1067
Vanguard won't run (TPM/Secure Boot on Win11) or a driver conflict
Cause: Similar to 9003 — TPM 2.0/Secure Boot off, or a virtualization/driver conflict blocking Vanguard.
- Enable TPM 2.0 and Secure Boot in BIOS.
- Update Windows fully.
- Disable memory integrity/virtualization features that conflict, then restart.
Error Code 29
There was an error with the Riot Client / login session
Cause: A client or session glitch, often after a patch — the Riot Client needs a full restart.
- Fully close the Riot Client from Task Manager and relaunch.
- Restart your PC.
- Check Riot's service status for the login queue.
Error Code 39 / 43 / 57
Vanguard/platform failed to initialize (connection to server timed out)
Cause: Vanguard didn't start correctly or the platform couldn't be reached — a service/connection timeout.
- Restart the PC so Vanguard loads at boot.
- Verify Vanguard is running (system tray) before launching Valorant.
- Reinstall Vanguard if the error persists.
VAL 51 / Connection Error
Can't connect to Riot's platform
Cause: A Riot server outage or a network/firewall block reaching the platform.
- Check the Riot/Valorant service status page.
- Restart your router; allow Riot Client and Valorant through the firewall.
- Disable VPN or proxy.
Fixes that work for most Valorant errors
- Check the game's official server status page or its X/Twitter — if servers are down or under maintenance, no local fix will help; wait it out.
- Fully close and restart the game and its launcher (Steam / Epic / EA App / Battle.net / Riot Client).
- Restart your router and, on PC, flush DNS (open Command Prompt and run: ipconfig /flushdns).
- Verify or repair the game files in your launcher so a corrupted update is re-downloaded.
- Make sure the game and your OS are fully updated — most 'version mismatch' errors are an out-of-date client.
FAQ
How do I fix Valorant error VAN 9003?
VAN 9003 means Riot Vanguard needs TPM 2.0 and Secure Boot on Windows 11. Enter your BIOS/UEFI, enable TPM 2.0 (fTPM/PTT) and Secure Boot, then restart. Fully update Windows if it persists.
What is Valorant error code 29?
Error 29 is a Riot Client/login session error, usually after a patch. Fully close the Riot Client via Task Manager, relaunch, and restart your PC if it repeats; check Riot's service status.
Other games
- League of Legends Error Codes — Error Code 003, 004, 0, Bugsplat & More
- Roblox Error Codes — Full List & Fixes (267, 277, 279, 403, 517, 524, 610)
- Steam Error Codes — Disk Write Error, E-502 L3, Content Servers Unreachable & More
- Black Ops 7 Can't Connect to Online Services? Fix HUENEME & NEGEV Errors (2026)
- EA FC 26 Can't Connect to EA Servers? Fix Ultimate Team Disconnects & Ports (2026)
- Path of Exile 2 'Failed to Connect to Instance'? Fix Disconnects & Gateways (2026)
- Arena Breakout: Infinite Connection Failed / ACE Error? Fix 1-1704-30015228 & 7801113 (2026)
- REMATCH Can't Connect to Server? Fix Matchmaking & Connection Lost (2026)