Use the exact VAN code to choose the right Windows and Vanguard checks, then collect logs if the error remains.
Start by writing down the complete error code. VAN 128 and VAN 1067 both involve Vanguard, but Riot recommends different checks. Restart Windows and the Riot Client first; then follow the matching section and try opening League after each step. This guide is for Windows, not Wild Rift or the Mac client.
| Code | What Riot says | Start here |
|---|---|---|
| VAN 128 | Vanguard could not complete a startup or system-trust check. | Restore Windows security settings and check debug dumps. |
| VAN 1067 | Vanguard encountered an unexpected startup or system check-in issue. | Update Windows, disconnect unnecessary controllers, and check the Riot Client. |
| VAN 9001 | Required TPM 2.0 is not detected as enabled. | Follow Riot's TPM guide. |
| VAN 9003 | Secure Boot is not enabled as required. | Follow Riot's Secure Boot guide. |
Do not assume VAN 128 or 1067 means you need to change TPM or Secure Boot. If the message names a different code, use Riot's Vanguard error index. A VAL code is a different category from VAN.
VAN 128: security and startup checks
- Follow Riot's Windows security restoration steps to restore test-signing and driver-signature settings to their normal state. The page explains the two administrator commands and what to do if Secure Boot protects a setting. If the computer relies on test-signed drivers for work or development, understand that changing these settings can affect them before proceeding.
- To disable debug memory dumps, press the Windows key, enter
sysdm.cpl, open Advanced → Startup and Recovery → Settings, and set Write debugging information to (none). Confirm and restart. This changes future diagnostic dumps, so retain your prior setting if you need it for troubleshooting. - Install available Windows updates and restart. If the code remains, check the Vanguard service and reinstall Vanguard as described below.
- If that fails, Riot recommends a clean boot to identify conflicting background software, then reinstalling the game as a later step. Follow the official instructions and restore the services you disabled after diagnosis.
VAN 1067: client and connection checks
- Install available Windows updates and restart. Disconnect controllers and other unnecessary USB devices, then retry.
- Run Riot Client as administrator and try again. If the error persists, check the Vanguard service below.
- Follow Riot's clean-boot instructions to identify interfering background programs. Restore your normal startup settings after testing.
- Run a full malware scan with Windows Security or another trusted antivirus and restart after addressing any detections. If necessary, reinstall Vanguard, follow Riot's connection troubleshooting from the VAN 1067 page, and finally consider reinstalling the game.
Check the Vanguard service or reinstall it
If you use Vanguard Pre-Check for on-demand startup, do not automatically change vgc to start with Windows: follow the Pre-Check instructions for your setup. Otherwise, Riot says to press Windows + R, enter services.msc, open vgc, set Startup type to Automatic, start it if stopped, apply, and restart. If vgc is missing or cannot start, do not invent a service: use Riot's support steps.
To reinstall, close the Riot game and client, then follow Riot's Vanguard uninstall guide. Restart the PC and launch the game to reinstall Vanguard. League cannot run while the required Vanguard component is disabled or absent; follow any reinstall prompts and restart if requested.
Pre-Check eligibility: Riot lists Windows 11 version 25H2 or later, Secure Boot, TPM 2.0, IOMMU, VBS and HVCI. Open the Vanguard tray tool (VGTray) to view eligibility and the checks that need attention; follow Riot’s linked guidance for your device. Pre-Check is optional and is not a requirement for every Vanguard installation.
Still blocked?
Use Riot's Repair Tool guide to gather League logs, then attach the resulting ZIP to a Riot support ticket. Include the exact code, when it appears, and the steps already tried. Do not post diagnostic logs publicly: they may contain information about your system.
Sources
Revision history
— Recently updated