VALORANT Error Codes, Explained
39 errorsChecked against Riot dailyType the code VALORANT just gave you (VAL 43, VAN 216) to see what it means and the fix Riot gives for it. VAL codes belong to VALORANT. VAN codes come from Vanguard, the anti-cheat VALORANT shares with League, and League players have their own page for every VAN code.
Is it you or Riot? When half the server gets kicked at once, it's not your PC. Check Riot's service status page for VALORANT first.
Riot's VALORANT table is flagged as out of date. Riot says a bug is making some VALORANT errors display incorrectly, so a code can come up that doesn't fit the problem. The VAN pages here lean on Riot's separate Vanguard articles, which carry no such warning.
190 error lines indexed. Part of the line is enough.
VALORANT's own codes (VAL)
Account was logged into elsewhere.Riot saw your account signed in on another device or session, so it closed this one.
VAL 7 couldn't connect to the session serviceCouldn't connect to session service.VALORANT couldn't connect to Riot's session service. Riot gives two possible reasons: a suspension on your account, or trouble on Riot's side.
VAL 9 a problem with the Riot ClientProblems with the Riot Client.Riot puts every code from 8 to 21 down to the Riot Client itself having a problem.
VAL 19 the Riot Client ran into troubleProblems with the Riot Client.VAL 19 is in the range Riot lists as Riot Client problems, codes 8 through 21.
VAL 29 your firewall is blocking VALORANTThis is a network issue.Riot calls 29 a network issue and traces it to Windows Firewall, or antivirus, not letting VALORANT through.
VAL 39 VALORANT's servers aren't availableUnavailable ServerThe VALORANT server you need is down, for scheduled maintenance or an emergency fix.
VAL 43 a system timed outA system has timed out.Riot's table says a system timed out. The Riot Client waited for a response that never arrived.
VAL 51 VALORANT couldn't create a partyProblem creating a party.VALORANT's party system failed to create a party for you, so you can't get past the main menu.
VAL 59 the login queue failedLoginQueueFetchTokenFailureVALORANT couldn't get through Riot's login queue. Riot's internal name for it is LoginQueueFetchTokenFailure.
VAL 61 you've been banned from VALORANTYou have been banned from playing VALORANTYour account has a ban on playing VALORANT. It isn't a technical fault.
VAL 68 VALORANT can't load what you ownCapEntitlementsFetchErrorVALORANT couldn't fetch the list of content your account owns. Riot's internal name for this is CapEntitlementsFetchError.
Vanguard codes (VAN) in VALORANT
Connection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 0Vanguard couldn't confirm the PC was ready to run VALORANT, or it hit a problem during its own startup.
VAN -1 Vanguard didn't startConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -1Vanguard failed to start, or one of the Windows services it depends on wasn't available when VALORANT asked for it.
VAN 6 Vanguard failed while startingConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 6Vanguard either couldn't verify the PC was ready for VALORANT or ran into trouble while it was starting up.
VAN 68 Vanguard lost its sessionConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 68Vanguard dropped the session or connection it relies on, either while VALORANT was starting or partway through a game.
VAN -72 Vanguard couldn't confirm it was readyConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -72Vanguard couldn't start, hold its connection, or confirm everything was ready, either while VALORANT launched or during a match.
VAN -79 Vanguard lost its grip during a matchConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -79Vanguard had trouble starting, keeping its connection, or confirming your PC was ready, at launch or in the middle of a game.
VAN -81 Vanguard's service failed to startConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -81Riot's VALORANT table labels -81 as a failed service start: Vanguard didn't start, or couldn't stay connected once VALORANT was running.
VAN 84 Vanguard couldn't confirm your PC is readyConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 84Vanguard couldn't confirm that the PC was ready to run VALORANT, or it failed while initializing.
VAN -92 Vanguard dropped out mid-launch or mid-gameConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -92Vanguard couldn't start properly, lost its connection, or couldn't confirm the PC was ready while VALORANT was launching or running.
VAN -102 Vanguard couldn't start or stay connectedConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -102Vanguard struggled to start, keep its connection, or confirm your PC was ready, either as VALORANT launched or while you played.
VAN -104 Vanguard couldn't hold its connectionConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN -104Vanguard ran into trouble starting, keeping its connection, or confirming the PC was ready, at launch or during a match.
VAN 128 a Vanguard trust check failedVanguard Error: VAN 128. An unexpected error with Vanguard has occurred and the client will now close.Vanguard couldn't complete one of the checks it runs at startup to confirm Windows can be trusted.
VAN 133 Vanguard's PC check didn't passConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 133Vanguard couldn't verify that the PC was ready for VALORANT, or something went wrong while it initialized.
VAN 135 Vanguard failed to verify or startConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 135Vanguard couldn't confirm your PC was ready to run VALORANT, or ran into a problem while initializing.
VAN 138 Vanguard won't run in a virtual machineConnection Error: VALORANT encountered a connection error. Please relaunch the client to reconnect.VALORANT or Riot Vanguard is running inside a virtual machine or another unsupported virtualized setup.
VAN 140 the game, client and Vanguard didn't start togetherConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 140Something went wrong with how VALORANT, the Riot Client and Vanguard started up or connected to each other.
VAN 152 this PC has a hardware banConnection Error: A review detected that action of an account playing on this device violated the User Rules (Section 7) of our Terms of Service. […] Error Code: VAN 152Riot has banned this computer's hardware from playing, whichever account signs in. It isn't a fault you can fix.
VAN 185 your session with Vanguard brokeConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 185The session between VALORANT, the Riot Client and Vanguard broke down, at launch or while you were playing.
VAN 216 you hit Play too often, now wait 30 minutesVanguard Error: VAN 216. An unexpected error with Vanguard has occurred and the client will now close.VALORANT was launched too many times in a short spell, so Vanguard is making you wait. Nothing on your PC is broken by this code.
VAN 289 something on your PC is interfering with VanguardConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 289Another program on your PC is interfering with Vanguard or changing how it runs. That's the only cause Riot gives.
VAN 293 Vanguard couldn't start or stay connectedConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 293Vanguard struggled to start, keep its connection, or confirm everything was ready while VALORANT was launching or running.
VAN 302 antivirus or another program is blocking VanguardConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 302Vanguard spotted a program interfering with it or with the game. Riot names antivirus as one likely culprit.
VAN 1067 Vanguard hit a problem checking in with your PCConnection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 1067Vanguard ran into an unexpected problem while starting up or checking in with your system.
VAN 9001 turn on TPM 2.0VAN9001. This build of Vanguard requires TPM 2.0 to be enabled in order to play.Vanguard needs TPM 2.0 for its security checks, and it doesn't see TPM 2.0 enabled on this PC.
VAN 9002 Exploit Protection is switched offVAN9002: This build of Vanguard requires Control Flow Guard (CFG) to be enabled in system exploit protection settings.Windows Exploit Protection has been turned off or changed, and Vanguard needs Control Flow Guard and its siblings running.
VAN 9003 Secure Boot is offVAN9003. This build of Vanguard requires secure boot to be enabled in order to play.Secure Boot isn't turned on in this PC's firmware, and Vanguard won't let VALORANT run without it.
VAN 9005 TPM 2.0, Secure Boot and VBS aren't all set upVAN9005: This version of Vanguard requires TPM version 2.0 and UEFI compliant firmware in order to use Virtualization-based Security (VBS)Vanguard wants to use Virtualization-based Security, which needs TPM 2.0 and UEFI firmware, and it can't find that setup on this PC.
VAN 9090 TPM 2.0 needs setting up againVAN 9090: TPM 2.0 initialization failure. The TPM 2.0 (Trusted Platform Module) has recently been cleared, please reinitialize your TPM.TPM 2.0 is present but didn't initialize properly, often because it was recently cleared and needs setting up again.
No match. Try just the number, or check the full table below.
Every number in Riot's VALORANT table
Riot's VALORANT support site lists its codes by number alone, 41 rows in all. Each number is below with the label Riot gives it. Where there's a page here, the code links to it.
| Code | Riot's label | Our page |
|---|---|---|
| 0 | Connection Error | VAN 0 |
| 1 | Connection Error | Riot's table only |
| 4 | Your display name is invalid. | Riot's table only |
| 5 | Account was logged into elsewhere. | VAL 5 |
| 7 | Couldn't connect to session service. | VAL 7 |
| 8 - 21 | Problems with the Riot Client. | VAL 9 VAL 19 |
| 29 | This is a network issue. | VAL 29 |
| 31 | Failed to get player name information. | Riot's table only |
| 33 | The Riot Client process was closed. | Riot's table only |
| 38 | Connection Error | Riot's table only |
| 39 | Unavailable Server | VAL 39 |
| 43 | A system has timed out. | VAL 43 |
| 44 | Vanguard not initialized. | Riot's table only |
| 45 | Vanguard Reboot required. | Riot's table only |
| 46 | Platform downtime. | Riot's table only |
| 49 | Chat did not initialize. | Riot's table only |
| 50 | Voice did not initialize. | Riot's table only |
| 51 | Problem creating a party. | VAL 51 |
| 52 | Problem fetching skill information for players. | Riot's table only |
| 53 | Problem with Riot Client chat. | Riot's table only |
| 54 | Content service failure. | Riot's table only |
| 55 | ApplicationRepairManagerInitFailure | Riot's table only |
| 56 | LegalInfoInitFailure | Riot's table only |
| 57 | PlayerAffinityInitFailure | Riot's table only |
| 58 | RSOValidationFailure | Riot's table only |
| 59 | LoginQueueFetchTokenFailure | VAL 59 |
| 60 | PatchInitFailure | Riot's table only |
| 61 | You have been banned from playing VALORANT | VAL 61 |
| 62 | NoGamepodsToPingFailure | Riot's table only |
| 63 | ManagerDeleted | Riot's table only |
| 64 | SessionFetchFailure | Riot's table only |
| 65 | PatchAvailabilityInitFailure | Riot's table only |
| 66 | ContentIndexInitFailure | Riot's table only |
| 67 | ChatFriendMetadataInitFailure | Riot's table only |
| 68 | CapEntitlementsFetchError | VAL 68 |
| 69 | CapWalletsFetchError | Riot's table only |
| 70 | StoreOffersFetchError | Riot's table only |
| -81 | Service Start Failed | VAN -81 |
| 128 | VALORANT has encountered connection error. Please relaunch client to reconnect | VAN 128 |
| 138 | VALORANT has encountered connection error. Please relaunch client to reconnect | VAN 138 |
| 152 | HWID ban | VAN 152 |
Sources: Riot Games Player Support's Error Codes and Solutions in VALORANT table for the VAL codes, and Riot's Vanguard error code articles for the VAN codes. Every page links the Riot article it paraphrases, and both are re-read daily.