Home/Guides/VALORANT VAN 9001 and VAN 9003: check TPM 2.0 and Secure Boot
Devices and settings

VALORANT VAN 9001 and VAN 9003: check TPM 2.0 and Secure Boot

These Vanguard errors call for different checks. Read the protection status in Windows first; further steps depend on your hardware and boot configuration.

VALORANT
VALORANT · Riot Games

Identify the exact message

Riot’s VAN 9001 entry says Vanguard does not detect TPM 2.0 as enabled. VAN 9003 concerns Secure Boot being disabled. Keep the full text: VAN: RESTRICTION and other codes can carry additional requirements. This article covers Windows PCs; its steps should not be applied to PlayStation or Xbox.

Read TPM status and specification version

Press Win + R, enter tpm.msc, and open TPM management. Look for both a ready-for-use status and specification version 2.0. Version 1.2 is different; an unavailable compatible TPM does not immediately mean you must buy a separate module. Your device may use Intel PTT or AMD fTPM. If the console does not open, Riot suggests checking security processor details under Windows device security.

Read both System Information fields

Open msinfo32 through Win + R and note BIOS Mode and Secure Boot State. This check expects UEFI and Secure Boot On. UEFI with Secure Boot Off is a different situation from Legacy with Unsupported. Save those values and your exact motherboard or laptop model before looking for a firmware switch.

Stop before changing Legacy or MBR

Do not switch a Legacy installation to UEFI by guesswork: Riot warns that an unprepared system may stop booting. That situation requires a separate migration plan, a disk layout check, and a backup. Disk conversion is not the first action for every VAN 9003 error. Use manufacturer and Microsoft documentation for your configuration, or obtain qualified help.

Use instructions for your exact hardware

If a required feature is off, consult your exact PC or motherboard guide through Riot’s documentation links. BIOS labels and menu locations vary. Clearing TPM, resetting keys, and flashing firmware are not substitutes for checking status. With BitLocker encryption, ensure access to your recovery key beforehand: changing protection keys or TPM mode can trigger recovery at the next boot.

Recheck Windows and report persistent errors

After Windows starts, check tpm.msc and msinfo32 again, then retry the game. If the expected states are already confirmed and the error persists, record the code, device model, firmware version, and check results for Riot Support. Do not disable protection to bypass a requirement. Consider a BIOS update under manufacturer guidance after investigating the cause, rather than as a guaranteed fix for every PC.

Sources and checks

Keep reading

↑