A "VAN" code when starting League of Legends means: Riot's anti-cheat system, Vanguard, can't start up cleanly, can't connect to the Riot Client, or can't verify your system. The error message looks cryptic at first glance, but it usually comes down to one of four root causes – Vanguard isn't running, the connection to the Riot Client is disrupted, your Windows configuration isn't supported, or another program is blocking the anti-cheat.
Instead of one blanket guide for every code, below you'll find each important VAN code broken down individually, with the matching fix – use the table of contents to jump straight to your code.
RunItDown (@RunItDownDE) on X
Never miss a beat: Follow us on X for League of Legends updates – news, analysis and results straight from the newsroom.
RunItDown
Table of contents: jump straight to your error code
Startup and initialization errors
- VAN -1
- VAN -72, VAN -79, VAN -83, VAN -92
- VAN -81 and VAN 57
- VAN 0 and VAN 6
- VAN 59, VAN 140, VAN 148, VAN 193
Connection and session errors
System and hardware requirements
Special case
The basic reset sequence
Before jumping to a specific code: these steps already resolve a large share of startup and connection errors, before a reinstall is even necessary.
- Fully close League of Legends and the Riot Client, end any leftover processes in Task Manager
- Fully restart your PC (not sleep/hibernate) – the Vanguard service and driver load at Windows startup
- Let the Riot Client fully load once before starting League
- Check the "vgc" service via
services.mscand set it to "Automatic," starting it manually if needed
These four steps are assumed as the "basic reset" for every individual code below.
VAN -1: Vanguard won't install or uninstall cleanly
Riot classifies VAN -1 directly as an install/uninstall error, not a connection problem.
- Remove Vanguard via Windows Settings → Apps → Installed apps
- Restart your PC
- Open the Riot Client and start League – Vanguard reinstalls itself automatically
- If Vanguard doesn't show up in the app list at all, the installation is already corrupted – file a Riot Support ticket right away, noting the failed removal
VAN -72, VAN -79, VAN -83, VAN -92: same root-cause class
Riot describes these four negative codes in almost identical terms: Vanguard is having trouble starting up, establishing a connection, or confirming your system is ready.
- Run the basic reset
- Install pending Windows and driver updates
- Run a clean boot to rule out third-party software as a blocker
- If the error persists: fully uninstall and reinstall Vanguard
Important: with four different codes sharing the same root-cause description, it's not worth jumping to a pure internet-connection theory too quickly – a background service, security software, or a corrupted Vanguard install are just as likely.
VAN -81 and VAN 57: Vanguard doesn't start with Windows
Both codes typically show up when the anti-cheat service is disabled, a background process is stuck, or the Riot Client tries to talk to Vanguard before the service is ready.
- End all Riot, League, and Vanguard processes in Task Manager
- Restart your PC – not just the Riot Client
- Check via
services.mscwhether "vgc" is set to "Automatic," starting it manually if needed - If the service won't stay running: fully reinstall Vanguard
VAN -1 can be narrowed down with the same service check as a first step, but is more specifically tied to a failed installation than a pure startup issue.
VAN 0 and VAN 6: Vanguard can't confirm you're ready
- Restart League and the Riot Client
- If the error persists, fully restart your PC
- Reinstall Vanguard afterward if the code shows up again
VAN 59, VAN 140, VAN 148, VAN 193: unexpected startup or check-in errors
According to Riot, these four codes point to an unexpected error during startup, while communicating with the Riot Client, or during the system check.
- Restart the Riot Client and your PC
- Check the "vgc" service
- Try closing overlays, hardware tools, and security software
- Reinstall Vanguard, and only reinstall League if that alone isn't enough
VAN 140 also shows up more often on outdated or no-longer-supported Windows versions – in that case, check League's current system requirements first instead of just reinstalling.
VAN 68 and VAN 84: connection or session drops
VAN 68 happens when Vanguard loses a required connection or session, usually during game startup or mid-match. VAN 84 is classified similarly, as a connection or initialization error.
- Restart your PC, League, and the Riot Client
- Power your router off and back on if your connection has been unstable recently
- Try disabling VPN or proxy software
- Update or disable Killer Network services or similar traffic-management tools
- If the problem persists: try a different network to distinguish PC issues from router issues
If both codes hit many players at the same time, check Riot's server status first before troubleshooting your own installation.
VAN 185: session conflict between client and game
VAN 185 has historically often been tied to the Riot Client being left open continuously for a long time, or being logged in on multiple devices at once.
- Log out of the Riot Client on all other devices
- Fully close League and the Riot Client
- If the client was open for several days: restart your PC
- Log back in afterward and start only League
- If the error happens again mid-match, check your network and background software
VAN 216: usually a wrong system clock
VAN 216 is one of the newer codes and, according to Riot, is often tied to an incorrect Windows clock. Authentication and security checks work with timestamps – a wrong clock or time zone setting can make an otherwise working system look out of sync.
- Restart your PC so Vanguard reloads cleanly
- Under Settings → Time & Language → Date & Time, enable automatic time and time zone
- Click "Sync now"
- Close and reopen the Riot Client
- If the error persists: reinstall Vanguard and send the logs to Riot Support
Test the fix in practice tool or a custom lobby first – if VAN 216 interrupts you mid-queue, it can otherwise trigger a LeaverBuster penalty.
VAN 1067: local hardware or software conflicts
- Update chipset, motherboard, and graphics drivers
- Disconnect unnecessary controllers, USB storage, hubs, capture cards, and adapters
- Close RGB tools, overclocking software, hardware monitoring, and overlays
- Run a clean boot and test League with only the essential Windows services running
- Reinstall Vanguard after removing the suspected conflict
VAN -101: unsupported system configuration
Riot explicitly classifies VAN -101 not as an ordinary connection error, but as a sign of an unsupported PC or Windows configuration.
- Check League's current system requirements
- Install all available Windows updates
- Update motherboard, chipset, storage, and graphics drivers
- Remove compatibility modes on League or Riot Client programs
- Avoid modified, stripped-down, or test-signed Windows installations
- If your PC meets all requirements and the code persists: contact Riot Support
VAN 138: League is running in a virtual machine
VAN 138 means League or Vanguard is running in a virtualized or unsupported environment.
- Only run League on a regular, non-virtualized Windows installation
- Never run Vanguard inside a VM at all – this isn't a misconfiguration, it's a deliberate restriction from Riot
VAN9001: TPM 2.0 missing or disabled
- Check which TPM spec version is active via
tpm.msc - Enable TPM 2.0 in BIOS/UEFI if available
- If TPM doesn't show up, check your motherboard's BIOS support and Windows 11 requirements
VAN9002: Windows Exploit Protection disabled
- Under Windows Security → App & Browser Control → Exploit Protection Settings, restore the default settings
- Recheck your Windows security settings afterward
VAN9005: UEFI, TPM 2.0, or VBS requirement missing
- Enable UEFI mode and TPM 2.0
- Check firmware and Virtualization-Based Security (VBS) settings
- Before making firmware changes, check BIOS mode and Secure Boot status in Windows System Information
VAN9006: Windows version no longer supported
- Update Windows to a currently supported version
- Restart League afterward – a separate Vanguard fix usually isn't needed
VAN9101: Vanguard flags the system as untrustworthy
- Update drivers, disconnect unnecessary devices
- Remove conflicting third-party software, especially tools that hook into games or resemble cheat/debugging functionality
- Don't use registry edits or disabling important Windows security features as a workaround – the goal is a normal, supported system state, not bypassing the check
VAN: STATUS_VMD_9001: Intel RST driver issue
This code is more specific than the other numeric VAN codes and, according to Riot, is tied to the Intel Volume Management Device.
- Determine your exact PC, laptop, or motherboard model
- Download the current Intel RST or VMD driver from the official manufacturer support page
- Install the driver, restart your PC
- Check Windows Update for matching optional driver updates
- Don't disable VMD and don't change the storage controller mode in BIOS – an incorrect storage mode change can prevent Windows from booting
VAN 152: hardware ID ban – no self-service fix possible
VAN 152 isn't a technical glitch, it's a hardware ID ban. Reinstalling, switching devices, or altering hardware identifiers won't fix it.
- Don't repeatedly reinstall or manipulate hardware identifiers
- File a ticket with Riot Support directly if you believe the ban is unjustified
When is contacting Riot Support worth it?
A ticket makes sense if the same code keeps showing up after a basic reset, service check, clean boot, and a clean Vanguard reinstall – or right away for VAN 152. Helpful info for the ticket: the exact code including any minus sign or suffix like "STATUS_VMD_9001," when it occurs (login, champion select, mid-match), your Windows version, whether the "vgc" service starts, steps you've already tried, and any recent Windows, driver, or hardware changes.