VALORANT articles ↗
WALKER BEX›VALORANT›VAN 9001 · GIGABYTE
VALORANT · GIGABYTE GUIDE

VAN 9001 Gigabyte Secure Boot Fix

A safe motherboard-specific checklist—without changing the wrong setting or losing Windows boot.

Walker Bex Guides••7 min read
ON THIS PAGE

The quick answer

VAN 9001 points to TPM first. Then verify Secure Boot.

Riot currently describes VAN 9001 as a TPM 2.0 detection problem; Secure Boot has a related but separate code, VAN 9003. On a Gigabyte PC, check tpm.msc for TPM 2.0, then msinfo32 for UEFI and Secure Boot. Only change firmware settings after confirming the exact motherboard model and a UEFI/GPT boot setup.

Jump into the guide

01 First: VAN 9001 is not the same as VAN 9003

These codes appear together in older search results, but Riot’s current documentation treats them separately: VAN 9001 means TPM 2.0 is not detected as enabled; VAN 9003 is the Secure Boot error. If your message mentions Secure Boot specifically, follow that requirement as well—but do not overlook TPM.

VAN 9001Start with the TPM version and readiness check.
VAN 9003Check Secure Boot State and UEFI compatibility.
VAN 9005Includes TPM, UEFI/Secure Boot and Memory Integrity/VBS checks.

02 Check Windows before opening Gigabyte BIOS

  1. Confirm the motherboard model

    Press Win + R, enter msinfo32, and note BaseBoard Manufacturer and BaseBoard Product. “Gigabyte” alone is not enough to identify the firmware menu.

  2. Check the TPM

    Press Win + R, enter tpm.msc. You want a ready TPM and Specification Version 2.0.

  3. Check BIOS mode and Secure Boot

    In msinfo32, note BIOS Mode and Secure Boot State. If they already read UEFI and On, do not change them.

  4. Check the system disk partition style

    Open Disk Management, open properties for the Windows system disk, and inspect the Volumes → Partition style field if available. A supported Secure Boot configuration typically boots Windows via UEFI using GPT.

03 Gigabyte settings: the safe path

  1. Back up and prepare

    Keep important files backed up and have your BitLocker or Device Encryption recovery key accessible. If BIOS Mode says Legacy or the Windows disk is MBR, stop here and seek help converting safely.

  2. Use the official manual for your model

    Restart and enter firmware setup (many Gigabyte desktop boards use Delete during startup). Switch to Advanced Mode if needed. Layouts differ by generation.

  3. Enable the firmware TPM when needed

    On supported Gigabyte AMD systems the menu can be Settings → AMD CPU fTPM. On supported Intel systems, it may be named Intel PTT. Enable only the option that matches your CPU and manual.

  4. Check Secure Boot only on UEFI/GPT

    Gigabyte’s documented AM4 path commonly uses Boot → CSM Support → Disabled before Secure Boot becomes available. Follow this only if Windows is already UEFI/GPT and your exact motherboard supports it.

  5. Save, restart and verify

    Return to Windows. Recheck TPM readiness with tpm.msc and UEFI/Secure Boot status with msinfo32. Then test VALORANT.

Very important: Enabling Secure Boot, disabling CSM, or changing factory keys can prevent Windows from booting or trigger drive-encryption recovery. If the Windows installation is Legacy/MBR, use a qualified technician or official conversion guide first.

04 Secure Boot appears disabled or hidden?

Some Gigabyte AM4 BIOS versions hide Secure Boot when CSM Support is enabled. Gigabyte’s published AM4 instructions also discuss installing factory Secure Boot keys when the system is in setup mode. This is an advanced, model-dependent operation, not an automatic fix for VAN 9001.

  • If the TPM is already 2.0 and ready, stop toggling TPM and check Riot’s exact code message.
  • If Secure Boot is On, do not reset the Secure Boot keys.
  • If “Secure Boot State” shows Unsupported or BIOS Mode is Legacy, do not force UEFI settings.
  • If you are asked to restore factory keys, first verify drive encryption recovery access and follow the exact Gigabyte manual for your motherboard revision.
  • If firmware menus differ from an online screenshot, do not improvise or flash a random BIOS file.

05 What if the code still appears?

TPM not foundCheck CPU support, Gigabyte BIOS model/revision, and the official TPM guide.
TPM ready, Secure Boot OffCheck whether the actual error also specifies Secure Boot; use Gigabyte’s model guide if UEFI/GPT is already verified.
Everything shows enabledRestart once and report the exact code, system details, and screenshots to Riot Player Support.
Windows won’t start after firmware changeReturn firmware to its previous known-good setting with qualified help; do not keep experimenting.

06 Frequently asked questions

Is VAN 9001 a Secure Boot error?

Riot’s February 2026 VAN 9001 guide primarily identifies TPM 2.0 detection. The dedicated Secure Boot error is VAN 9003; both requirements may matter depending on what the game reports.

Where is Secure Boot on Gigabyte motherboards?

Menu locations vary. Gigabyte documents Boot → CSM Support and Boot → Secure Boot on some AM4 models; consult your exact board and revision.

Should I disable CSM to play VALORANT?

Only if your Windows installation is already prepared for UEFI/GPT and official model instructions call for it. Forcing this can prevent startup.

Can I clear TPM to fix VAN 9001?

Do not clear TPM as a guess; doing so can affect encryption and protected credentials. Diagnose readiness first.

07 Sources & update notes

This article is written independently for Walker Bex. Support guidance checked October 10, 2026. Riot and motherboard instructions can change; verify the source before making firmware changes.