VALORANT Secure Boot and TPM Preflight: Check Before Entering UEFI

Read the system state before changing it

Riot's Secure Boot guide describes the UEFI and GPT prerequisites and the possible Legacy/MBR branch, but its menu steps cannot be generalized across vendors. This guide deliberately stops at a decision checklist: a working machine's boot path and encryption state should be confirmed before changes.

References: Riot Support: Secure Boot Guide · Microsoft Support: Windows and Secure Boot

Collect these checks

Use these read-only checks to gather the values the worksheet asks for. Stop before changing firmware, disks or encryption.

1. Record the exact Riot code and Windows version.
2. Press Windows+R, enter msinfo32, and note BIOS Mode and Secure Boot State; close the window without changing anything.
3. In Disk Management, inspect the Windows disk's Properties > Volumes > Partition style. Do not initialize, format, convert or alter partitions.
4. Press Windows+R, enter tpm.msc, and record the displayed TPM status/version.
5. Confirm you can access your important-file backup and the correct BitLocker/device-encryption recovery key through your own Microsoft or organization process.
6. Only if the status matches the applicable Riot article, follow the official PC/motherboard maker's exact instructions. Restart and re-check the Windows status before launching the game.

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

Why this tool stops instead of fixing BIOS

A browser page cannot determine whether a device uses custom boot settings, disk encryption, dual boot, managed security policy or vendor-specific firmware. Treat Legacy/MBR and unknown values as a stop-and-research state, not as permission to run a conversion command.

References: Riot Support: Secure Boot Guide · Microsoft Support: Windows and Secure Boot · r/VALORANT player discussions

Before you play

• I checked BIOS Mode and Secure Boot State in msinfo32 without changing settings.
• I checked the Windows disk partition style without altering partitions.
• I checked TPM status in tpm.msc.
• I have a current backup and can retrieve the correct recovery key before firmware changes.
• I will use my PC/motherboard maker's official instructions and the exact Riot code page.

Frequently asked questions

Sources & revision notes

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

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.