LoL Error Codes, Explained

A patch didn't go through, so the client won't let you log in. Riot files it as a storage problem, with antivirus as the second suspect.

A League update started and didn't finish. Riot ties it to the Riot Client lacking permissions, free disk space or network access while it patches.

Windows is stopping the League client from opening, so you never reach the login. Riot says the exact cause isn't known.

Riot's servers are overloaded. Nothing on your PC caused it.

Your connection to the match got badly disrupted, and League is scrambling to fetch the game data you missed. It's a network problem, on your side or Riot's.

Riot blames programs with in-game overlays for this one. It stops you getting into League.

A connection problem between your internet provider and League's servers is stopping the login. Riot says it usually sorts itself out in a couple of hours.

Something on your PC is keeping the Riot Client from launching or updating a game. Riot lists damaged or outdated files, drivers and background programs as the usual causes.

Another copy of the League client is usually stuck running in the background, and the new login trips over it.

The game asked for memory your PC couldn't give it, so it shut down. Riot points at other programs hogging resources, or Windows running short on virtual memory.

Champion select finishes but the game itself never opens, and the client sits on the reconnect screen. Riot is still investigating the causes.

Vanguard has been installed or reinstalled and needs a reboot before it can run, so Play stays locked. One restart normally clears it.

Mostly a Linux problem: the League client can't pull down its updates.

Your internet connection is too unstable for League to log you in or download its updates.

Something went wrong with graphics while League was starting, and the client won't launch.

The game has decided your version of Windows isn't one it supports, so it won't let you in.

Windows is refusing to open the game's program file. Riot's fix points at the program's compatibility settings.

A DirectX file League needs isn't on the PC yet, so the match won't start. Riot sees it mostly on new computers.

Your PC blue-screens and the crash points at vgk.sys, Vanguard's driver. Riot's article is for 13th and 14th generation Intel CPUs only.

Vanguard checked for Secure Boot at startup and couldn't confirm it was on and working, so the game won't launch.

Vanguard has to verify the game from the internal drive Windows boots from, and yours is installed somewhere else.

Secure Boot is part of the startup trust check Vanguard runs before the game can open, and your PC didn't pass it.

Vanguard couldn't confirm that Memory Integrity, the Windows Core Isolation feature also called HVCI or VBS, is switched on and actually running.

Riot Vanguard wasn't running when the game asked for it. The game can't run without it, so the client shut itself down.

Vanguard hit a problem talking to your PC's Intel Volume Management Device (VMD) controller, which is mostly seen on PCs running Intel Rapid Storage Technology.

A driver on your PC doesn't meet Vanguard's security requirements. Riot's examples are Intel's VMD/RST storage driver, a few third-party NVMe and SATA drivers, and one MediaTek Wi-Fi driver.

Something installed on your PC, usually a driver, doesn't meet Vanguard's security requirements. The error shows the exact file.

Vanguard won't let the game start until Windows is updated or a specific security feature is switched on. Your account is fine.

Vanguard found a problem with how Secure Boot is set up on your PC, even though Secure Boot itself may be on.

Vanguard couldn't start the way it should, or a service it depends on wasn't available, so you were kicked from the game.

League's anti-cheat, Vanguard, couldn't get going or keep its link up, and the game stopped. It's one of seven codes Riot treats as a single problem.

Vanguard couldn't start, keep its connection, or confirm the PC was ready, and the game closed. It can happen at launch or in the middle of a match.

Vanguard couldn't get going, hold its connection or confirm the PC was ready, either as the game launched or while you were playing.

Riot Vanguard, the anti-cheat League needs, failed somewhere between boot-up and your match, so the client shut itself down.

Despite the heading, this is Vanguard's error, not your router's. The anti-cheat lost its grip on the session while you were loading in or already playing.

Vanguard decided your PC's configuration is one League doesn't support, meaning it falls short of the game's system requirements.

Vanguard ran into trouble getting started, staying connected, or confirming the PC was ready, while the game launched or during play.

Vanguard failed a check it runs to keep the game going. It can happen on launch or halfway through a match, and it's a Vanguard problem before it's a network one.

