Valorant VAN9003 Fix 2026: Secure Boot & TPM Guide
VAN9003 usually appears when Riot Vanguard cannot verify the Windows security setup it expects. This guide walks you through the safe order: check Windows first, enable the right firmware settings second, then repair Vanguard only after Secure Boot and TPM are actually working.
Verified sources: Riot’s VAN 9001/9003/9090 troubleshooting, Riot Vanguard restrictions, Microsoft Secure Boot guidance and Microsoft TPM 2.0 guidance.
How to fix Valorant VAN9003
To fix Valorant VAN9003, open System Information and confirm that BIOS Mode says UEFI and Secure Boot State says On. Then open tpm.msc and confirm that TPM is ready and the specification version is 2.0. If one of those checks fails, fix it in your motherboard firmware before reinstalling Riot Vanguard.
Do not start by clearing TPM, editing random registry keys or downloading “VAN9003 bypass” tools. VAN9003 is normally a security-state problem, not a normal game file problem. The fastest fix is the boring one: make Windows report the correct UEFI, Secure Boot and TPM state, then let Vanguard start cleanly.
VAN9003 is fixed when Windows reports UEFI + Secure Boot On + TPM 2.0 ready, and Vanguard is reinstalled after those settings are correct.
What VAN9003 means in Valorant
VAN9003 is part of the same family as VAN9001 and VAN9090. On Windows 11, Riot Vanguard expects specific platform security features to be available. If Vanguard cannot verify them, Valorant may refuse to launch and show an error about Secure Boot, UEFI, TPM 2.0 or Vanguard requirements.
The confusing part is that BIOS screens can say a setting is enabled while Windows still reports it as off. Vanguard reads what the system actually exposes, not what a motherboard menu seemed to promise. That is why the Windows checks below are more important than guessing inside BIOS.
A UEFI security feature that helps make sure trusted software starts during boot.
A hardware or firmware security processor used by Windows 11 and security features.
The modern firmware mode needed for Secure Boot. Legacy or CSM boot can block the fix.
Riot’s anti-cheat. It checks the security state before Valorant can run.
Common VAN9003 messages and what they point to
The exact wording can vary by client version, Windows build and Vanguard update. Treat the message as a clue, then verify the real status in Windows.
| What you see | Likely cause | First check |
|---|---|---|
| VAN9003 | Vanguard cannot verify the required platform security state. | msinfo32 and tpm.msc |
| This version of Vanguard requires UEFI Secure Boot | Secure Boot is Off, unsupported or blocked by Legacy/CSM boot. | BIOS Mode and Secure Boot State |
| Secure Boot is enabled in BIOS but Valorant still fails | Windows still reports Secure Boot State as Off, keys are missing or OS Type is wrong. | msinfo32 after reboot |
| TPM 2.0 required | TPM is disabled, hidden under Intel PTT or AMD fTPM, or not supported. | tpm.msc specification version |
If you are searching for “valorant van9003 gigabyte,” “valorant van9003 asrock” or “valorant van9003 windows 11,” the core fix is still the same. The brand only changes the menu names inside firmware.
Check Windows before touching BIOS
This is the part most players skip, and it is why they get stuck. Before you change firmware settings, write down what Windows currently reports.
| Windows check | Good result | If it fails |
|---|---|---|
| BIOS Mode | UEFI | Do not just toggle Secure Boot. Legacy/CSM may need careful conversion first. |
| Secure Boot State | On | Enable Secure Boot, load default keys or set Windows UEFI mode in firmware. |
| TPM Status | Ready for use | Enable Intel PTT, AMD fTPM or Security Device Support in firmware. |
| TPM Spec Version | 2.0 | Update BIOS or check whether the device supports TPM 2.0. |
Enable Secure Boot safely
If System Information says Secure Boot State is Off, you need to enter your firmware settings. Microsoft’s normal route is Settings, System, Recovery, Advanced startup, Restart now, then Troubleshoot, Advanced options and UEFI Firmware Settings. Some PCs also use Delete, F2, F10, F12 or Esc during startup.
Inside firmware, look for Boot, Security or Authentication. Secure Boot may be hidden until the system is in UEFI mode and CSM or Legacy boot is disabled. Some motherboards also require OS Type to be set to Windows UEFI Mode or Secure Boot Mode to be Standard, then default factory keys installed.
If BIOS Mode says Legacy, do not randomly switch to UEFI or disable CSM unless you know your Windows disk is ready for UEFI boot. A Legacy/MBR Windows install may fail to boot after the wrong firmware change. Back up important files and follow motherboard or Microsoft guidance before converting boot mode.
Enable TPM 2.0 for Valorant
If tpm.msc says no compatible TPM is found, the setting may be disabled in firmware. On modern systems, TPM is often built into the CPU or chipset and appears under different names depending on Intel or AMD.
| Platform | Common TPM name | Where to look |
|---|---|---|
| Intel | Intel PTT, Platform Trust Technology, PCH-FW | Security, Advanced, Trusted Computing or PCH-FW Configuration |
| AMD | AMD fTPM, Firmware TPM, Security Device Support | Advanced, Trusted Computing, AMD fTPM Configuration or Security |
| Prebuilt laptops | TPM, Security Chip, Firmware TPM | Security, Device Security or Advanced BIOS menu |
After enabling TPM, save changes and boot back into Windows. Open tpm.msc again and confirm the TPM is ready. If you see TPM 1.2 or no TPM 2.0 support, update your BIOS and check your motherboard or laptop support page.
Clearing TPM can affect BitLocker, Windows Hello and device encryption. If BitLocker is enabled, save your recovery key before changing TPM reset options. For VAN9003, enabling TPM is usually what matters, not clearing it.
Common BIOS labels by motherboard brand
Motherboard menus change by model, BIOS version and laptop manufacturer. Treat this as a map of common labels, not a guaranteed click path.
| Brand | Secure Boot labels | TPM labels |
|---|---|---|
| ASUS | Boot, Secure Boot, OS Type, Windows UEFI Mode, Key Management | Intel PTT, AMD fTPM, Trusted Computing |
| MSI | Settings, Advanced, Windows OS Configuration, Secure Boot | Security Device Support, AMD fTPM, Intel PTT |
| Gigabyte | BIOS, Secure Boot, CSM Support, Secure Boot Mode | Intel PTT, AMD CPU fTPM, Trusted Computing |
| ASRock | Security, Secure Boot, CSM, Install Default Secure Boot Keys | Intel Platform Trust Technology, AMD fTPM Switch |
| Lenovo / HP / Dell | Security, Secure Boot, UEFI Boot | TPM, Security Chip, Embedded Security, Firmware TPM |
After any change, reboot and check Windows again. If msinfo32 still says Secure Boot State Off, Vanguard will likely keep throwing VAN9003 no matter what the firmware screen looked like.
If VAN9003 still appears after enabling everything
Once Windows reports UEFI, Secure Boot On and TPM 2.0 ready, then you can repair Riot Vanguard. At that point, the platform state is correct and Vanguard may simply need a clean restart or reinstall.
What not to do when fixing VAN9003
VAN9003 guides on forums often skip the safety part. That is dangerous because firmware and TPM settings are not normal game settings. A wrong change can leave Windows unable to boot or lock you behind a BitLocker recovery prompt.
Enable and verify TPM before considering resets. Save BitLocker keys before any TPM reset.
If Windows was installed in Legacy mode, switching boot mode can break startup.
They can create malware and account risk, and they do not fix the real security-state problem.
Always confirm in msinfo32 and tpm.msc after rebooting into Windows.
Final VAN9003 checklist
Before you queue again, make sure every item below is true. If one fails, fix that item before reinstalling Vanguard again.
Frequently asked questions
What does VAN9003 mean in Valorant?
VAN9003 usually means Riot Vanguard cannot verify the Secure Boot or Windows 11 security requirement it needs. Check BIOS Mode, Secure Boot State and TPM 2.0 before changing anything in BIOS.
How do I fix Valorant VAN9003 on Windows 11?
Open System Information and TPM Management first. Your PC should show BIOS Mode as UEFI, Secure Boot State as On and TPM specification version 2.0. If not, enable the correct UEFI, Secure Boot and TPM settings in your firmware, then reinstall Riot Vanguard if needed.
Why does Valorant say Secure Boot is required when it is enabled in BIOS?
The most common reasons are Legacy or CSM boot mode, missing Secure Boot keys, OS Type not set to Windows UEFI mode, outdated BIOS firmware or Windows still reporting Secure Boot State as Off.
Should I clear TPM to fix VAN9003?
No, not as a first step. Clearing TPM can affect BitLocker and other device security. Save your BitLocker recovery key and follow Microsoft or motherboard guidance before touching TPM reset options.
Does reinstalling Vanguard fix VAN9003?
It can help after Secure Boot and TPM are correctly enabled, but it usually will not fix VAN9003 if Windows still reports Secure Boot as Off or TPM 2.0 as unavailable.
Can I bypass Valorant VAN9003?
You should not use bypass tools or unofficial patches. They can create account and security risk. Fix the underlying Secure Boot, TPM and UEFI status instead.
Valorant fixed, account still not ready?
If your PC is finally launching Valorant again but you still want to skip early leveling, compare Valorant accounts by rank, region, access and skins.