Valorant error

Valorant VAN 9001

On screen: VAN9001. This build of Vanguard requires TPM 2.0 to be enabled in order to play.

Not an outage

People land on this error while searching whether the service is down. It is not. This code cannot be produced by an outage, so no amount of waiting will clear it.

What it actually means

Riot's Vanguard kernel driver refuses to start on Windows 11 unless the machine reports a TPM 2.0 device and UEFI Secure Boot is enabled. On Windows 10 the requirement is not enforced.

The check fails when TPM is switched off in firmware — it is called PTT on Intel boards and fTPM or PSP on AMD — or when the machine boots in Legacy/CSM mode from an MBR disk, which makes Secure Boot impossible until the disk is converted. Virtual machines fail for the same reason.

How to tell which one you have

Nothing to tell apart. This is hardware configuration and it can never be caused by a Valorant outage. If you arrived here from a search for whether Valorant is down, it is not — at least not for this reason.

Before you change anything

Before you enable fTPM on an AMD board, suspend BitLocker or save your recovery key. Turning it on changes the platform measurements and a number of machines demand the BitLocker recovery key on the next boot. This is the most damaging omission in the advice currently ranking for this error.

Fixes, in the order worth trying

Run tpm.msc — If it says a compatible TPM cannot be found, the chip is switched off in firmware rather than absent. Almost every modern board has one.
Run msinfo32 — Check two lines: BIOS Mode should read UEFI, and Secure Boot State should read On.
Enable fTPM or PTT and Secure Boot in UEFI — Intel calls it Intel Platform Trust Technology, AMD calls it AMD fTPM.
If BIOS Mode says Legacy, convert the disk first — Run mbr2gpt /convert /allowfullos before touching Secure Boot. Enabling Secure Boot on an MBR disk leaves the machine unbootable, and this is the step the guides on the first page of results leave out.
After a BIOS update, restore factory keys — Secure Boot often drops back to Setup Mode after a firmware update, which fails the check even though it looks enabled.
Reinstalling Vanguard or Valorant does nothing — The check is against firmware state, not against the installation.

Neighbouring codes: VAN 9003 is specifically Secure Boot, and VAN 1067 means the Vanguard driver is not running, which needs a different fix entirely.

Operator documentation: support.riotgames.com. Riot's page is current — last revised 4 February 2026 — but it is three sentences long. Their TPM guide sits at support.riotgames.com/riot/client/tpm-20-guide.

Common questions

What does Valorant VAN 9001 mean?

Riot's Vanguard kernel driver refuses to start on Windows 11 unless the machine reports a TPM 2.0 device and UEFI Secure Boot is enabled. On Windows 10 the requirement is not enforced.

Is Valorant VAN 9001 an outage?

People land on this error while searching whether the service is down. It is not. This code cannot be produced by an outage, so no amount of waiting will clear it.

How do I fix Valorant VAN 9001?

Start with: Run tpm.msc. If it says a compatible TPM cannot be found, the chip is switched off in firmware rather than absent. Almost every modern board has one.