Vanguard couldn't confirm your PC was ready to run the game, or it ran into a problem while starting up.

Vanguard either couldn't check that your PC was ready for the game or ran into trouble during startup, and it ended the session.

Vanguard ran its startup checks on your PC and couldn't get through one of them, so the client closed. Riot treats it as a Windows settings problem first.

Vanguard, Riot's anti-cheat, wasn't running when you pressed Play, so the client shut itself. Your account isn't in trouble.

Vanguard ran into something unexpected while it was starting or while it was talking to the Riot Client, so the client closed.

Vanguard dropped the connection or session it needs, either while the game was starting or partway through a match.

Vanguard either couldn't verify that your PC was ready to run the game or hit a problem while it was starting up. League and VALORANT both use Vanguard, so both games show this code.

Vanguard couldn't get through one of the checks it runs when it starts to decide your PC is trustworthy, and the client shut down.

Vanguard either couldn't verify that your PC was ready for the game or hit a problem while initializing. It can close a game you're already in.

Riot says VAN 135 usually means Vanguard couldn't verify your PC was ready to run the game, or something went wrong as it initialized.

Vanguard believes it, or the game, is sitting inside a virtual machine or some other virtualized setup, and Riot doesn't support Vanguard there.

Something went wrong between the game, the Riot Client and Vanguard as they started up or connected. Riot's article is written around VALORANT, but Vanguard is shared with League.

Vanguard ran into something it didn't expect while it was starting or checking your system, and the client closed. It can also end a game in progress.

Riot has banned this computer's hardware, so every account is blocked from playing on it. Nothing is broken on your PC.

Riot reads VAN 185 as a session or connection problem between the game, the Riot Client and Vanguard. It can kick you out of a game already in progress.

Riot says VAN 193 usually means Vanguard ran into trouble starting up, or couldn't communicate properly with the Riot Client, so the client shut down.

You tried to launch the game too many times in a short spell. Nothing on your PC needs fixing.

Another program on your PC is interfering with Vanguard or changing how it runs. That's the only cause Riot's article gives.

Vanguard is having trouble starting up, keeping its connection, or confirming it's ready, either as the game launches or while you're in a match.

Vanguard spotted a program on your PC that's interfering with it. Riot names antivirus first, and anything that modifies the game environment after that.

Vanguard ran into something unexpected while it was booting up or reporting in to your PC. It's a shared Vanguard code, so VALORANT players get it too.

Vanguard couldn't verify that your PC was ready, or ran into trouble initializing, and the client closed itself.

Vanguard needs TPM 2.0 for its security checks, and it can't see TPM 2.0 turned on in this PC. The same code blocks VALORANT.

Vanguard needs Windows Exploit Protection on, and Riot says this code usually means it's been turned off. It stops VALORANT the same way.

Vanguard requires Secure Boot, and it isn't enabled on this PC. VALORANT uses the same Vanguard, so it gets blocked by the same check.

Vanguard needs Windows 10 20H1 or a newer release, and it doesn't detect one on this PC. It's the same requirement in VALORANT.

Vanguard wants to use Windows' Virtualization-based Security, which needs TPM 2.0 and UEFI firmware, and it can't find that setup on this PC. VALORANT hits the same wall.

Your Windows is older than the 20H1 release Vanguard requires. League and VALORANT both check for it, since they share Vanguard.

Riot Vanguard's own files are damaged or it isn't working the way it should, so the game refuses to start until Vanguard is put back. Nothing's wrong with your account.

Vanguard ran into a fault inside itself that it couldn't get past, so the client shut down rather than keep going with Vanguard in a broken state.

Vanguard needs TPM 2.0, and on your PC it didn't come up properly. Riot ties this to a TPM that was recently cleared or has to be set up again.

Vanguard decided the game is running inside a virtual machine or some other virtualized setup it doesn't support, and it won't run there.

Vanguard tried to check your PC's current state and couldn't finish the job. Riot names drivers, plugged-in devices and background software as the things that get in the way.