On screen: VAN9003. This build of Vanguard requires secure boot to be enabled in order to play.
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.
Riot's driver refuses to load because UEFI Secure Boot is disabled. Their own wording: VAN 9003 means Secure Boot is not enabled on your system, which is required by Vanguard.
This is configuration, not a fault, and it can never be caused by a Valorant outage.
Press Win+R, run msinfo32 and read the Secure Boot State line. If it says Off, this is your code and it is entirely local. If it says On and you still get VAN 9003, that is worth a ticket rather than more BIOS changes.
Before enabling fTPM or Secure Boot on an AMD board, suspend BitLocker or save your recovery key. Changing platform measurements makes a number of machines demand the recovery key on the next boot.
VAN 9001 is the related code for TPM 2.0 rather than Secure Boot, and needs the same UEFI trip for a different setting.
Operator documentation: support.riotgames.com. Riot maintains two separate registries and it matters here: VAN codes are Vanguard, their anti-cheat, while VAL codes are the game. Their Vanguard index states this split explicitly. VAN 9003 is firmly in the anti-cheat registry.
Riot's driver refuses to load because UEFI Secure Boot is disabled. Their own wording: VAN 9003 means Secure Boot is not enabled on your system, which is required by Vanguard.
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.
Start with: Check BIOS Mode in msinfo32 before touching anything. If it says Legacy rather than UEFI, do not enable Secure Boot yet. Read the next step first.