ERROR CODES
VALORANT errors (VAN and VAL) and how to fix them Type your error code in the box below to jump straight to it. VAN errors come from Vanguard (Riot's anti-cheat), and VAL errors come from the game itself and its servers.
Last checked: November 19, 2026
TPM, Secure Boot and Windows security errors Vanguard launch and connection errors VAL errors (the game itself and its servers) Type the error code, e.g. 9003
Tip: Before anything else, do one full system restart (Restart, not Shut down). Many Vanguard errors are fixed by this alone, because Vanguard starts when Windows boots.TPM, Secure Boot and Windows security errors These mean Vanguard sees one of your system's security features as turned off. The fix is usually a setting in the BIOS or Windows, and reinstalling the game won't fix it.
VAN 9001 Vanguard needs TPM 2.0 but doesn't see it enabled on your system. In game the message reads: This build of Vanguard requires TPM 2.0[1] [2]
What to do
Press Win + R and type tpm.msc to see whether Windows detects the TPM. You should see The TPM is ready for use and Specification Version 2.0. If no TPM is found, go into the BIOS and enable it. On Intel systems it's usually called Intel PTT , and on AMD it's AMD fTPM . Save the changes with F10, boot the system and open the game again. Step by step: TPM 2.0 and Secure Boot for Vanguard, step by step
VAN 9003 Secure Boot isn't enabled on your system. The game's message: This build of Vanguard requires secure boot to be enabled in order to play.[3] [4]
What to do
Use msinfo32 to check what BIOS Mode is set to and whether Secure Boot State is on. If BIOS Mode is Legacy, the Windows disk first has to be converted from MBR to GPT. Only do this step with a backup. In the BIOS, set Boot Mode to UEFI, turn off CSM and enable Secure Boot. Step by step: TPM 2.0 and Secure Boot for Vanguard, step by step
VAN RESTRICTION 1 Vanguard couldn't confirm that Secure Boot is enabled and working properly on your system.[5]
What to do
Enable Secure Boot, restart the system and open the game. If Secure Boot is on and the same error still appears, update your motherboard BIOS. Step by step: TPM 2.0 and Secure Boot for Vanguard, step by step
VAN RESTRICTION 3 The game is installed on a drive that doesn't have Windows on it.[6]
What to do
Uninstall VALORANT and reinstall it on the same drive Windows is on (usually drive C). VAN RESTRICTION 4 Vanguard couldn't verify your system's Secure Boot settings.[7]
What to do
Enable Secure Boot, restart the system and try again. Step by step: TPM 2.0 and Secure Boot for Vanguard, step by step
VAN RESTRICTION 5 Vanguard couldn't see that Memory Integrity (also called HVCI or VBS) is on and working properly.[8] [9]
What to do
Turn on Memory Integrity from Windows Security (the steps are on the TPM and Secure Boot page). Restart the system and open the game. Sometimes this also requires turning on Virtualization in the BIOS. Step by step: TPM 2.0 and Secure Boot for Vanguard, step by step
Vanguard launch and connection errors This group usually means the Vanguard service didn't start properly or its connection dropped mid-session. The order of the steps matters: start from the first one and test the game after each step.
VAN 0 / 84 / 135 Vanguard couldn't confirm that your system is ready to run the game.[10] [11] [12]
What to do
Fully update Windows. Set the vgc service to Automatic: Win + R, type services.msc, double-click vgc, set Startup type to Automatic and click Start. Uninstall and reinstall Vanguard (Riot Vanguard in the Apps section of Windows). Do a Clean Boot to rule out another program conflicting with Vanguard: msconfig > Services > tick Hide all Microsoft services > Disable all, then restart. When you're done, Enable them all again. If that doesn't fix it, fully uninstall the game and install it again. VAN 68 Vanguard lost its connection to the server.[13]
What to do
Restart the system. Check that the Windows date, time and Time zone are correct. Set the vgc service to Automatic, and if that doesn't fix it, reinstall Vanguard. Do a clean boot, and if you have a Killer network card, turn off the Killer Network Service. VAN -81 Vanguard ran into a problem while starting up.[14]
What to do
Restart the system and check the Windows date and time. Set the vgc service to Automatic, and if that doesn't fix it, reinstall Vanguard. Do a clean boot and, as a last step, reinstall the game. VAN 57 Vanguard isn't running.[15]
What to do
Set the vgc service to Automatic and restart the system. Uninstall and reinstall Vanguard. Do a clean boot, and if it still isn't fixed, reinstall the game. VAN 1067 Vanguard ran into an unexpected problem.[16]
What to do
Update Windows and unplug any controllers or extra USB devices from the system. Open Riot Client with Run as administrator. Set the vgc service to Automatic and do a clean boot. Scan the system with an antivirus, then reinstall Vanguard and, if needed, the game itself. VAN 152 Hardware ban (HWID ban). It means your system is banned from the game, and reinstalling won't fix it.[17] [18]
What to do
Reinstalling the game or Vanguard won't help. If you think it's a mistake, the only way to follow it up is a Riot support ticket. VAL errors (the game itself and its servers) Riot itself says this list of codes may not be complete or up to date. Many of these are server-side, and all you can do is wait.[18]
VAL 29 A network problem, usually a firewall blocking the game.[18]
What to do
Allow VALORANT and Riot Client through Windows Firewall (or your antivirus firewall). VAL 39 The server isn't available.[18]
What to do
The problem is on Riot's side. Wait a few minutes and try again. VAL 43 The connection to Riot's systems timed out.[18]
What to do
Close Riot Client and open it again. If it keeps happening, restart the system and check your internet connection. VAL 44 Vanguard didn't start.[18]
What to do
Reopen Riot Client. If that doesn't fix it, uninstall Vanguard and reinstall it by opening the game. VAL 45 Vanguard needs a system restart to work.[18]
What to do
Restart the system. If the error comes back, uninstall and reinstall Vanguard. VAL 46 The servers are down for maintenance.[18]
What to do
Wait until the maintenance is over. VAL 59 The login queue is full.[18]
What to do
Try logging in again in a few minutes. VAL 61 Your account is banned.[18]
What to do
You can only follow this up through Riot support. VAL 62 The game couldn't ping any of the servers (NoGamepodsToPing).[18]
What to do
Close Riot Client and open it again, and check your internet and firewall. VAL 138 The game was launched in a Virtual Machine.[18]
What to do
VALORANT doesn't run in a virtual machine. Install it on your main Windows system. Tip: If none of these work, Riot says to collect logs with the Riot Repair Tool and send them to support in a ticket. The link to each error's official page is at the bottom of this page.Sources Riot Support: VAN 9001 Official Riot Seen November 19, 2026 Riot Support: TPM 2.0 guide Official Riot Seen November 19, 2026 Riot Support: VAN 9003 Official Riot Seen November 19, 2026 Riot Support: Secure Boot guide Official Riot Seen November 19, 2026 Riot Support: VAN RESTRICTION 1 Official Riot Seen November 19, 2026 Riot Support: VAN RESTRICTION 3 Official Riot Seen November 19, 2026 Riot Support: VAN RESTRICTION 4 Official Riot Seen November 19, 2026 Riot Support: VAN RESTRICTION 5 Official Riot Seen November 19, 2026 Riot Support: Enabling Memory Integrity Official Riot Seen November 19, 2026 Riot Support: VAN 0 Official Riot Seen November 19, 2026 Riot Support: VAN 84 Official Riot Seen November 19, 2026 Riot Support: VAN 135 Official Riot Seen November 19, 2026 Riot Support: VAN 68 Official Riot Seen November 19, 2026 Riot Support: VAN -81 Official Riot Seen November 19, 2026 Riot Support: VAN 57 Official Riot Seen November 19, 2026 Riot Support: VAN 1067 Official Riot Seen November 19, 2026 Riot Support: VAN 152 Official Riot Seen November 19, 2026 Riot Support: Error codes and solutions in VALORANT Official Riot Seen November 19, 2026 Next TPM 2.0 and Secure Boot for Vanguard, step by stepAll help pages