A VALORANT message saying “This build of Vanguard requires Secure Boot to be enabled” points to the security state Windows reports, not an ordinary game-file problem. Before reinstalling VALORANT, check whether Windows is running in UEFI mode and whether Secure Boot is actually on.
Firmware menus differ by motherboard and laptop model. The illustrations below show the settings to recognize; they are not a promise that your BIOS will have the same layout.
Read the exact Vanguard message
Record the error code and its wording. VAN 9003 concerns Secure Boot, while other Vanguard messages can identify TPM or additional requirements. Work on the requirement named in your message rather than changing every security setting at once.
Riot’s Secure Boot guide covers the firmware requirement and situations where the option is unavailable.
Check what Windows sees before opening the BIOS
Press Windows + R, enter msinfo32, and press Enter. In System Summary, find BIOS Mode and Secure Boot State. Write down both values.
| Windows reports | What it means for this repair |
|---|---|
| UEFI and Secure Boot On | The basic Secure Boot requirement appears satisfied; record any different Vanguard requirement |
| UEFI and Secure Boot Off | Investigate the firmware’s Secure Boot configuration |
| Legacy BIOS Mode | Check the Windows disk and UEFI support before changing boot mode |
| Secure Boot Unsupported | Investigate boot mode and firmware capabilities; this alone does not prove the PC must be replaced |
For the unsupported result, use Secure Boot State Unsupported to separate configuration problems from hardware limitations.
Confirm the Windows disk’s partition style
Right-click Start and open Disk Management. Identify the disk containing the Windows C: partition. Right-click its Disk 0, Disk 1, or equivalent label on the left, select Properties, and open Volumes. Check Partition style.
Do not assume the Windows disk is Disk 0, particularly on a PC with several drives.
GPT is the normal partition style for a Windows UEFI installation. If Windows already reports UEFI, you usually do not need a disk conversion for this error.
MBR with Legacy mode needs a more careful plan. Switching firmware to UEFI first can leave the existing Windows installation unable to boot. Microsoft’s MBR2GPT documentation describes supported conversion and validation requirements. Do not run a conversion command copied from a guide without confirming the correct disk, a restorable backup, UEFI support, and encryption requirements.
If you cannot verify those conditions, get model-specific assistance before changing boot mode. Formatting the drive is not a prerequisite for diagnosing Vanguard.
Prepare for a firmware change
Back up important files and locate the recovery key if BitLocker or Device Encryption is active. Firmware changes can trigger recovery. For a work-managed PC, ask IT to handle the settings.
Photograph the existing boot and security settings so you can identify what changed. Avoid altering AHCI, RAID, or VMD: storage-controller settings are not a Secure Boot fix and can prevent Windows from starting.
Enable Secure Boot in the model’s firmware
In Windows 11, open Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. If the firmware option is absent, use the manufacturer’s documented startup key rather than assuming your hardware lacks UEFI.
Find Secure Boot under a menu such as Boot or Security. Use the instructions for your exact model. If the Windows installation is ready for UEFI, the firmware may require disabling Legacy or CSM before Secure Boot becomes available.
Enable Secure Boot and use the manufacturer’s normal Windows configuration. If default Secure Boot keys must be installed, follow the model’s instructions; do not delete keys or switch into Custom mode at random. Dual-boot systems and manually managed keys require particular care.
Save the change, restart into Windows, and check msinfo32 again. The meaningful result is Secure Boot State: On, not simply a BIOS switch that appears enabled. If the two disagree, see Secure Boot enabled but not active.
Check TPM if Vanguard also asks for it
Press Windows + R, enter tpm.msc, and check the status and Specification Version. For TPM 2.0, look for “The TPM is ready for use” and version 2.0.
If Windows cannot find a compatible TPM, inspect the manufacturer’s TPM setting. It may be labeled Intel PTT, AMD fTPM, or TPM Security. Enabling the appropriate supported TPM is different from clearing it. Do not click Clear TPM as a routine Vanguard repair.
Only address additional features named in your error. If it specifically requires Memory Integrity, use Memory Integrity can’t be turned on rather than disabling Windows protections to make the game start.
Recheck Vanguard after a full restart
Restart the PC after changing firmware or installing Vanguard, then launch the game. If Windows now reports Secure Boot On and TPM 2.0 ready but the same error continues, note the exact code and check for Windows updates under Settings > Windows Update.
If needed, uninstall Riot Vanguard from Windows’ installed-apps settings, restart, and launch VALORANT to reinstall it. Restart again if prompted. Reinstallation can repair the service; it cannot enable Secure Boot in the firmware.
If a firmware change stops Windows from starting
Do not keep changing unrelated settings. If you changed boot mode without converting the installation, restore the previous boot mode. If you completed a disk conversion, the installation now needs the corresponding UEFI boot configuration; blindly reverting to Legacy may not help.
For a BitLocker recovery screen, use the correct recovery key or contact the organization managing the device. Do not clear the TPM to dismiss it. If you changed the storage-controller mode accidentally, restore its recorded original value.
When the security requirements are confirmed but Vanguard still refuses to start, give Riot support the error screenshot, msinfo32 values, TPM status, Windows version, and computer model. That evidence is more useful than repeating risky firmware changes or applying an unofficial Vanguard bypass.
