VALORANT VAN Error Checklist: Match the Code Before Changing Windows

Preparing the interactive tool. Please wait; the guide and worked examples remain available below.

Browser-local error router

Vanguard error code triage

Choose the exact prefix and code shown by Riot Client; use the matching Riot support article before changing a Windows security setting.

Exact message

Source-bounded next step

Riot's current article maps VAN 9001 to Vanguard not detecting TPM 2.0 as enabled. Read the TPM status first; do not change firmware until you identify your PC or motherboard model and follow its official instructions.

This page only routes your selection. It cannot read Windows, TPM, Secure Boot, VBS, Vanguard, your Riot account or error logs.

Route the exact error, not a guessed cause

Riot's Vanguard index is the current source of truth for code-specific routes. A similar-looking number can describe a different requirement, and Riot explicitly separates VAN-prefixed Vanguard messages from VAL client messages.

Code shown	Riot's documented direction	First safe check
VAN 9001	TPM 2.0 not detected as enabled	Check tpm.msc, then identify PC/motherboard model before firmware steps
VAN 9002	Exploit Protection settings	Check Riot's exact System and Program Settings steps; record custom values
VAN 9003	Secure Boot not enabled/detected	Read BIOS Mode and Secure Boot State in msinfo32
VAN 9005	TPM 2.0, Secure Boot, Memory Integrity/VBS	Verify each in Riot's stated order; restart after applicable changes
VAN 9006	Supported Windows version not detected	Check Windows version/update state, then use Riot's linked article
VAL code or other VAN code	Different error route	Use Riot's live index and matching article; do not substitute a similar code

References: Riot Support: Vanguard Error Codes · Riot Support: Error VAN 9001 · Riot Support: Error VAN 9003 · Riot Support: Error VAN 9005 · Riot Support: Error VAN 9002 · Riot Support: Error VAN 9006

Keep firmware changes as a separate, deliberate step

Riot's Secure Boot guide says the check is hardware-specific and warns that incorrect BIOS/UEFI changes may cause system problems. Start with read-only checks. If Windows reports Legacy mode or an MBR system disk, do not simply switch firmware to UEFI; follow the exact computer maker and Microsoft instructions and confirm backup/encryption recovery first.

Write down the complete error string, whether it starts with VAN or VAL, Windows edition/build, and when it began. Never include passwords or account recovery codes in a public post.
For TPM, open tpm.msc and record whether it is ready, disabled, or unavailable. The browser tool does not read this window.
For Secure Boot, open System Information (msinfo32) and note BIOS Mode and Secure Boot State. In Disk Management, inspect the Windows disk's partition style without changing it.
For VAN 9002, use the Riot article and note any custom Exploit Protection values before considering edits. Apply only the named Riot-related procedure if it fits your configuration.
Before any firmware or partition action, locate your PC/motherboard manufacturer's current guide and confirm important data is backed up and any BitLocker/device-encryption recovery key is safely available.
After following the exact applicable official steps, restart and check the same error. If the security states already meet Riot's article, submit a Riot support ticket with requested, redacted logs rather than repeatedly toggling firmware.

References: Riot Support: Secure Boot Guide · Microsoft Support: Windows and Secure Boot · Riot Support: Vanguard Error Codes

Discussion scope

The player forum link is provided for comparing similar symptoms, not to replace Riot's current error pages. Firmware menus and security policies differ by motherboard, Windows configuration and organization; an anecdotal fix may not apply to your device.

References: r/VALORANT player discussions · Riot Support: Vanguard Error Codes

Before you play

I copied the exact VAN or VAL prefix and code.
I started with read-only checks and matched the official article for that code.
I identified my exact PC/motherboard before any firmware changes.
I confirmed backup and encryption recovery details before touching boot or partition settings.
I did not share passwords, recovery keys or unredacted support logs.

Frequently asked questions

Can I enable Secure Boot by switching Legacy to UEFI immediately?

No. Riot's guide discusses UEFI/GPT prerequisites, but the correct path depends on how Windows is installed and on the exact hardware. Inspect first, back up, confirm encryption recovery, and use manufacturer/Microsoft steps.

Does VAN 9005 mean I should turn on every virtualization feature?

Riot's article specifies TPM 2.0, Secure Boot and Memory Integrity/VBS checks for that code. Do not broadly change unrelated virtualization settings; follow the current code-specific article.

Can the checker tell which security setting is off?

No. It routes the code you choose to a source-bounded checklist; it cannot read Windows, BIOS, TPM, Secure Boot, VBS or Vanguard.

Sources & revision notes

Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

Riot Support: Vanguard Error Codes (Official)
Riot's live index separates VAN Vanguard errors from VAL client errors and routes individual codes to specific support articles. Check this page again because entries and requirements can change.
Riot Support: Error VAN 9001 (Official)
Riot says VAN 9001 means Vanguard currently requires TPM 2.0 but does not detect it enabled. Its linked TPM procedure warns BIOS/UEFI menus vary by hardware; follow the PC or motherboard maker's official instructions.
Riot Support: Error VAN 9002 (Official)
Riot identifies Windows Exploit Protection settings and Riot-specific program entries, then requests a restart. Record non-default settings before editing them; a custom configuration may be intentional or managed by an organization.
Riot Support: Error VAN 9003 (Official)
Riot says VAN 9003 means Secure Boot is not enabled/detected. The related Secure Boot guide discusses UEFI/GPT prerequisites and warns that firmware changes can cause system problems; do not treat this summary as device-specific BIOS instructions.
Riot Support: Error VAN 9005 (Official)
Riot's issue-specific sequence is TPM 2.0, Secure Boot, and Memory Integrity/VBS, then restart; if the message persists with those configured, contact support with logs. This is not a universal Windows security optimization checklist.
Riot Support: Error VAN 9006 (Official)
Riot maps VAN 9006 to Windows 10 20H1 or newer not being detected and directs users to install available Windows updates and restart. Check Riot's current notice because support requirements can change.
Riot Support: Secure Boot Guide (Official)
Riot's current walkthrough uses msinfo32, Windows disk partition style and manufacturer-specific BIOS/UEFI steps; it warns incorrect changes can cause system issues and that Secure Boot key reset can trigger BitLocker recovery. This guide deliberately stops short of generic conversion or firmware instructions.
Microsoft Support: Windows and Secure Boot (Official)
Microsoft's Windows Secure Boot reference. Firmware interface and encryption implications remain device-specific; use the PC maker's instructions and recovery-key process before changing firmware.
r/VALORANT player discussions (Community)
External player-authored discussion, not Riot support or verified GamerWin advice. Match Windows version and exact VAN/VAL code; do not post Riot login details, recovery keys, serial numbers, or unredacted logs.

What changed in this revision

November 7, 2026: first publication, reorganized Riot's distinct current code pages into a non-destructive decision path. No Vanguard error, Windows installation, firmware setting or game launch was reproduced.

How we research and correct guides

No affiliate links or paid placement. Commercial disclosure.