VAN 9001 Error in Valorant: How to Enable Secure Boot and TPM

VAN 9001 is the Valorant error that appears when Vanguard, Riot’s anti-cheat, cannot verify that Secure Boot and TPM 2.0 are enabled on your PC. The fix is to turn both on in your BIOS settings, Vanguard will not let you launch the game without them. This guide walks through every step for Intel, AMD, ASUS, MSI and Gigabyte boards.
What Causes the VAN 9001 Error in Valorant
Vanguard requires two Windows security features to be active: Secure Boot and TPM 2.0. These were optional before Windows 11 but are now enforced by Riot for all Valorant players regardless of which Windows version they run. If either one is disabled, or if your motherboard has them off by default, Vanguard blocks the game at launch and shows VAN 9001.
Common reasons you might see this error:
- You built your PC and never enabled Secure Boot in BIOS (most boards ship with it off).
- You enabled CSM (Compatibility Support Module) for an older OS install, which disables Secure Boot.
- Your motherboard’s firmware TPM (fTPM on AMD, PTT on Intel) is turned off.
- A BIOS update reset your settings to defaults.
- You are running Windows in Legacy/MBR mode instead of UEFI/GPT.
How to Fix VAN 9001: Enable Secure Boot
Secure Boot verifies that only signed software runs during startup. Enabling it takes five minutes in BIOS and does not affect your files or installed programs.
Step 1: Enter BIOS
Restart your PC and press the BIOS key during the boot screen. The key depends on your motherboard:
- ASUS: DEL or F2
- MSI: DEL
- Gigabyte: DEL or F2
- ASRock: F2
- Laptops (HP, Lenovo, Dell): F2, F10, or F12
If you miss it, restart and try again. You can also hold Shift while clicking Restart in Windows, then go to Troubleshoot → Advanced → UEFI Firmware Settings.
Step 2: Disable CSM
CSM (Compatibility Support Module) allows your PC to boot in Legacy mode, which is incompatible with Secure Boot. You must disable CSM before Secure Boot will appear as an option.
- ASUS: Boot tab → CSM → set to Disabled.
- MSI: Settings → Advanced → Windows OS Configuration → CSM/UEFI → set to UEFI.
- Gigabyte: BIOS tab → CSM Support → set to Disabled.
If your Windows installation uses MBR (Master Boot Record) instead of GPT, disabling CSM may prevent Windows from booting. Check first: open Command Prompt as admin, type msinfo32, and look for “BIOS Mode”. If it says UEFI, you are safe. If it says Legacy, you need to convert your disk from MBR to GPT using mbr2gpt /convert /allowfullOS before disabling CSM.
Step 3: Enable Secure Boot
- ASUS: Boot tab → Secure Boot → OS Type → set to Windows UEFI mode. Secure Boot state should now show Enabled.
- MSI: Settings → Advanced → Windows OS Configuration → Secure Boot → set to Enabled.
- Gigabyte: BIOS tab → Secure Boot → Secure Boot Enable → set to Enabled.
Save and exit BIOS (usually F10). Your PC will restart into Windows normally.
How to Enable TPM 2.0
TPM (Trusted Platform Module) is a security chip that stores encryption keys. Most modern motherboards have a firmware-based TPM built into the CPU, AMD calls it fTPM, Intel calls it PTT. You just need to turn it on.
Check if TPM is already enabled
Press Windows + R, type tpm.msc, and press Enter. If the TPM Management window says “The TPM is ready for use” and shows version 2.0, you are done. If it says “Compatible TPM cannot be found”, you need to enable it in BIOS.
Enable fTPM (AMD) or PTT (Intel) in BIOS
- AMD (ASUS): Advanced → AMD fTPM configuration → set to Enabled.
- AMD (MSI): Settings → Security → Trusted Computing → AMD fTPM switch → set to AMD CPU fTPM.
- AMD (Gigabyte): Settings → Miscellaneous → AMD CPU fTPM → set to Enabled.
- Intel (ASUS): Advanced → PCH-FW Configuration → PTT → set to Enabled.
- Intel (MSI): Settings → Security → Trusted Computing → TPM Device Selection → set to PTT.
- Intel (Gigabyte): Peripherals → Intel Platform Trust Technology (PTT) → set to Enabled.
Save, exit, and reboot. Run tpm.msc again to confirm version 2.0 is now active.
Verify the Fix
After enabling both Secure Boot and TPM 2.0:
- Boot into Windows and run
msinfo32. Confirm “Secure Boot State” says On and “BIOS Mode” says UEFI. - Run
tpm.msc. Confirm TPM version 2.0 is ready. - Restart your PC once more (Vanguard loads at boot, not at game launch).
- Open Valorant. VAN 9001 should be gone.
If the error persists, check the Vanguard system tray icon (bottom right of your taskbar). A green shield means Vanguard is running correctly. If the icon is missing or shows an error, restart your PC, Vanguard must run from startup.
VAN 9001 on Windows 10
Windows 10 does not require Secure Boot or TPM for installation, but Vanguard does. The fix is the same: enable both in BIOS. Windows 10 runs fine with Secure Boot enabled as long as your disk is GPT and BIOS mode is UEFI. The only extra risk is on very old installations that were set up in Legacy mode, those need the MBR-to-GPT conversion described above before you can safely enable Secure Boot.
Common Problems After Enabling Secure Boot
- PC does not boot after disabling CSM: Your Windows partition uses MBR. Re-enter BIOS, re-enable CSM temporarily, boot into Windows, convert to GPT with
mbr2gpt, then disable CSM again. - Dual-boot Linux no longer starts: Secure Boot blocks unsigned bootloaders. Most mainstream Linux distributions (Ubuntu, Fedora, Mint) support Secure Boot natively. Others may need their bootloader signed or Secure Boot set to allow third-party keys.
- Older hardware without TPM 2.0: If your motherboard predates 2015 and has no firmware TPM, you may need a discrete TPM module (a small chip that plugs into a header on the motherboard) or a hardware upgrade. Vanguard does not accept TPM 1.2.
Other Valorant Vanguard Errors
VAN 9001 is the most common Vanguard error, but not the only one. Related errors include VAN 9003 (Vanguard not initialised, restart your PC), VAN 68 (connection timeout, check your internet), and VAN -102 (Vanguard crashed, reinstall Vanguard from the Valorant client). For a full list, see our Valorant error codes guide.
If you want to play Valorant without troubleshooting your PC, our Valorant accounts are tested and ready for competitive.
VAN 9001 Error
Wondering about file sizes? Our Valorant download size guide covers install requirements and how to manage disk space.
FAQ
Does enabling Secure Boot delete my files?
No. Enabling Secure Boot and TPM in BIOS does not format your drive or delete any files. It only changes how the boot process verifies software.
Can I get banned for the VAN 9001 error?
No. VAN 9001 is a launch check, not a ban. It just prevents you from starting the game until Secure Boot and TPM are enabled.
Is TPM 2.0 required for Valorant?
Yes. Riot requires TPM 2.0 on all PCs running Valorant. This has been enforced since the Windows 11 Vanguard update, and applies to Windows 10 as well.
Does this fix work on laptops?
Yes. Most laptops made after 2016 have both Secure Boot and TPM 2.0 available in BIOS. The menu names may differ by manufacturer (HP uses “Secure Boot Configuration”, Lenovo uses “Security” tab), but the process is the same.
Why does Vanguard need Secure Boot?
Secure Boot prevents unsigned drivers from loading at startup. Vanguard uses it to block cheat software that runs before the OS fully loads, which is one of the hardest types of cheat to detect otherwise.



