GameHow to Fix Valorant VAN 9001: Enable TPM 2.0 & Secure Boot
You upgraded to Windows 11, everything else runs fine, you launch Valorant — and instead of the main menu you get a red screen: This build of Vanguard requires TPM version 2.0 and Secure Boot to be enabled in order to play. (VAN 9001). Restarting changes nothing, reinstalling the client changes nothing, and the error doesn't tell you how to fix it. If that sounds familiar, this guide is for you.
In plain English, VAN 9001 means Riot's anti-cheat, Vanguard, refuses to start because your PC's security settings don't meet its requirements on Windows 11. This is different from most Valorant errors: it's not a server problem, not a driver problem, and not a corrupted file — it's your motherboard's firmware settings. The good news? For the vast majority of players, the fix is two toggles in the BIOS/UEFI, and you can be back in the agent select in about fifteen minutes. Start at the top and work down.
What does Valorant VAN 9001 actually mean?
Vanguard is a kernel-level anti-cheat — it runs deep in your operating system to catch cheats before they can touch the game. On Windows 11, Vanguard takes advantage of two hardware-backed security features:
- TPM 2.0 (Trusted Platform Module 2.0) — a security chip (or firmware inside your CPU) that can verify your system hasn't been tampered with at boot.
- Secure Boot — a UEFI feature that only allows properly signed operating systems and drivers to load at startup, blocking rootkits and boot-level cheats.
Vanguard checks for both every time it starts. If either one is missing or disabled, you get VAN 9001 and Valorant won't launch. Importantly, this requirement only exists on Windows 11 — on Windows 10, Vanguard runs without it. And in most cases, your hardware does support both features: they were simply shipped switched off in the BIOS by the motherboard manufacturer. So VAN 9001 is usually a five-minute settings change, not a hardware problem.
What causes VAN 9001?
Every one of these comes down to the firmware settings, not the game:
- TPM disabled in the BIOS — the single most common cause. Many boards ship with it off. On Intel systems it's labeled Intel PTT (Platform Trust Technology); on AMD systems it's AMD fTPM.
- Secure Boot disabled in the BIOS — also frequently off by default, especially on custom-built PCs.
- Legacy/CSM boot mode — Secure Boot physically cannot work in Legacy mode. If your system boots in Legacy, the Secure Boot option is grayed out or missing entirely.
- MBR-partitioned system disk — disks formatted the old MBR way can't boot in UEFI mode, which blocks Secure Boot too.
- Outdated BIOS firmware — older BIOS versions sometimes misreport TPM status to Windows or hide the option completely.
- Old hardware without TPM 2.0 — a minority of older CPUs and boards genuinely lack TPM 2.0. No setting can fix this; it's the one case that needs a hardware upgrade.
tpm.msc, and hit Enter. If it says The TPM is ready for use with Specification Version: 2.0, your TPM is already on and you can skip to Fix 3. If it says Compatible TPM cannot be found, your TPM is off — Fix 2 is your target. Then press Win + R again, type msinfo32, and look at BIOS Mode and Secure Boot State. Write down what each says — that tells you exactly which fixes below you need.1Confirm the requirement applies to you
First, make sure you're actually on Windows 11 — go to Settings → System → About and check the edition. If you're on Windows 10, you shouldn't be seeing VAN 9001 at all; if you are, something else is wrong and the BIOS changes below won't help. On Windows 11, also confirm your CPU is on the supported list: most Intel chips from the 8th generation onward and most AMD Ryzen chips support TPM 2.0 (either as a firmware feature in the CPU or a discrete chip). If your hardware is from roughly 2018 or later, you're almost certainly fine and this is purely a settings problem.
2Enable TPM 2.0 in the BIOS/UEFI
This is the fix that resolves most VAN 9001 cases. Restart your PC and press the BIOS key during startup — usually Delete, F2, or F12 (the boot screen shows which). Once inside the BIOS/UEFI:
- On Intel systems: look under Advanced → PCH-FW Configuration or Security for Intel PTT or PTT and set it to Enabled.
- On AMD systems: look under Advanced → CPU Configuration or Security for AMD fTPM, PSP fTPM, or Firmware TPM and set it to Enabled.
The exact menu names vary by manufacturer — ASUS, MSI, Gigabyte, and ASRock all put it in slightly different places. If you can't find it, search your motherboard model plus enable TPM for the exact menu path. Save and exit (F10 on most boards), let Windows boot, and re-run tpm.msc to confirm it now says the TPM is ready for use.
3Enable Secure Boot
Back in the BIOS/UEFI, go to the Boot or Security tab and find Secure Boot. Switch it to Enabled. On some boards you first need to change the OS Type setting from Other OS to Windows UEFI mode before the Secure Boot option becomes selectable. Save, exit, and boot into Windows. Then check msinfo32 again — Secure Boot State should now read On. If the option is grayed out or missing, don't force it: that means your system is booting in Legacy mode, and Fix 4 is what you need first.
4Switch from Legacy boot to UEFI mode
This is the fix for players who can't enable Secure Boot at all. Check msinfo32: if BIOS Mode says Legacy, Secure Boot can never work — it's a UEFI-only feature. The fix has two parts:
- Convert your disk from MBR to GPT: open Command Prompt as administrator and run
mbr2gpt /validatefirst. If validation succeeds, runmbr2gpt /convert. This converts the partition style without deleting your files — but back up anything important first anyway, because disk operations always carry some risk. - Change the BIOS boot mode: go back into the BIOS/UEFI, find the Boot Mode or CSM setting, switch it from Legacy/CSM to UEFI (disable CSM), save, and exit.
After switching to UEFI, the Secure Boot option in Fix 3 becomes available. Enable it, and msinfo32 should show BIOS Mode: UEFI and Secure Boot State: On.
vgk.sys) or running registry hacks. Don't do this. Vanguard won't launch the game without its driver, and tampering with anti-cheat components can look exactly like cheating to Riot's systems — risking your account for zero benefit. The BIOS fixes above are the legitimate, permanent solution.5Update your BIOS firmware and Windows
If the TPM or Secure Boot options don't appear in your BIOS at all, or Windows still reports them as missing after you enabled them, your BIOS is probably out of date. Visit your motherboard manufacturer's support page, find your exact model, and check the BIOS version against what's installed (shown on the BIOS main screen or in msinfo32). A newer BIOS can expose previously hidden TPM options and fix TPM detection bugs — this is especially common on boards from 2019–2021. Follow the manufacturer's flash instructions exactly and don't interrupt the process. While you're at it, install all pending Windows updates in Settings → Windows Update: Microsoft has fixed several TPM status-reporting issues in Windows 11 updates, and Vanguard's checks rely on what Windows reports.
6Reinstall Riot Vanguard
Sometimes the firmware settings are all correct but Vanguard's installation is stale and keeps reading the old state. Go to Settings → Apps → Installed apps, find Riot Vanguard, and Uninstall it. Restart your PC — this is important, because Vanguard's driver stays loaded until a reboot. Then launch Valorant: the game detects the missing anti-cheat and reinstalls it automatically. After the reinstall, Vanguard runs its TPM and Secure Boot checks fresh against your now-correct settings. If you want to be thorough, you can also reinstall Valorant itself, but Vanguard alone is enough in most cases.
7Check for hardware limits or contact Riot support
If your BIOS has no TPM option even after a BIOS update, and your CPU predates TPM 2.0 support (very old Intel chips, pre-Ryzen AMD), your hardware genuinely can't meet the requirement — no software trick will change that, and the honest fix is newer hardware. For everyone else whose settings look right but VAN 9001 won't clear: submit a ticket to Riot Support with your motherboard model, BIOS version, CPU, and screenshots of tpm.msc and msinfo32. Their team can confirm whether your specific board is on a known-issue list and walk you through manufacturer-specific steps. Include the fixes you've already tried so they don't make you repeat them.
Quick checklist to keep VAN 9001 away
- Leave TPM and Secure Boot enabled permanently — don't toggle them off for other OS installs unless you stop playing Valorant.
- After any BIOS update, double-check that TPM and Secure Boot stayed enabled — some updates reset BIOS settings to defaults.
- Keep your BIOS reasonably up to date; manufacturers fix TPM detection bugs over time.
- If you dual-boot Linux or another OS, use UEFI mode and keep Secure Boot on rather than switching to Legacy.
- Bookmark this page's Fix 4 steps — BIOS resets after power loss are the most common reason VAN 9001 comes back months later.
Frequently asked questions
What does Valorant VAN 9001 mean in plain English?
It means Riot Vanguard, Valorant's anti-cheat, can't start because your PC is missing two security features it requires on Windows 11: TPM 2.0 and Secure Boot. In most cases your hardware has both and they're simply switched off in the BIOS — it's a settings problem, not a broken PC.
Is VAN 9001 caused by my PC or by Riot's servers?
It's always your PC's firmware settings. VAN 9001 never comes from Riot's servers, so restarting the client, your router, or waiting it out won't help. The fix is enabling TPM 2.0 and Secure Boot in your BIOS or UEFI settings — Fix 2 and Fix 3 above.
Can I avoid VAN 9001 by playing on Windows 10?
Vanguard enforces the TPM 2.0 and Secure Boot requirement on Windows 11 only, so Windows 10 doesn't show VAN 9001. But downgrading your whole operating system is a drastic move — enabling the two settings in the BIOS takes fifteen minutes and is the fix Riot intends.
What is the difference between Intel PTT and AMD fTPM?
They're the same thing under different names: a firmware-based TPM built into the processor. Intel calls it PTT (Platform Trust Technology); AMD calls it fTPM. Enabling either one gives you TPM 2.0, which is exactly what Vanguard checks for.
Why can't I enable Secure Boot in my BIOS?
The most common reason is that your PC boots in Legacy (CSM) mode instead of UEFI — Secure Boot is a UEFI-only feature, so the option is grayed out or missing in Legacy mode. Convert your disk from MBR to GPT and switch the BIOS boot mode to UEFI (Fix 4), then the Secure Boot option appears.
Does VAN 9001 mean my Valorant account is banned?
No. VAN 9001 is a hardware security requirement, not a punishment, and it says nothing about your account standing. Your rank, skins, and inventory are completely untouched — the error clears the moment TPM 2.0 and Secure Boot are enabled and Vanguard reinstalls.
For most players, VAN 9001 ends at Fix 2 or 3 — the TPM and Secure Boot toggles were off by default and turning them on is all Vanguard needed. The settings feel intimidating because they live in the BIOS, but they're just two on/off switches, and your motherboard manual (or a quick search for your board model) will point you to the exact menu. And if you'd rather skip launchers, anti-cheat requirements, and BIOS menus entirely for a while, the free browser games here on GameAdda start with a single click. 🎮