VALORANT isn’t without its flaws.
There are dozens of unfortunate error codes that can (and will) crop up at any given time. From an invalid display name to the Vanguard anti-cheat not being initialized, here’s the full rundown of error codes in VALORANT, what they mean, and how to fix them.
All VALORANT error codes
Standard VALORANT error codes
Code number | Meaning | Solution |
0 | Connection error | Go ahead and restart VALORANT and the Riot client. |
1 | Connection error | Go ahead and restart VALORANT and the Riot client. |
4 | Your display name is invalid | Something’s up with your Riot ID. You can change it here. |
5 | Account was logged into elsewhere | You should log out from all devices. |
7 | Couldn’t connect to session service | You might have a suspension on your account. Check your email for more information. It could also be a platform issue. Make sure to check the VALORANT Discord or Support site banner for more information. |
8-21 | Problems with the Riot client | Go ahead and restart the Riot client. |
29 | This is a network issue | Make sure your firewall allows VALORANT through. Further details can be found here. |
31 | Failed to get player name information | Go ahead and restart the Riot client. |
33 | The Riot client process was closed. | Go ahead and restart the Riot client. |
38 | Connection error | Go ahead and restart VALORANT and the Riot client. |
43 | A system has timed out | Go ahead and restart the Riot client. |
44 | Vanguard not initialized | Go ahead and restart the Riot client. If the problem persists, uninstall Riot Vanguard and estart VALORANT |
45 | Vanguard reboot required | Go ahead and restart the Riot client. If the problem persists, uninstall Riot Vanguard and restart VALORANT |
46 | Platform downtime | This is planned downtime allotted for the engineers to work on Riot’s systems. Check back with the game later. |
49 | Chat did not initialize | There seems to be an issue with the chat. Go ahead and restart the Riot client. |
50 | Voice did not initialize | There seems to be an issue with the chat. Go ahead and restart the Riot client. |
51 | Problem creating a party | There seems to be an issue with the Party System. Go ahead and restart the Riot client. |
52 | Problem fetching skill information for players | Go ahead and restart the Riot client. |
53 | Problem with Riot client chat. | There seems to be a problem with the Riot client chat. Go ahead and restart the Riot client. |
54 | Content service failure. | VALORANT was unable to retrieve your content. Go ahead and restart the Riot client. |
55 | ApplicationRepairManagerInitFailure | Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. If there are no issues with the client, submit a ticket to Riot. |
56 | LegalInfoInitFailure | Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. If there are no issues with the client, submit a ticket to Riot. |
57 | PlayerAffinityInitFailure | Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. If there are no issues with the client, submit a ticket to Riot. |
58 | RSOValidationFailure | Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. If there are no issues with the client, submit a ticket to Riot. |
59 | LoginQueueFetchTokenFailure | There seems to be an issue with the login queue. Go ahead and restart the Riot client and check for any Support Site banners. |
60 | PatchInitFailure | Something went wrong during the startup process. Go ahead and restart the Riot client.. |
61 | You have been banned from playing VALORANT | Submit a ticket to Riot. |
62 | NoGamepodsToPingFailure | Something seems to be amiss with your network. Go ahead and restart the Riot client. If the problem persists, submit a ticket to Riot. |
63 | ManagerDeleted | Something went wrong during the startup process. Go ahead and restart the Riot client. |
64 | SessionFetchFailure | Something went wrong during the startup process. Go ahead and restart the Riot client. |
65 | PatchAvailabilityInitFailure | Something went wrong during the startup process. Go ahead and restart the Riot client. |
66 | ContentIndexInitFailure | Something went wrong during the startup process. Go ahead and restart the Riot client. |
67 | ChatFriendMetadataInitFailure | Go ahead and restart VALORANT and the Riot client. If the problem persists, submit a ticket to Riot. |
68 | CapEntitlementsFetchError | VALORANT can’t seem to fetch your owned content. Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. |
69 | CapWalletsFetchError | VALORANT can’t seem to fetch your owned content. Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. |
70 | StoreOffersFetchError | VALORANT can’t seem to fetch your owned content. Go ahead and restart the Riot client. If the problem persists, check the Support Site banners. |
-81 | Service start failed | Go ahead and restart your PC and the Riotclient. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, submit a ticket to Riot. |
128 | VALORANT has encountered a connection error. Relaunch client to reconnect | Go ahead and restart your PC and the Riotclient. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, submit a ticket to Riot. |
138 | VALORANT has encountered a connection error. Relaunch client to reconnect | Looks like you’re running VALORANT or Riot Vanguard from a virtual machine. Since this isn’t allowed, you’ll have to install both on a regular instance of Windows instead of a virtual one. |
152 | HWID ban | This is a hardware ban which typically lasts four months. |
VAN VALORANT error codes
Code number | Meaning | Solution |
VAN -1 | Uninstall feature | Reinstall Riot Vanguard. If the problem persists, please submit a ticket. |
VAN 0 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Go ahead and restart VALORANT and the Riot client. |
VAN 1 | VALORANT has encountered connection error. Please relaunch client to reconnect, | Go ahead and restart VALORANT and the Riot client. |
VAN 6 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Go ahead and restart VALORANT and the Riot client. |
VAN -81 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Go ahead and restart your PC and the Riot Client. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, please submit a ticket. |
VAN -102 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Go ahead and restart your PC and the Riot Client. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, please submit a ticket. |
VAN -104 | Connection error. | Go ahead and restart your PC and the Riot Client. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, please submit a ticket. |
VAN 128 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Go ahead and restart your PC and the Riot Client. If the problem persists, uninstall Riot Vanguard and VALORANT, then do a fresh reinstallation of both. If the problem persists, please submit a ticket. |
VAN 138 | VALORANT has encountered connection error. Please relaunch client to reconnect. | Looks like you’re running VALORANT/Riot Vanguard from a virtual machine. Since this isn’t allowed, you’ll have to install both on a regular instance of Windows instead of a virtual one. |
VAN 152 | HWID Ban. | This is a hardware ban which typically lasts 4 months. Please submit a ticket at the bottom of this page if you have further questions. |
VAN9001 | Secure Boot or TPM (Trusted Platform Module) 2.0 is not enabled. | Please see this article on how to check whether your Windows 11 system supports Secure Boot and TPM 2.0, and how to troubleshoot. |
VAN9002 | This build of Vanguard requires Control Flow Guard (CFG) to be enabled in system exploit protection settings. | Please see this article on how to change exploit protection settings. If the problem persists, please submit a ticket. |
VAN9003 | Secure Boot is not enabled. | Please see this article on how to check whether your Windows 11 system supports Secure Boot, and how to troubleshoot. |
VAN9005 | This version of Vanguard requires TPM version 2.0 and UEFI compliant firmware in order to use Virtualization-based Security (VBS). | Please see this article to change your BIOS Mode to UEFI and enable TPM 2.0. |
VAN9006 | You are currently running an older version of Windows that will no longer be supported by Vanguard. | Please update to Windows 10 20H1 (Version 2004) or later to continue playing VALORANT. |