Riot Vanguard requires TPM 2.0 and Secure Boot to be on before it lets VALORANT launch. This error means one or both are off. Enabling them fixes it. Jump to your situation below or work through the methods in order.
VAN9001 (and the related VAN1067) means Riot Vanguard, VALORANT's anti-cheat, found that TPM 2.0 or Secure Boot is not enabled, so it blocks the game from launching. Vanguard runs at the kernel level and uses Secure Boot and the TPM to confirm the system is in a trusted state before it loads, so both must be on. Often the hardware fully supports them and they are simply switched off in the firmware, sometimes a Windows update toggles Secure Boot off in the background. The fix is to check the current state with msinfo32 and tpm.msc, then enable Secure Boot and the TPM (Intel PTT or AMD fTPM) in UEFI, switching to UEFI mode and disabling CSM if needed. For VAN1067 specifically, also confirm the Vanguard service is running and clear the VALORANT cache. Once Secure Boot and TPM 2.0 are on, VALORANT launches.
Vanguard is a kernel-level anti-cheat, so it cares deeply about whether the system booted in a trusted, untampered state. Secure Boot guarantees only signed boot code ran, and the TPM attests to the platform's integrity. Vanguard requires both as evidence the PC is trustworthy.
VAN9001 means that evidence is missing: Secure Boot or TPM 2.0 is off, so Vanguard will not load and the game cannot start. Because most modern PCs support both, the fix is usually just enabling them in the firmware rather than any hardware change.
“VAN9001 scares players into thinking their PC is too old, but almost always the hardware is fine and Secure Boot or TPM is just switched off in the BIOS. So I check msinfo32 and tpm.msc first to see which one, then flip Secure Boot and the TPM on in the UEFI. The only real snag is a PC stuck in legacy mode, then you have to move to UEFI and convert the disk to GPT before Secure Boot will even turn on. After that VALORANT launches.”
msinfo32, and confirm Secure Boot State is On and BIOS Mode is UEFI.tpm.msc, and confirm the TPM is ready and the Specification Version is 2.0.%AppData%, go to Local, VALORANT, Saved, and delete the Crashes folder.VAN9001 and VAN1067 mean Vanguard needs TPM 2.0 and Secure Boot, so check msinfo32 and tpm.msc, then enable both in UEFI, moving to UEFI mode and a GPT disk if the PC is in legacy mode. For VAN1067, also confirm the Vanguard service is running and clear the VALORANT cache.
If Secure Boot and TPM 2.0 both read as on in msinfo32 and tpm.msc but VAN9001 persists, reinstall Vanguard and update the BIOS, since an older firmware or a corrupt Vanguard install can still trigger it. You can also submit your error to us for a tailored fix.