The short answer
Riot describes VAN9003 as Secure Boot not being enabled. First read BIOS Mode and Secure Boot State in msinfo32. Before considering firmware changes, back up important files, confirm access to the encryption recovery key and find the manufacturer’s model-specific instructions. Stop and ask for help if any of these are unclear.
Different symptom or still not fixed? Find the next check →Key facts
- Read first
- msinfo32: BIOS Mode and Secure Boot State
- Before changes
- Backup, recovery-key access and exact PC model
- Already On
- Recheck after restart and record the remaining error
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| Not sure which VAN error appeared | Record the number and complete message | Step 1 |
| UEFI with Secure Boot Off | Prepare recovery access and the correct manufacturer guide | Step 3 |
| Legacy, Unsupported or unclear | Stop before changing boot mode | Step 2 |
| UEFI and On but the error remains | Give Riot the post-restart state and full error | Step 4 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1|Record the error and who manages the PC
Similar error numbers can need different checks.
Time: About 3–5 minutes to check · Risk: low
- Record VAN9003, the full message, time and Windows version. For VAN9001, use the TPM article instead.
- For a work or school PC, contact its administrator without changing firmware or encryption settings.
- Before considering BIOS work, back up important files and make sure you can access the BitLocker/device-encryption recovery key from another device. Never post that key in article feedback or public screenshots.
Step 2|Read both fields in msinfo32
This check reads the current state without changing it.
Time: About 3–5 minutes to check · Risk: low
- Press Windows + R, enter msinfo32 and press Enter. In System Information, record BIOS Mode and Secure Boot State.
- If they show UEFI and On, continue to Step 4. For UEFI and Off, use Step 3 to check the prerequisites.
- For Legacy, Unsupported or an unclear result, stop. Give the manufacturer the model and displayed values before switching to UEFI or disabling CSM.
Reading the state needs no rollback. Switching boot mode alone can prevent Windows from starting.
Step 3|Prepare recovery access and the model guide
An Off result is not enough to start changing BIOS settings.
Time: About 3–5 minutes to check · Risk: medium
- Identify the exact PC or motherboard model. Use the manufacturer resources linked in Riot’s Secure Boot guide to find instructions for that model.
- Confirm your backup, recovery-key access from another device, original settings and recovery procedure before any change. Ask the manufacturer if disk layout or model support is unclear.
- Only follow the model-specific procedure after those conditions are established. If an option is gray or the screen differs from the guide, cancel without saving; do not delete or reset Secure Boot keys.
This general guide does not walk through BIOS updates, disk conversion or key management. Any recovery also needs the manufacturer’s procedure.
Step 4|Recheck the state and error after restart
Record Windows state and game behavior separately.
Time: About 3–5 minutes to check · Risk: low
- Save your work, restart the PC and read the two msinfo32 fields again before launching VALORANT.
- If UEFI and On are confirmed but the game stops, check whether the complete error still says VAN9003 or now shows VAN: RESTRICTION or another message.
- Send Riot support the model, Windows version, displayed states, any changes and the post-restart error. Exclude recovery keys and private information.
Avoid
- Do not clear TPM or delete/reset Secure Boot keys
- Do not apply a blanket Legacy-to-UEFI switch, CSM change or disk conversion
- Do not disable Vanguard or antivirus protection to bypass the error
Important cautions
- Stop before firmware changes if recovery-key access or model instructions are missing. Ask the administrator or manufacturer.
- On other Windows versions too, follow the displayed error and current Riot requirements; the OS name alone does not settle the requirement.
FAQ
What if Secure Boot is already On?
Record msinfo32 and the complete error after restarting. Another requirement may be involved. Contact Riot instead of repeatedly toggling firmware settings.
Does Unsupported mean I should change BIOS mode?
No. Ask the manufacturer to check model support, boot mode and disk layout first. Do not switch to UEFI or manipulate keys on that assumption.
Sources
We checked these official pages and wrote the steps in our own words. Follow the publisher’s page if it has changed.
Riot: error VAN9003Riot: Secure Boot state and manufacturer resourcesMicrosoft: find your BitLocker recovery keyRiot: Vanguard security requirementsVALORANTJapanese version of this page