VAN 133 in VALORANT: Vanguard's PC check didn't pass

Connection Error: VALORANT has encountered a connection error. Please relaunch the client to reconnect. Error Code: VAN 133

133 and 135 look alike for a reason

VAN 133 and VAN 135 sit two numbers apart and Riot explains them identically. Both are readiness failures, where Vanguard couldn't verify the PC or broke while starting, and both get the same six steps as VAN 0, 6 and 84.

That matters if you're searching for a fix that's specific to 133. Riot hasn't published one. The best guide is the shared list, starting with Windows Update and working down.

If you're on Pre-Check

Step two sets the vgc service to Automatic. Riot carves out one exception: players using Vanguard Pre-Check, where Vanguard only starts with the game. If that's you, leave the service as it is and move on to the reinstall.

Riot's fix, in Riot's order

1. Install every pending Windows update

   Open Settings, then Windows Update, and keep installing and restarting until it says you're up to date. Vanguard's checks lean on security components that ship in those updates, and optional driver updates are worth a look while you're there.

2. Set the vgc service to Automatic

   Vanguard has two parts: a driver that loads at boot and a Windows service called vgc. If the service isn't running when you press Play, the game closes.

   1. Press Win+R, type services.msc and press Enter.
   2. Find vgc in the list and double-click it.
   3. Set Startup type to Automatic. If the status says Stopped, click Start.
   4. Apply, OK, then restart the PC.

   The exception is Vanguard Pre-Check, Riot's opt-in mode where Vanguard only runs while a game is open. It needs Windows 11 25H2 or newer plus Secure Boot, TPM 2.0, IOMMU, VBS and HVCI, and if you're on it you shouldn't force the service to Automatic.

   Riot's guide: Set the vgc service to Automatic

3. Uninstall Vanguard, restart, and let the game reinstall it

   1. Close the game and exit the Riot Client from the system tray.
   2. Right-click the red Vanguard icon in the tray, choose Advanced, then Uninstall Vanguard. If the icon isn't there, search Windows for Add or remove programs and uninstall Riot Vanguard from the list.
   3. Restart the PC. Vanguard is gone if its tray icon doesn't come back.
   4. Open the Riot Client and launch the game. It reinstalls Vanguard and will ask for one more restart before Play unlocks.

   Riot's guide: Uninstall Vanguard, restart, and let the game reinstall it

4. Do a clean boot

   This switches off every non-Microsoft service for one boot, so you can tell whether something in the background is the problem.

   1. Press Win+R, type msconfig and press Enter.
   2. On the Services tab, tick Hide all Microsoft services first (skip it and you'll switch off parts of Windows).
   3. Click Disable all, then tick vgc again so Vanguard still starts.
   4. Apply, OK, restart, and test.

   Some programs ignore a clean boot anyway, third-party antivirus and networking tools most of all. If the error goes away, turn services back on a few at a time until it returns, and you've found it.

   Riot's guide: Do a clean boot

5. Reinstall the game

   Close the Riot Client first, then uninstall VALORANT from Windows' Installed apps list. For a clean reinstall, Riot's guide has you remove the VALORANT and Riot Client folders inside C:\Riot Games, empty the Recycle Bin, then delete the Riot Games and VALORANT folders under %localappdata%. Restart, then download the installer again from Riot's site.

   Riot's guide: Reinstall the game

6. Work through Riot's connection checklist

   Last on Riot's list for a reason: only get here once the Vanguard steps above have failed. Riot's PC connection guide covers the usual suspects: a wired connection instead of Wi-Fi, restarting the router, switching to a public DNS, firewall exceptions for the Riot Client and game, and turning off VPNs.

   Riot's guide: Work through Riot's connection checklist

Related VALORANT errors

• VAN 135
• VAN 0
• VAN 6
• VAN 84

Source: Riot Games Player Support, Error VAN 133, updated July 14, 2026. Riot's steps are paraphrased here, not copied; checked October 8, 2026.