Valorant VAN Error Codes: Complete Guide to Every Error and Fix
A complete reference for all Valorant VAN error codes including VAN 1, 6, 9, 68, 81, 84, 128, 135, 152, and 1067, with causes and step-by-step fixes.
By SensePublished
Understanding VAN Error Codes
VAN errors in Valorant are generated by Riot Vanguard, the game's anti-cheat system. When Vanguard detects a problem with your system configuration, driver status, or security settings, it blocks the game from launching and displays a VAN error code.
These errors are not bans. They indicate that something on your system needs to be fixed before Vanguard will allow the game to run. Here is a complete reference for every common VAN error code.
VAN 1
Cause: Vanguard is not initialized. The Vanguard driver did not load during boot, or it was disabled.
Fix:
- Restart your computer. Vanguard's kernel driver loads at boot, and a simple restart resolves this in most cases.
- If the error persists, check that the Vanguard service is not disabled: open Services (
services.msc), find "vgc", and ensure its startup type is set to Automatic. - Reinstall Vanguard by uninstalling it from Add/Remove Programs, then launching Valorant to trigger a fresh install.
VAN 6
Cause: Vanguard encountered an error during initialization. This can be caused by conflicting software, corrupted Vanguard files, or system issues.
Fix:
- Restart your computer first.
- Disable any software that might conflict with Vanguard: virtualization software (VMware, VirtualBox, Hyper-V), certain RGB control software, overclocking utilities, or other anti-cheat systems running simultaneously.
- Reinstall Vanguard if the error persists.
VAN 9
Cause: Vanguard requires a system restart. This typically appears after Vanguard updates or after certain system changes.
Fix:
- Restart your computer. This error almost always resolves with a reboot.
- If repeated restarts do not help, reinstall Vanguard.
VAN 68
Cause: Vanguard's driver is not running or failed to load.
Fix:
- Restart your computer.
- Open Command Prompt as Administrator and run:
sc query vgkto check the driver status. If it shows STOPPED, runsc start vgkor restart. - Check BIOS for Secure Boot and TPM 2.0 settings (required on Windows 11).
- Ensure your Windows is up to date, as outdated Windows versions can prevent the Vanguard driver from loading.
VAN 81
Cause: Vanguard requires Secure Boot to be enabled. This error appears on Windows 11 systems where Secure Boot is disabled in BIOS.
Fix:
- Enter BIOS/UEFI settings (usually by pressing DEL or F2 during boot).
- Find the Secure Boot option and enable it.
- Ensure your system is booting in UEFI mode, not Legacy/CSM mode.
- Save and restart.
Note: If your Windows was installed in Legacy mode with MBR partitioning, you may need to convert to GPT before enabling Secure Boot. Use mbr2gpt /validate /disk:0 in Command Prompt to check compatibility.
VAN 84
Cause: Vanguard requires TPM 2.0 to be enabled. This error appears on Windows 11 systems where TPM is not detected.
Fix:
- Enter BIOS/UEFI settings.
- For Intel systems: enable "Intel Platform Trust Technology (PTT)".
- For AMD systems: enable "AMD fTPM".
- Save and restart.
- Verify TPM is active: press Win+R, type
tpm.msc, and check that it shows TPM 2.0.
VAN 128
Cause: Vanguard has detected an incompatible driver or software. A specific driver on your system is conflicting with Vanguard.
Fix:
- Check recent driver installations or updates. Roll back any recently updated drivers.
- Known problematic drivers include certain older audio drivers, RGB software drivers, and fan control software.
- Update your graphics drivers to the latest version.
- If you recently installed a VPN, its TAP adapter driver might be the cause. Try disabling or uninstalling it.
VAN 135
Cause: Vanguard requires Windows to be up to date. Your Windows version is below the minimum required by the current Vanguard version.
Fix:
- Run Windows Update and install all available updates.
- If updates fail, run the Windows Update troubleshooter from Settings.
- In rare cases, a clean Windows installation may be necessary if the update system is corrupted.
VAN 152
Cause: Vanguard cannot verify system integrity. This can be caused by modified system files, incompatible drivers, or Secure Boot issues.
Fix:
- Ensure Secure Boot is enabled in BIOS.
- Run
sfc /scannowin an elevated Command Prompt to repair corrupted system files. - Disable Test Mode if enabled:
bcdedit /set testsigning offand restart. - Disable Driver Signature Enforcement bypass if active.
VAN 1067
Cause: The Vanguard service terminated unexpectedly or failed to start properly.
Fix:
- Restart your computer.
- Check Event Viewer (Application and System logs) for Vanguard-related errors that might indicate the cause.
- Temporarily disable your antivirus software to check if it is interfering with Vanguard.
- Reinstall Vanguard.
General Troubleshooting Steps
If none of the specific fixes work:
- Full reinstall: Uninstall both Vanguard and Valorant. Delete remaining files from
C:\Program Files\Riot Vanguardand%LOCALAPPDATA%\Riot Games. Reinstall. - Windows repair: Run
DISM /Online /Cleanup-Image /RestoreHealthfollowed bysfc /scannow. - Clean boot: Start Windows with minimal drivers and services using
msconfigto identify conflicting software. - Check for unsigned drivers: Some VAN errors relate to unsigned drivers on the system. Run
sigverifto check driver signatures.
VAN Errors vs. Bans
It is important to understand that VAN errors are not bans. A ban in Valorant typically shows a specific ban message on the login screen, not a VAN code. If you see a VAN error, your account is fine; your system needs a configuration fix. If you see a ban message, the issue is with your account or hardware, not your system settings.