Site icon Google Maps Widget

How to Fix Valorant UEFI Secure Boot Error (Step-by-Step)

If you’ve tried launching Valorant recently and encountered the dreaded “This build of Vanguard requires TPM version 2.0 and Secure Boot to be enabled in order to play” message, you’re not alone. This error can be frustrating, especially when you’re eager to jump into a few competitive rounds. Fortunately, fixing the Valorant UEFI Secure Boot error isn’t as complicated as it may initially seem. This guide will walk you through the process step-by-step—no advanced tech knowledge required!

Why Does Valorant Require Secure Boot?

Valorant’s anti-cheat system, Vanguard, operates on a kernel level, meaning it interacts closely with your system’s firmware. To ensure integrity and prevent cheating, Vanguard mandates that Secure Boot and TPM 2.0 be enabled in your PC’s BIOS/UEFI settings. This helps prevent malicious software from loading before your operating system does and is also part of Microsoft’s requirements for Windows 11.

Step-by-Step Guide to Fix the Valorant Secure Boot Error

Resolving this issue involves enabling Secure Boot and TPM 2.0 from your PC’s UEFI BIOS. Follow these steps carefully to fix the problem:

Step 1: Check Your Secure Boot and TPM Status

  1. Press Windows + R to open the Run dialog.
  2. Type msinfo32 and press Enter.
  3. In the System Information window, look for:
    • Secure Boot State: Should say On.
    • TPM Version: Check under Security Device Support. If it says 2.0, you’re good to go.
  4. If Secure Boot is Off or not supported, proceed with the steps below.

Step 2: Access Your UEFI BIOS

  1. Click on the Start Menu and select Settings.
  2. Go to System > Recovery.
  3. Under Recovery Options, click Restart now next to “Advanced startup”.
  4. Once your PC restarts, go to Troubleshoot > Advanced options > UEFI Firmware Settings.
  5. Click Restart and your PC will enter BIOS/UEFI.

Step 3: Enable TPM 2.0

In the BIOS/UEFI menu, use your keyboard to navigate (mouse support may be limited):

Note: TPM 2.0 is usually available on most modern computers. If your PC is older, make sure your motherboard supports it and that the feature is not locked.

Step 4: Enable Secure Boot

Important: Enabling Secure Boot from Legacy (CSM) mode may require converting your drive from MBR to GPT. You can do this non-destructively using the mbr2gpt tool available in Windows.

Step 5: Save and Exit BIOS

  1. Press the designated key (usually F10) to Save and Exit.
  2. Confirm changes if prompted and allow your system to reboot.

Step 6: Reboot and Try Launching Valorant

Once your system boots back into Windows, try launching Valorant. If both TPM 2.0 and Secure Boot were properly enabled, the error should now be gone. Vanguard will load correctly, and you’ll be back to competing in no time.

What If You Still See the Error?

If you’ve enabled Secure Boot and TPM 2.0 but still see the error, try the following:

How to Convert MBR to GPT (If Needed)

If Secure Boot remains greyed out due to your system using MBR (Master Boot Record) rather than GPT (GUID Partition Table), you can convert it safely:

  1. Open Command Prompt as Administrator.
  2. Type the following command and press Enter:
    mbr2gpt /convert /allowfullOS
  3. Once complete, reboot into BIOS and switch from Legacy to UEFI.

Be sure to back up your important data before doing this—even though the tool is safe, mistakes can happen.

Other Tips and Considerations

Conclusion

While the Valorant UEFI Secure Boot error may seem like a technical hurdle, following the right steps ensures a smooth fix. Enabling Secure Boot and TPM 2.0 enhances your computer’s security while allowing Vanguard to function as intended. By understanding your system’s firmware settings and how to configure them, you’ll not only get back into your game but also be better prepared for other modern PC software requirements.

So the next time Valorant refuses to launch, don’t panic. Grab this guide, follow it step-by-step, and you’ll be back to climbing the ranks in no time.

Exit mobile version