How to fix the VALORANT VAN9003 error
This means Vanguard found Secure Boot is not enabled, or the system is out of compliance with its settings. Enabling Secure Boot fixes it. Jump to your situation below or work through the methods in order.
This means Vanguard found Secure Boot is not enabled, or the system is out of compliance with its settings. Enabling Secure Boot fixes it. Jump to your situation below or work through the methods in order.
VAN9003 means Riot Vanguard requires Secure Boot to be enabled and found it off, or that the build is out of compliance with the current system settings. Vanguard uses Secure Boot to confirm only trusted, signed code ran during boot, which stops cheaters loading malicious drivers before the anti-cheat starts. So if Secure Boot is disabled, in legacy / CSM mode, or in a mismatched Secure Boot key configuration, Vanguard refuses to load. The fix is to enable Secure Boot in UEFI, make sure the PC is in UEFI mode with CSM disabled (converting an MBR disk to GPT if needed), and, where the firmware offers it, reset the Secure Boot keys to the Standard configuration. Confirm the result in msinfo32. If it still fails, ensure the Vanguard service is running, reinstall Vanguard, and update the BIOS.
Secure Boot is the part of UEFI that allows only signed, trusted code to run at startup. Vanguard relies on it to be sure no tampered driver loaded before the anti-cheat. VAN9003 means Secure Boot is not active, so Vanguard cannot trust the boot chain and stops.
The out-of-compliance wording covers the related cases: the PC is in legacy mode where Secure Boot is unavailable, or the Secure Boot keys are in a custom or mismatched state. Getting into UEFI mode and enabling Secure Boot with standard keys brings the system back into compliance.
“VAN9003 is specifically the Secure Boot one. Vanguard wants proof that only trusted code booted, and Secure Boot is that proof, so if it is off, Vanguard says no. I enable Secure Boot in the UEFI, and the usual catch is a PC still in legacy mode, where Secure Boot is greyed out until you switch to UEFI and convert the disk to GPT. If the board has weird custom Secure Boot keys, resetting them to Standard sorts the out-of-compliance variant. Then confirm it in msinfo32.”
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.VAN9003 means Vanguard requires Secure Boot, so enable it in UEFI and confirm in msinfo32. The common blocker is legacy / CSM mode, so switch to UEFI and convert the disk to GPT first. For the out-of-compliance variant, reset the Secure Boot keys to Standard, and if it persists, reinstall Vanguard and update the BIOS.
If Secure Boot reads as On but VAN9003 continues, an older BIOS handling Secure Boot modes inconsistently is a common cause; updating the BIOS and reinstalling Vanguard usually resolves it. You can also submit your error to us for a tailored fix.