How to Fix League of Legends Vanguard Errors (VAN Codes)

Updated Published

On this page

A League of Legends Vanguard error — a VAN code that blocks the client from launching, or a “Vanguard session is initializing” message that never clears — comes from the same kernel-level anti-cheat that protects Valorant, and it’s fixed the same handful of ways: enable Secure Boot and TPM 2.0, restart the Vanguard service, or clear a driver conflict. This guide covers the fixes and codes specific to League.

How to Fix League of Legends Vanguard Errors

Riot brought Vanguard to League of Legends in 2024 — it’s the same anti-cheat install that also protects Valorant, sharing the same vgc/vgk services and BIOS requirements. If you also play Valorant and want the full command reference and every VAN code Riot uses across both games, see How to Fix Valorant VAN Errors and Vanguard Won’t Start.

Step 1 – Restart Vanguard the easy way

Most one-off League Vanguard errors clear with a clean restart, because Vanguard has to load at boot, before the OS finishes starting up.

  1. Fully close League of Legends and the Riot Client.
  2. In the system tray, right-click the Vanguard (Riot) icon and choose Exit / Quit.
  3. Reboot your PC — don’t just relaunch the client, Vanguard needs to reload during startup.
  4. Launch the Riot Client and start League again.

Step 2 – Enable Secure Boot and TPM 2.0

League’s Vanguard install enforces the exact same Windows 11 security requirements as Valorant: TPM 2.0 and Secure Boot both have to be on, or the client won’t get past the anti-cheat check.

  1. Press Win + R, type msinfo32, press Enter.
  2. Confirm Secure Boot State: On and BIOS Mode: UEFI.
  3. Press Win + R, type tpm.msc, press Enter — it should read TPM 2.0, ready for use.

If either is missing, enable it in BIOS using your board’s guide:

Step 3 – Fix VAN57 by restarting the Vanguard service

VAN57 is the most common League Vanguard error, and it means the vgc service isn’t running.

  1. Press Win + R, type services.msc, press Enter.
  2. Find vgc in the list.
  3. Right-click → Properties → set Startup type to Automatic.
  4. Click Start, then OK, and reboot.

Step 4 – Reset the vgk driver from Command Prompt

If VAN57, VAN84, or a “waiting for Vanguard to start” message persists after a service restart, reset the kernel driver directly.

  1. Open Command Prompt as administrator (here’s how).
  2. Run these one at a time: 
    sc stop vgc
sc stop vgk
sc start vgk
sc start vgc
  3. Launch League again.

Step 5 – Clear VAN128 driver conflicts

VAN128 means Vanguard’s kernel driver is conflicting with another program, or a required security feature isn’t enabled.

  1. Re-confirm Secure Boot and TPM 2.0 are both on (Step 2) — this is the most common trigger.
  2. Temporarily disable third-party antivirus software. Third-party AV suites frequently flag Vanguard’s own driver files, which is exactly backwards but common.
  3. Close overlay and peripheral software (RGB utilities, capture tools) while testing, then reboot and relaunch.

Step 6 – Reinstall Vanguard cleanly

For anything that survives Steps 1–5, a clean reinstall clears most remaining issues.

  1. Open Settings → Apps → Installed apps.
  2. Uninstall Riot Vanguard.
  3. Reboot.
  4. Launch the Riot Client — it reinstalls Vanguard automatically and prompts for a restart. Allow it.

”Vanguard session is initializing” won’t go away

The “Vanguard session is initializing” message means the League client is waiting for Vanguard to finish loading and hasn’t confirmed it yet. Vanguard’s kernel driver loads when Windows boots, so a client restart alone rarely clears it.

  1. Close League and the Riot Client completely (end RiotClientServices and LeagueClient in Task Manager if they linger).
  2. Restart the PC — a full restart, not a client relaunch.
  3. If it returns, set the vgc service to Automatic (Step 3) and restart again.
  4. Still stuck after a Windows update or a client crash: reinstall Vanguard (Step 6).

League Vanguard error codes: meaning and fix

Meanings below follow Riot’s own support articles for each code. Work the fixes in the order given and test in Practice Tool after each one.

