How to Fix VAN 1067 in Valorant (2026 Guide)
VAN 1067 has meant two things over time. On older Vanguard builds it meant Windows 11 needs TPM 2.0 and Secure Boot. Riot's 2026 article describes it as an unexpected problem starting or checking in. So check TPM and Secure Boot first. If both are on, update Windows, run the Riot Client as administrator, unplug extra devices and reinstall Vanguard.
VAN 1067

What causes VAN 1067
The most common cause is still the old one: on Windows 11, TPM 2.0 or Secure Boot is off, often after a BIOS update reset them. When both are on, VAN 1067 comes from a start-up problem: missing Windows updates, a Vanguard service stopped by an optimizer, a controller or tool that interferes, or a damaged Vanguard install.
How to fix VAN 1067 in Windows
Check your TPM
tpm.msc and press Enter. The TPM is ready for use with Specification Version 2.0 is what you want. Compatible TPM cannot be found means the firmware TPM is switched off in the BIOS. Almost every AMD Ryzen CPU (fTPM) and Intel CPU of the last years (PTT) has one built in.Check how your PC starts
msinfo32 and press Enter. In System Summary look at BIOS Mode and Secure Boot State. BIOS Mode UEFI is what you want. Legacy means your PC starts in the old mode, and Secure Boot cannot be turned on until the disk is converted (next step).Install every Windows update
Run the Riot Client as administrator
Unplug extra devices
Set the Vanguard service to start
services.msc. Find vgc, open it, set Startup type to Automatic and click Start. Optimizer and debloat tools often set it to Disabled. The vgk driver only loads at boot, so restart the PC afterwards, then open the game.Scan for malware
Reinstall Riot Vanguard
sc delete vgc and sc delete vgk in Terminal (Admin), restart and start the Riot Client.How to fix it in the BIOS
This part happens in your PC's firmware setup (the BIOS), so open this page on your phone first. Menu names change a little between BIOS versions: if a path below does not match, look for the words in bold. Only if tpm.msc or msinfo32 showed TPM or Secure Boot off.
Restart into the BIOS
shutdown /r /fw /t 0 in Terminal (Admin). You can also press Del right after switching the PC on (desktops; F2 on many laptops and some ASRock and MSI boards).Change these settings
- Turn on the firmware TPM: AMD fTPM (often Firmware TPM) on AMD, Intel PTT (Platform Trust Technology) on Intel.
- Turn CSM (Compatibility Support Module, Legacy boot) off so the PC starts in UEFI mode. Only when
msinfo32shows BIOS Mode UEFI or after the GPT conversion above, or Windows will not start. - Turn on Secure Boot and install the default keys (Install default Secure Boot keys or Restore Factory Keys). Secure Boot mode Standard, OS type Windows UEFI mode.
Where to find them on your board:
ASUS
TPM 2.0 (AMD fTPM / Intel PTT): Advanced > AMD fTPM configuration > Firmware TPM (AMD), or Advanced > PCH-FW Configuration > PTT (Intel)
CSM off (UEFI only): Boot > CSM > Launch CSM: Disabled
Secure Boot: Boot > Secure Boot > OS Type: Windows UEFI mode, then Key Management > Install Default Secure Boot keys
MSI
TPM 2.0 (AMD fTPM / Intel PTT): Settings > Security > Trusted Computing > Security Device Support: Enable, then AMD CPU fTPM or Intel PTT
CSM off (UEFI only): Settings > Advanced > Windows OS Configuration > BIOS UEFI/CSM Mode: UEFI (on some boards: Windows 10/11 WHQL Support: Enabled)
Secure Boot: Settings > Advanced > Windows OS Configuration > Secure Boot: Enabled, Secure Boot Mode: Standard
Gigabyte (AORUS)
TPM 2.0 (AMD fTPM / Intel PTT): Settings > Miscellaneous > AMD CPU fTPM (AMD) or Intel Platform Trust Technology (PTT) (Intel)
CSM off (UEFI only): Boot > CSM Support: Disabled
Secure Boot: Boot > Secure Boot: Enabled, Secure Boot Mode: Standard (or Restore Factory Keys)
ASRock
TPM 2.0 (AMD fTPM / Intel PTT): Advanced > CPU Configuration > AMD fTPM switch (AMD), or Security > Intel Platform Trust Technology (Intel)
CSM off (UEFI only): Boot > CSM (Compatibility Support Module): Disabled
Secure Boot: Security > Secure Boot: Enabled, then Install Default Secure Boot Keys
Laptops and prebuilt PCs
HP: Esc then F10, Advanced > Secure Boot Configuration, Security > TPM Embedded Security, Advanced > System Options > Virtualization Technology.
Lenovo: F1 on ThinkPad, F2 or the Novo button on IdeaPad and Legion, Security > Secure Boot, Security > Security Chip, Security > Virtualization.
ASUS: F2, Security > Secure Boot Control, Advanced > Trusted Computing.
Acer: F2, set a Supervisor password first or Secure Boot stays greyed out, then Boot > Secure Boot and Security > TPM.
MSI: Del, Security > Secure Boot, Advanced > Trusted Computing.
Gigabyte / AORUS: F2, Security > Secure Boot, Advanced > Trusted Computing.
Save and restart
If it still does not work
Contact Riot Support
Fix it in one click with RIP Tweaks (free)
RIP Tweaks 6.9.3 has a free anti-cheat error fixer. Open Fixes, then Anti-cheat errors, and paste VAN 1067 or pick your game. The app first checks what your PC has right now (for example Secure Boot: Off, TPM: On) and shows only the steps still missing.

It fixes the Windows side itself
It takes you into the BIOS with the right card
It checks again after the restart
The fixer is free in every plan, also without an account. Download RIP Tweaks (free)
Check that it worked
msinfo32 shows Secure Boot State On, tpm.msc shows a ready TPM 2.0, and the Riot Client starts without VAN 1067.
Frequently asked questions
Why does VAN 1067 come back after every BIOS update?
BIOS updates often reset fTPM and Secure Boot to off. Turn both on again after each update.
Does VAN 1067 happen on Windows 10?
The TPM and Secure Boot version of it is a Windows 11 thing. On Windows 10 it points to the start-up causes: updates, the vgc service, interfering tools or a broken install.
Can a controller cause VAN 1067?
Yes, Riot lists unplugging controllers and closing remap tools as a step. Some controller drivers interfere with Vanguard at start.
How do I know if my PC has TPM 2.0?
Press Win + R, type tpm.msc and press Enter. If it says the TPM is ready for use and Specification Version is 2.0, you have it. If it says no compatible TPM was found, the firmware TPM is usually just switched off in the BIOS.
Do I have to reinstall Windows to turn on Secure Boot?
No. If msinfo32 already says BIOS Mode UEFI, you only switch Secure Boot on in the BIOS. If it says Legacy, Microsoft's MBR2GPT tool converts the disk without deleting anything, and then you turn CSM off and Secure Boot on.
Can changing these settings get me banned?
No. These are the anti-cheat's own requirements, and the publisher asks you to change them. Bans come from cheats and tools that tamper with the game, never from turning on Windows security features.
Sources
- Riot Support: Vanguard error codes (updated 22 May 2026)
All anti-cheat errors: Anti-Cheat Error Fixes. Related: How to Fix VAN 9001 in Valorant (TPM 2.0 and Secure Boot) – 2026 and How to Fix "Vanguard Not Initialized" (VAN -1, VAN 57, VAN -117) – 2026.