Complete reference
All Valorant Error Codes
50 error codes — find the code you're seeing and jump straight to the fix. Each entry links to a full step-by-step guide.
4 server-side·21 client-side·18 mixed
| Code | Meaning | Cause | Fix |
|---|---|---|---|
CLIENT-UPDATE | Your Valorant client is out of date. The game servers require the latest version before you can queue for a match. | Fix guide → | |
CONNECTION-TIMEOUT | Valorant could not establish a stable connection to game servers before timeout. | Server or client | Fix guide → |
FPS-DROP | Valorant runs at lower FPS than expected — stutter during fights or menus. | Client-side | Fix guide → |
HIGH-PING | Valorant shows high ping or rubber-banding in-game. | Server or client | Fix guide → |
PACKET-LOSS | Valorant reports packet loss — shots register late or players teleport. | Client-side | Fix guide → |
RECONNECT-FAILED | Valorant attempted to reconnect you to an ongoing match but failed. The match may have ended or the server rejected the reconnection. | Server or client | Fix guide → |
STUTTERING | Valorant micro-stutters every few seconds despite decent FPS. | Client-side | Fix guide → |
VAN-0 | Valorant lost connection to Riot services mid-session or at login. | Server or client | Fix guide → |
VAN-1 | Vanguard, Valorant's anti-cheat system, is not running or failed to initialize, so your client is not authorized to launch a match. | Fix guide → | |
VAN-106 | Valorant timed out while connecting to Riot servers or completing the login handshake. | Server or client | Fix guide → |
VAN-11 | The Valorant client could not communicate with the Riot Games backend services needed to start the game. This includes authentication servers or matchmaking services. | Server-side | Fix guide → |
VAN-124 | Vanguard's file integrity check found that one or more Valorant game files have been modified or corrupted. Vanguard blocks the game from launching when it detects file tampering. | Client-side | Fix guide → |
VAN-128 | Valorant lost connection to game server mid-match. | Server or client | Fix guide → |
VAN-135 | Your account or device does not meet Valorant's regional or platform requirements for the current server. | Server or client | Fix guide → |
VAN-138 | Valorant could not maintain a stable connection to Riot servers. | Server or client | Fix guide → |
VAN-152 | Vanguard detected a security or driver conflict preventing Valorant from starting. | Client-side | Fix guide → |
VAN-19 | Valorant lost connection to Riot game servers during queue or match. | Server or client | Fix guide → |
VAN-21 | Valorant could not authorize your session. You may have launched Valorant directly instead of through the Riot Client, or Vanguard is not active. | Fix guide → | |
VAN-29 | Valorant VAN 29 relates to Riot Vanguard anti-cheat failing to initialize. | Client-side | Fix guide → |
VAN-31 | Your system's graphics hardware or driver does not meet Valorant's DirectX 11 requirement. Valorant requires DirectX 11 or later to run. | Client-side | Fix guide → |
VAN-33 | The Riot Vanguard anti-cheat service failed to start or initialize. Without Vanguard running, Valorant cannot launch. | Client-side | Fix guide → |
VAN-37 | Windows' Memory Integrity (Core Isolation) setting is conflicting with Riot Vanguard. Either Memory Integrity is on and blocking Vanguard, or a driver incompatible with Memory Integrity is also causing Vanguard issues. | Client-side | Fix guide → |
VAN-39 | Vanguard's kernel driver is not loaded, is outdated, or requires a system restart to activate after an update. | Fix guide → | |
VAN-43 | Valorant detected incorrect system time. | Client-side | Fix guide → |
VAN-45 | Vanguard's anti-cheat process failed to start or was terminated. Valorant cannot run without an active Vanguard session. | Fix guide → | |
VAN-46 | Vanguard denied your account authorization to enter a match, often due to a hardware ID flag, account restriction, or anti-cheat detection. | Server or client | Fix guide → |
VAN-51 | Riot Vanguard detected a conflicting application or driver that interferes with its kernel-level anti-cheat protection. Vanguard blocked Valorant's launch as a result. | Client-side | Fix guide → |
VAN-52 | Your Windows installation is missing critical updates required for Riot Vanguard to function. Vanguard blocks the game when it detects that essential OS components or security updates are absent. | Client-side | Fix guide → |
VAN-55 | Riot Vanguard detected a BIOS or UEFI configuration that is incompatible with its security requirements. This is often related to outdated firmware or certain BIOS settings that Vanguard treats as insecure. | Client-side | Fix guide → |
VAN-57 | Vanguard detected a conflict or failed its security check. | Client-side | Fix guide → |
VAN-6 | Valorant VAN 6 indicates a connection failure between client and Riot servers. | Server or client | Fix guide → |
VAN-61 | Valorant's Vanguard anti-cheat requires Secure Boot to be enabled in your BIOS/UEFI. Your system has Secure Boot disabled, preventing Vanguard from loading. | Client-side | Fix guide → |
VAN-63 | Valorant's voice chat system could not access your microphone. Windows or your privacy settings are blocking microphone access for the application. | Client-side | Fix guide → |
VAN-67 | Vanguard requires Secure Boot to be enabled in your system BIOS/UEFI. Your current configuration has Secure Boot disabled. | Fix guide → | |
VAN-68 | Vanguard requires TPM 2.0 (Trusted Platform Module) to be enabled. Your system either lacks TPM 2.0 or it is disabled in BIOS. | Fix guide → | |
VAN-7 | The Riot Client could not maintain a stable connection to Riot servers. | Server or client | Fix guide → |
VAN-73 | Your Windows version is not compatible with Riot Vanguard. Valorant requires Windows 10 version 1903 (May 2019 Update) or later. | Client-side | Fix guide → |
VAN-75 | Riot Vanguard's installation files are corrupted or incomplete. Vanguard cannot start in a damaged state and blocks Valorant from launching. | Client-side | Fix guide → |
VAN-81 | Valorant lost connection to Riot services during login or queue. | Server or client | Fix guide → |
VAN-84 | Vanguard blocked an incompatible driver. | Client-side | Fix guide → |
VAN-85 | Vanguard requires Secure Boot on some systems. | Client-side | Fix guide → |
VAN-87 | Riot Vanguard cannot find a Trusted Platform Module (TPM) 2.0 chip on your system, or TPM 2.0 is present but disabled in BIOS. Vanguard requires TPM 2.0 as a hardware security requirement. | Client-side | Fix guide → |
VAN-9001 | Valorant failed during startup while contacting Riot authentication or configuration services. | Server or client | Fix guide → |
VAN-9002 | Valorant failed to connect to Riot configuration services. | Server or client | Fix guide → |
VAN-9003 | Valorant could not connect to Riot services or complete Vanguard checks. | Server or client | Fix guide → |
VAN-9005 | Valorant network validation failed. | Server or client | Fix guide → |
VAN-9006 | Valorant could not authenticate your Riot account during the game launch process. This is distinct from the login screen — van-9006 occurs after login when the game client tries to verify your session. | Server-side | Fix guide → |
VAN-9008 | Valorant's Riot Client could not refresh your authentication token. The token may have expired, or the token refresh service is temporarily unavailable. | Server-side | Fix guide → |
VAN-9998 | Valorant could not connect to game servers — VAN 9998. | Server or client | Fix guide → |
VAN-9999 | Valorant is in maintenance or Riot authentication is unavailable. | Server-side | Fix guide → |
Mixed (Server or Client) — 18 codes
CONNECTION-TIMEOUTValorant could not establish a stable connection to game servers before timeout.HIGH-PINGValorant shows high ping or rubber-banding in-game.RECONNECT-FAILEDValorant attempted to reconnect you to an ongoing match but failed. The match may have ended or the server rejected the reconnection.VAN-0Valorant lost connection to Riot services mid-session or at login.VAN-106Valorant timed out while connecting to Riot servers or completing the login handshake.VAN-128Valorant lost connection to game server mid-match.VAN-135Your account or device does not meet Valorant's regional or platform requirements for the current server.VAN-138Valorant could not maintain a stable connection to Riot servers.VAN-19Valorant lost connection to Riot game servers during queue or match.VAN-46Vanguard denied your account authorization to enter a match, often due to a hardware ID flag, account restriction, or anti-cheat detection.VAN-6Valorant VAN 6 indicates a connection failure between client and Riot servers.VAN-7The Riot Client could not maintain a stable connection to Riot servers.VAN-81Valorant lost connection to Riot services during login or queue.VAN-9001Valorant failed during startup while contacting Riot authentication or configuration services.VAN-9002Valorant failed to connect to Riot configuration services.VAN-9003Valorant could not connect to Riot services or complete Vanguard checks.VAN-9005Valorant network validation failed.VAN-9998Valorant could not connect to game servers — VAN 9998.Server-side — 4 codes
VAN-11The Valorant client could not communicate with the Riot Games backend services needed to start the game. This includes authentication servers or matchmaking services.VAN-9006Valorant could not authenticate your Riot account during the game launch process. This is distinct from the login screen — van-9006 occurs after login when the game client tries to verify your session.VAN-9008Valorant's Riot Client could not refresh your authentication token. The token may have expired, or the token refresh service is temporarily unavailable.VAN-9999Valorant is in maintenance or Riot authentication is unavailable.Client-side — 21 codes
FPS-DROPValorant runs at lower FPS than expected — stutter during fights or menus.PACKET-LOSSValorant reports packet loss — shots register late or players teleport.STUTTERINGValorant micro-stutters every few seconds despite decent FPS.VAN-124Vanguard's file integrity check found that one or more Valorant game files have been modified or corrupted. Vanguard blocks the game from launching when it detects file tampering.VAN-152Vanguard detected a security or driver conflict preventing Valorant from starting.VAN-29Valorant VAN 29 relates to Riot Vanguard anti-cheat failing to initialize.VAN-31Your system's graphics hardware or driver does not meet Valorant's DirectX 11 requirement. Valorant requires DirectX 11 or later to run.VAN-33The Riot Vanguard anti-cheat service failed to start or initialize. Without Vanguard running, Valorant cannot launch.VAN-37Windows' Memory Integrity (Core Isolation) setting is conflicting with Riot Vanguard. Either Memory Integrity is on and blocking Vanguard, or a driver incompatible with Memory Integrity is also causing Vanguard issues.VAN-43Valorant detected incorrect system time.VAN-51Riot Vanguard detected a conflicting application or driver that interferes with its kernel-level anti-cheat protection. Vanguard blocked Valorant's launch as a result.VAN-52Your Windows installation is missing critical updates required for Riot Vanguard to function. Vanguard blocks the game when it detects that essential OS components or security updates are absent.VAN-55Riot Vanguard detected a BIOS or UEFI configuration that is incompatible with its security requirements. This is often related to outdated firmware or certain BIOS settings that Vanguard treats as insecure.VAN-57Vanguard detected a conflict or failed its security check.VAN-61Valorant's Vanguard anti-cheat requires Secure Boot to be enabled in your BIOS/UEFI. Your system has Secure Boot disabled, preventing Vanguard from loading.VAN-63Valorant's voice chat system could not access your microphone. Windows or your privacy settings are blocking microphone access for the application.VAN-73Your Windows version is not compatible with Riot Vanguard. Valorant requires Windows 10 version 1903 (May 2019 Update) or later.VAN-75Riot Vanguard's installation files are corrupted or incomplete. Vanguard cannot start in a damaged state and blocks Valorant from launching.VAN-84Vanguard blocked an incompatible driver.VAN-85Vanguard requires Secure Boot on some systems.VAN-87Riot Vanguard cannot find a Trusted Platform Module (TPM) 2.0 chip on your system, or TPM 2.0 is present but disabled in BIOS. Vanguard requires TPM 2.0 as a hardware security requirement.