Fix Valorant VAN errors and Vanguard won't start
Valorant won't launch because of a VAN error or because Vanguard's kernel driver never starts. VAN errors are Riot's anti-cheat rejection codes — they don't mean you're banned. They mean Vanguard couldn't verify its environment, usually after a Windows update, driver update, or security-software change.
VAN 81 — Vanguard initialization failed.
VAL 5 — A Vanguard error has occurred.
What the common codes mean
- VAN 1067: Vanguard's driver (
vgk.sys) isn't loaded. Most common after Windows feature updates and after "Fast Startup" reboots. - VAN 81: Driver loaded but failed verification. Usually antivirus interference or a broken Vanguard install.
- VAL 5: Generic client-side failure — try the reinstall sequence below.
Fixes, in order
Vanguard loads its driver at boot. If you use Fast Startup (default on Windows 10/11), "Shut down" doesn't fully reload it. Click Restart — this alone fixes VAN 1067 for a large share of players.
- Open Control Panel → Programs and Features
- Uninstall Riot Vanguard (not Valorant itself)
- Restart your PC (required — the driver must be removed)
- Launch Valorant via the Riot Client — it will reinstall Vanguard
- Restart once more when prompted, then play
This fixes VAN 1067 and VAN 81 in the vast majority of cases because it rebuilds both the service and the driver registration.
- Press Win+R, type services.msc, press Enter
- Find vgc → right-click → Properties
- Startup type: Automatic (not Automatic (Delayed))
- If stopped, click Start, then launch Valorant
Third-party antivirus tools that hook kernel drivers (360, Malwarebytes, Comodo, etc.) are the #1 cause of VAN 81. Disable them, restart, test — then re-enable. If Vanguard still fails with the antivirus off, uninstall it.
Riot requires Secure Boot on Windows 11. If you recently enabled/disabled it or changed BIOS settings, Vanguard will refuse to run until the next full boot cycle. Also: Settings → Privacy & Security → Windows Security → Device Security → Core isolation → Memory integrity must be off if you're on an older CPU without VBS support.