CodeWhat Riot says it meansFix, in order
VAN -1Vanguard couldn’t start correctly, or a required service is unavailableReinstall Vanguard (Step 6), then set vgc to Automatic (Step 3)
VAN -81 / VAN -83Vanguard is having trouble starting, staying connected, or confirming it’s ready while the game launches or runsRestart PC → check Windows time, date and time zone → vgc Automatic → reinstall Vanguard → clean boot → reinstall League
VAN 57The Vanguard service (vgc) isn’t running — the most common League codeStep 3, then reboot
VAN 59Vanguard hit an unexpected issue starting or talking to the Riot ClientRestart the Riot Client → reinstall Vanguard → reinstall League
VAN 84Vanguard couldn’t verify your PC is ready, or failed while initializingUpdate Windows → vgc Automatic → reinstall Vanguard → clean boot
VAN 128Driver conflict or a missing security featureStep 5 (Secure Boot, TPM 2.0, antivirus)
VAN 138Virtual machine detectedRun League on a native Windows install, not a VM
VAN 152Hardware ID banNot fixable client-side — contact Riot Support
VAN 1067Vanguard hit an unexpected issue starting or checking in with your systemUpdate Windows → unplug controllers and spare USB devices → run the Riot Client as administrator → vgc Automatic
VAN -101Unsupported system configurationUpdate Windows and drivers, then retry

Codes not on Riot’s list. Searches also turn up VAN 48, VAN 216 and VAN 289, which Riot’s League error-code index doesn’t document. Don’t trust a single forum explanation for these — work the generic order (restart PC → vgc Automatic → reinstall Vanguard → clean boot), and if the code survives that, open a ticket with Riot Player Support and attach your logs.

Check the Windows clock. Riot lists wrong time, date or time zone as a cause for the connection-type codes (VAN -81, VAN -83). Open Settings → Time & language → Date & time, turn on Set time automatically, and click Sync now.

Because League and Valorant share one Vanguard install, fixing an error in either game usually fixes it for both. Work through the steps in order and the large majority of League Vanguard failures clear without a support ticket.

Frequently asked questions

Why does League of Legends need Vanguard now?

Riot rolled its kernel-level Vanguard anti-cheat out to League of Legends in 2024, the same system that already protected Valorant. It's one shared install — Vanguard runs at the OS level below the game itself, so it applies the same Secure Boot, TPM 2.0, and driver requirements to League that it always enforced in Valorant.

What's the most common League Vanguard error?

VAN57, which points to a Vanguard service problem — usually the vgc service isn't running or didn't start with Windows. It's almost always fixed by setting the vgc service to Automatic startup and rebooting (Step 3 below).

Do I need to reinstall Vanguard separately for League and Valorant?

No. If you already have Valorant installed, Vanguard is already on your system and League uses the same install — you won't be prompted to install it twice. If you only play League, the Riot Client installs Vanguard automatically the first time you launch the game.

What does VAN128 mean in League of Legends?

VAN128 means Vanguard's kernel driver is either conflicting with another program on your PC or Windows is missing a required security feature. Confirm Secure Boot and TPM 2.0 are both enabled (Step 2), then temporarily disable third-party antivirus software, which is a common cause of false-positive flags.

What do VAN -81 and VAN -83 mean in League of Legends?

Riot describes VAN -81 and VAN -83 the same way: Vanguard is having trouble starting, staying connected, or confirming it is ready while League launches or runs. Riot's fix order is restart your PC, check that Windows time, date and time zone are correct, set the vgc service to Automatic, then reinstall Vanguard, clean boot, and reinstall the game if it persists.

How do I fix 'Vanguard session is initializing' in League?

The message means the League client is still waiting for Vanguard to finish loading. Vanguard only fully loads when Windows boots, so close the Riot Client, restart the PC (not just the client), and make sure the vgc service is set to Automatic in services.msc. If it keeps returning, reinstall Vanguard and reboot.

Is VAN152 fixable on my end?

No. VAN152 is a hardware ID ban, not a settings or driver problem — no client-side fix will clear it. If you believe it was issued in error, the only path is a support ticket through Riot's official channels.