VAN 67 is triggered when Vanguard detects that Secure Boot is not enabled. Since Riot made Secure Boot and TPM 2.0 mandatory for Vanguard, this error blocks Valorant on machines where Secure Boot has been turned off — commonly after a manual BIOS change or Windows reinstallation.
What does Valorant VAN 67 mean?
Riot Games requires Secure Boot as part of Vanguard's hardware-level security. Secure Boot prevents unsigned code from loading during the boot process, which makes it harder for cheats to load before Vanguard does. VAN 67 means this requirement is not met on your system.
Why Secure Boot may be off
Secure Boot is often disabled when installing Linux, dual-booting, or using older hardware that doesn't support it. It can also be turned off during Windows reinstallation or BIOS resets. After enabling it again, Valorant will work normally.
Enabling Secure Boot
Access BIOS/UEFI (usually by pressing Del, F2, or F12 at startup). Look for a Secure Boot setting under Security or Boot tabs. Enable it, save, and restart. If Secure Boot is unavailable, your hardware may be too old to meet Vanguard's requirements.
How to fix step by step
- 1Restart your PC and enter BIOS/UEFI (press Del, F2, or F10 during startup — check your motherboard manual).
- 2Navigate to the Security or Boot tab and find the Secure Boot setting.
- 3Enable Secure Boot and save changes.
- 4Restart and verify: Settings > System > Recovery > Advanced Startup > Restart now > Troubleshoot > UEFI Firmware Settings, or use msinfo32 to confirm Secure Boot is On.
- 5Relaunch Valorant through Riot Client after confirming Secure Boot is active.
- 6If your hardware does not support Secure Boot, Valorant cannot run on that machine — check Riot's system requirements.
How VAN-67 differs from related codes
- Error VAN-68: Vanguard requires TPM 2.0 (Trusted Platform Module) to be enabled. Your system either lacks TPM 2.0 or it is disabled in BIOS. (user-side)
- Error VAN-1: Vanguard, Valorant's anti-cheat system, is not running or failed to initialize, so your client is not authorized to launch a match. (user-side)