The short answer
VAN9005 means Vanguard did not detect required security settings. Follow Riot’s current order: TPM 2.0, Secure Boot, then memory integrity. Read the state with tpm.msc and msinfo32 first; do not use disabling VBS from older articles as a general fix.
Different symptom or still not fixed? Find the next check →Key facts
- Order
- TPM 2.0 → Secure Boot → memory integrity
- Read-only checks
- tpm.msc and msinfo32
- Legacy or unsupported
- Check model and recovery options before switching settings
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| TPM missing or specification 1.2 | Check readiness and model support | Step 1 |
| Legacy BIOS mode or Secure Boot off | Seek guidance before changing boot mode | Step 2 |
| TPM and Secure Boot look correct | Check running memory integrity | Step 3 |
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|Read TPM readiness and specification
Enabling TPM is not the same as clearing it.
Time: Allow 3–5 min to check · Risk: low
- Record the full VAN9005 message, Windows version and exact PC or motherboard model. Open tpm.msc with Windows + R and read readiness and Specification Version 2.0.
- For missing TPM or version 1.2, check manufacturer support for the model. Do not infer absence or failure, clear or switch TPM, or buy parts from this reading alone.
- Before configuration changes, confirm backups and access to the BitLocker/device encryption recovery key. Ask the administrator for managed PCs. Never publish the key.
Step 2|Read UEFI and Secure Boot status
Stop before switching settings if the system uses Legacy.
Time: Allow 3–5 min to check · Risk: low
- In msinfo32, record BIOS Mode and Secure Boot State separately: UEFI and On are the readings to check.
- For Legacy, Unsupported or Off, consult Riot’s linked guide and your exact model’s official support. Switching UEFI/CSM immediately on Legacy/MBR can prevent Windows from booting.
- Ask the manufacturer if encryption, dual boot, disk layout or recovery is unclear. Do not convert disks or change storage mode based on a general article alone.
Step 3|Check memory integrity and running HVCI
Do this after the TPM and Secure Boot checks.
Time: Allow 3–5 min to check · Risk: low
- In Windows Security, open Device security and Core isolation to read memory integrity status.
- In msinfo32, check running VBS and Hypervisor enforced Code Integrity in its running services. A virtualization-enabled indicator alone is insufficient.
- For missing requirements, follow Riot’s memory integrity guide. Identify incompatible drivers and publishers, prioritize official vendor updates and do not manually delete .sys files.
Step 4|Restart and compare after necessary changes
Use model-specific official guidance, one change at a time.
Time: Allow 3–5 min to check · Risk: low
- Only make a necessary change after confirming the official procedure; restart afterward. Recheck TPM, UEFI, Secure Boot and HVCI readings, then launch VALORANT.
- If 9005 remains, send Riot the full message, model, Windows version, readings and actions. If it becomes RESTRICTION 5 or another number, check that guide’s scope.
- Prepare logs requested by official support without sharing recovery keys or unnecessary personal information.
Avoid
- Do not treat old advice to disable VBS or memory integrity as a general fix.
- Do not clear TPM, immediately switch Legacy to UEFI or experiment with storage mode.
- Do not bypass the error by stopping Vanguard or antivirus protection.
Important cautions
- Official sources checked on 2026-10-14; no in-game reproduction or verified repair is claimed.
- Do not assume this is exclusive to Windows 11. Use current official guidance and the full message.
FAQ
An older article told me to turn VBS off.
The current VAN9005 guidance checks TPM 2.0, Secure Boot and memory integrity. Prioritize current requirements and the actual message over an old workaround.
Is enabled TPM 2.0 sufficient?
Do not skip the remaining checks. Record UEFI, Secure Boot and working memory integrity; contact Riot if 9005 persists after all have been checked.
Sources
We checked these official pages and wrote the steps in our own words. Follow the publisher’s page if it has changed.
Riot: current VAN9005 checks (Japanese)Riot: TPM status and manufacturer guidanceRiot: UEFI and Secure Boot checksRiot: memory integrity and HVCI checks (Japanese)VALORANTJapanese version of this page