Vanguard errors
Step-by-step fixes for Riot Vanguard error codes like VAN 68, VAN 9003 and VAN 1067.
- VAN 68Vanguard lost its connection while the game was runningVanguard lost the session it needs while your game was starting or playing.
- VAN 1067Vanguard ran into a problem while startingVanguard hit an unexpected issue while starting or checking in with Windows.
- VAN 128Vanguard couldn’t finish its startup checksWindows security or debugging settings are stopping Vanguard from verifying your PC.
- VAN 185Vanguard, Riot Client and the game lost their sessionA session or connection problem between the game, Riot Client and Vanguard.
- VAN 84Vanguard couldn’t confirm your PC is readyVanguard couldn’t verify your PC or hit a problem while starting up.
- VAN 135Vanguard couldn’t initialize on your PCVanguard couldn’t verify that your PC is ready or failed while starting.
- VAN 6Vanguard connection errorListed by Riot as a Vanguard connection error. Start with the standard checks.
- VAN 138Vanguard doesn’t work on virtual machinesYou’re running the game or Vanguard in a virtual machine or virtual environment.
- VAN 152This device has a hardware ID banRiot restricted this PC after an account on it broke the rules.
- VAN 9001TPM 2.0 isn’t enabledVanguard needs TPM 2.0 and doesn’t detect it as enabled.
- VAN 9003Secure Boot isn’t enabledVanguard needs Secure Boot and your PC doesn’t have it turned on.
- VAN 9005TPM 2.0, UEFI or Virtualization-based Security is missingVanguard needs TPM 2.0, UEFI firmware and Virtualization-based Security (VBS).