How do you enable SEcure boot for Valorant? If you’ve run into the “Vanguard requires Secure Boot to be enabled” message, or you’ve seen your game refuse to launch, you’re not alone. The short answer: you need to dive into your computer’s BIOS or UEFI settings, switch to UEFI boot mode if you haven’t already, and enable Secure Boot. For many Valorant players, this is a sudden and occasionally intimidating requirement, but as you’ll see, it’s a lot more approachable than it first appears. Let’s break it down together so you can get back to clutching rounds in no time.
Why Secure Boot Is Required for Valorant
Valorant’s anti-cheat system, Riot Vanguard, takes fair play seriously. Part of that mission? Ensuring players can’t tamper with core system files during bootup. Secure Boot is a feature built into modern PCs that only allows booting trusted, digitally-signed software. If you’ve just upgraded to Windows 11, or you’re seeing a warning related to Secure Boot, this is Riot’s way of making sure no one gets an unfair edge—and that everyone’s system is as safe as possible from rootkits and similar threats.
Quick Check: Is Secure Boot On or Off?
Before you dive into the BIOS, pause for a second and check if Secure Boot might already be enabled:
- Press Windows key + R, type msinfo32, and press Enter.
- In the System Information window, look for the line that says Secure Boot State. If it says “On,” you’re good! If it says “Off” or “Unsupported,” you’ll need to take action.
Navigating to BIOS/UEFI: Where the Magic Happens
Okay, so Secure Boot is off. Time to roll up your sleeves and reboot into the BIOS (or UEFI) firmware menu. Sounds technical? Relax. Think of it as the cockpit of your computer—the where you steer how your system wakes up and runs.
- Start by restarting your PC.
- As soon as your system begins to power back on, start tapping F2, F10, F12, DEL, or ESC—the exact key varies by manufacturer (your screen may even flash the “Press F2 for setup” tip at boot).
- For Windows 11: You can also get to UEFI via Settings > System > Recovery > Restart Now under Advanced Startup. Then choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart.
Lost? Here’s a useful written walkthrough if step-by-step text is your thing.
Step-By-Step: Enabling Secure Boot in BIOS/UEFI
Every motherboard’s layout is different, but the basics remain surprisingly consistent:
- Switch to UEFI Boot Mode if you haven’t already. Secure Boot only works with UEFI, not “legacy” BIOS/CSM boot. Find the Boot tab or Boot Configuration and set the Boot Mode to UEFI.
- Jump to the Secure Boot menu. This is usually under “Boot,” “Security,” or “Authentication.”
- Set Secure Boot to Enabled.
- Optional but recommended: If you see an option for “Restore Factory Keys” or “Install Default Secure Boot Keys,” use it. It guarantees you’re using Microsoft’s standard certificates.
- Press F10 to Save and Exit. Your PC will restart.
If you get stuck, don’t sweat it—most manufacturer websites (like ASUS, Dell, HP, etc.) offer guides. Players on custom PCs and older hardware should pay special attention to the UEFI mode—sometimes a drive reformat is needed if you’re still on a legacy setup, but most modern machines are ready for UEFI with a simple toggle.
Brand-Specific Tips
- ASUS: Boot > Secure Boot > OS Type – set to “Windows UEFI mode”
- Dell: Boot Configuration > Boot Sequence – ensure UEFI, then enable Secure Boot
- HP: System Configuration > Boot Options – tick Secure Boot
- Always save changes (usually F10), or they won’t stick!
For even more step-by-step visuals, here’s a direct link to TurboSmurfs’ Secure Boot guide which covers multiple motherboard brands.
Don’t Forget TPM 2.0 (It’s Also Required!)
Along with Secure Boot, Valorant and Windows 11 both insist on TPM 2.0—another security feature. TPM is a security chip, either built into your motherboard or CPU. Most modern systems have it. Look for the “Trusted Platform Module” or “Security Device” section in your BIOS and make sure it’s set to Enabled as well.
Enabling both Secure Boot and TPM 2.0 guarantees that Vanguard can protect the game at a low system level. Need extra help combining both? Here’s a comprehensive video:
After Enabling Secure Boot: What’s Next?
Once you’ve saved changes and rebooted, it’s a good moment to double-check everything:
- Open System Information (msinfo32) and confirm Secure Boot State says “On.”
- If you still see game errors, check TPM 2.0 is Present and Enabled. (Sometimes called PTT, fTPM, AMD PSP, or Intel Platform Trust Technology in BIOS.)
- Now try launching Valorant. Most “Vanguard requires Secure Boot to be enabled” issues end here.
Still stuck? You might need a deeper dive into Riot’s official support article or consider updating your BIOS firmware if Secure Boot options don’t appear at all.
Common Pitfalls and Troubleshooting
- No Secure Boot option? BIOS update might be required, especially on older hardware.
- Secure Boot grayed out? Make sure you’ve switched to UEFI Boot Mode first. Legacy/CSM disables Secure Boot controls entirely.
- Drive not booting after UEFI switch? Your Windows installation may be in legacy MBR mode. You might need to convert your drive to GPT using built-in tools (Microsoft MBR2GPT guide), but always back up critical files first.
Extra Resources for Visual Learners
- TurboSmurfs: Secure Boot for Valorant
- Eloboss: How to Enable Secure Boot
- Riot Games: Vanguard Restrictions
- THESPIKE.gg: Secure Boot Tips
FAQ: Your Secure Boot & Valorant Questions Answered
What’s actually the purpose of Secure Boot when playing Valorant?
Secure Boot helps block malicious or unauthorized software during Windows startup. For Valorant, Vanguard leverages it to make sure no cheats or rootkits sneak in before the anti-cheat loads. It’s not just for Riot’s peace of mind—the feature truly enhances your system’s protection as well.
Do I really need to enable TPM 2.0, or is Secure Boot enough?
Both are required for Windows 11 users. TPM 2.0 and Secure Boot work together to meet Microsoft’s security baseline, and Vanguard uses both for maximum cheat prevention. Not enabling TPM 2.0 means you’ll likely continue to get error messages or be locked out from the game.
Will enabling Secure Boot delete any of my files?
No, changing Secure Boot status does not affect your personal files or installed games. That said, switching from legacy BIOS to UEFI mode may require drive conversion on older systems, so always back up your important documents first if you’re prompted to “convert MBR to GPT.”
What if my PC doesn’t have Secure Boot options at all?
This sometimes happens on legacy hardware, rare laptops, or custom PCs built with older motherboards. Check if a BIOS update is available from your manufacturer’s website. If your system only supports legacy BIOS, unfortunately, Secure Boot isn’t possible—and Valorant on Windows 11 may not work until you upgrade your hardware.
Does Secure Boot impact gaming performance or FPS?
Not in any measurable way. Secure Boot applies only during the system startup sequence. Once Windows is running and you’re in-game, you’ll see zero difference in FPS or performance by virtue of having Secure Boot toggled on or off.
I still get Secure Boot errors on startup or in Valorant. Now what?
Start by revisiting the BIOS to confirm settings were saved, and that both UEFI Boot Mode and Secure Boot show as enabled. Double-check that TPM 2.0 is on. If issues persist, consult the official Riot support guide and consider reaching out to your motherboard maker’s support team for specific troubleshooting, especially if options are missing or grayed out.
Your Next Steps: Secure Boot, No Sweat
At the end of the day, enabling Secure Boot for Valorant is something every modern PC owner can handle, even if you’ve never poked around your BIOS before. It’s a one-time fix that opens the gates to competitive Valorant play—and brings your setup up to industry security standards. Curious for more? Scan through the official articles, community tutorials, and the video guides embedded above for additional walkthroughs tailored to your hardware. Good luck, agent—see you in the server!