How to Enable Uefi Secure Boot for Valorant

How to Enable Uefi Secure Boot for Valorant

If Valorant suddenly stops launching and Vanguard asks for Secure Boot, don’t change random BIOS settings first. Start in Windows, check the current setup, then change only what’s needed. The key result is simple: BIOS Mode must say UEFI, and Secure Boot State must say On.

Check BIOS Mode and Secure Boot State in Windows

Check BIOS Mode and Secure Boot State in Windows

Windows can show you the two settings you need before you touch your computer’s firmware. This gives you a starting point and helps prevent unnecessary changes.

  1. Press Windows Key + R.
  2. Type `msinfo32`.
  3. Press Enter.

The System Information window will open. Find these two entries:

Write down what each one says before doing anything else. You can also take a photo of the screen with your phone.

For Valorant and Vanguard, the target setup is:

You may see one of several different combinations:

  • BIOS Mode says UEFI, while Secure Boot State says Off
  • BIOS Mode says Legacy, while Secure Boot State says Unsupported or Off
  • BIOS Mode says UEFI, and Secure Boot State already says On

That last combination means the two main settings are already correct. If Valorant still refuses to start, skip ahead to the troubleshooting section rather than changing firmware settings again.

The first two combinations need a closer look. In particular, don’t try to enable Secure Boot while the computer is still using Legacy or CSM mode. Change the boot mode to UEFI first.

Confirm whether your PC is using UEFI or Legacy/CSM

Confirm whether your PC is using UEFI or Legacy/CSM

The BIOS Mode line in System Information tells you how Windows started.

  • UEFI means the computer is already using the newer firmware boot mode.
  • Legacy means it is using the older boot method.
  • CSM may appear in your firmware settings as a compatibility mode that supports Legacy-style booting.

The wording can differ between Windows, a desktop motherboard, and a laptop. You may not see the word CSM in `msinfo32`, but you can still find it later in the firmware menu.

This check matters because Secure Boot is tied to UEFI. If your system is running in Legacy mode, simply turning on Secure Boot may not work. The correct order is:

  1. Check the current values in Windows.
  2. Open the firmware settings.
  3. Change Legacy or CSM to UEFI.
  4. Enable Secure Boot.
  5. Save the changes.
  6. Check the two Windows fields again.

Before restarting into firmware, record the original setting. If BIOS Mode says Legacy, note that down. If you see a boot option such as Legacy, CSM, or UEFI and Legacy, write down the exact choice. This gives you something to return to if Windows does not start normally after the change.

Enter your motherboard’s UEFI or BIOS settings

Enter your motherboard’s UEFI or BIOS settings

You need to change these options outside normal Windows settings. Depending on your computer, the firmware screen may be called UEFI, BIOS, or UEFI BIOS Utility. They all refer to the startup settings area you need.

You can enter it during startup, usually by pressing a key as the computer turns on. The exact key depends on the motherboard or computer maker, so watch the first screen for a message that tells you which key to press.

If you miss the timing, restart and try again. Some computers use a startup key, while others offer a Windows recovery route into firmware settings.

From Windows, you can also try this general path:

  1. Open Settings.
  2. Go to the recovery or advanced startup options.
  3. Restart into the computer’s advanced startup menu.
  4. Choose the option for entering UEFI Firmware Settings, if it appears.

The menu names can vary between Windows 10 and Windows 11. Don’t worry if your screen looks different from another guide. You’re looking for the firmware menu that contains boot settings and Secure Boot.

Before changing anything, pause and look at the current values. Firmware screens often include several options with similar names. Avoid changing storage, recovery, or security settings that are unrelated to boot mode.

Switch Boot Mode from Legacy or CSM to UEFI

Find a setting named something like:

  • Boot Mode
  • UEFI/Legacy Boot
  • Boot List Option
  • CSM Support
  • Legacy Support

The exact label depends on your motherboard. Your goal is to use UEFI, not Legacy or CSM.

If the menu has a direct choice, select:

  • UEFI

If it has a CSM option, you may need to disable CSM so the system uses UEFI booting. Some firmware menus show UEFI and Legacy as separate choices. Others hide the UEFI-only choices until CSM or Legacy support is turned off.

Make one change at a time, then look at the other options that appear. Some firmware menus reveal the Secure Boot setting only after the computer is set to UEFI mode.

This is the point where your original notes matter. If the computer does not start after saving the change, return to the firmware settings and restore the original Legacy or CSM choice. Don’t keep changing several settings at once, because that makes it hard to tell which change caused the problem.

Once the boot mode shows UEFI, find the Secure Boot setting.

Enable Secure Boot

Secure Boot may be listed under a Boot, Security, or Authentication tab. Look for a setting named Secure Boot or Secure Boot Control.

Set it to:

  • Enabled
  • On

The wording may be different, but the meaning is the same.

If Secure Boot is unavailable, greyed out, or missing, check the boot mode again. The computer may still be using Legacy or CSM. Some menus also place Secure Boot in a separate security section, so check the nearby tabs instead of assuming the feature is absent.

Don’t change other security options just to make the menu look different. The important sequence is still:

  • Set boot mode to UEFI
  • Turn off Legacy or CSM support if needed
  • Enable Secure Boot
  • Save the changes

If the firmware asks you to confirm the change, read the prompt before accepting it. This is another reason to keep a note or photo of your original configuration.

Save changes and verify Secure Boot in Windows

After changing the settings, save and exit the firmware menu. On some systems, F10 opens the Save and Exit command. Other computers may use a menu option or a different key.

Choose the option that saves your changes and restarts the computer. Let Windows start normally.

Now repeat the check:

  1. Press Windows Key + R.
  2. Type `msinfo32`.
  3. Press **Enter`.
  4. Check BIOS Mode and Secure Boot State.

You want to see:

  • BIOS Mode: `UEFI`
  • Secure Boot State: `On`

This second check is the part many quick guides skip. A setting that looked correct in firmware may not produce the result you expected after Windows starts. Windows is the final place to confirm what the operating system is actually using.

If BIOS Mode still says Legacy, return to the firmware settings and check the boot mode again. If BIOS Mode says UEFI but Secure Boot State says Off, go back and enable Secure Boot. Restart and check `msinfo32` once more.

For How to enable Secure Boot Windows 11, the process is the same: use `msinfo32`, enter UEFI settings, choose UEFI instead of Legacy or CSM, enable Secure Boot, then verify the two fields.

The same applies to How to enable Secure Boot Windows 10. The Settings screens may look different, but the firmware requirement and the Windows verification step are the same.

Troubleshoot Valorant when Secure Boot is already on

If Valorant still shows a Vanguard or Secure Boot message, don’t assume the setting failed. Recheck both fields in `msinfo32`.

Valorant may need both conditions:

  • BIOS Mode must be `UEFI`
  • Secure Boot State must be `On`

Secure Boot being on by itself may not be enough. For example, if you only checked the firmware screen but never confirmed BIOS Mode in Windows, you may still be dealing with a Legacy or compatibility-mode setup.

Use this quick check:

Windows fieldRequired result
BIOS ModeUEFI
Secure Boot StateOn

If both values are correct:

  1. Restart the computer once more.
  2. Open Valorant again.
  3. Read the Vanguard message carefully.
  4. Note whether it still specifically mentions Secure Boot or gives a different requirement.

If the message has changed, use the new message as your guide. Don’t keep switching Secure Boot on and off. That can make it harder to track the actual problem.

If either value is wrong, return to the firmware menu and review the boot mode and Secure Boot settings. Pay special attention to settings called Legacy Support, CSM, or Boot Mode. A motherboard can use different wording from the instructions you’re following.

If Windows does not start after changing from Legacy or CSM to UEFI, use the original configuration you recorded. Restore the previous boot mode, save, and restart. Then stop and review the firmware options before trying again.

What to check for Gigabyte and other motherboard menus

Gigabyte, ASUS, MSI, ASRock, Dell, HP, and other manufacturers may place these settings in different areas. The names may also change after you switch from a basic firmware screen to an advanced one.

On a Gigabyte board, for example, look through the Boot area for UEFI, CSM, or Secure Boot options. The exact labels can depend on the board and firmware version. Don’t rely on a menu position from someone else’s screenshot.

For any motherboard, search the screen for these terms:

  • UEFI
  • Legacy
  • CSM
  • Boot Mode
  • Secure Boot
  • Secure Boot Control

If you find CSM Support, check whether it is preventing the system from using UEFI-only booting. If you find a Boot Mode option, choose UEFI instead of Legacy. Then look again for Secure Boot.

The verification-first checklist is short:

  • Record the original boot configuration.
  • Open `msinfo32` in Windows.
  • Check BIOS Mode and Secure Boot State.
  • Change Legacy or CSM to UEFI first.
  • Turn Secure Boot on.
  • Save the firmware changes.
  • Open `msinfo32` again.
  • Confirm UEFI and On.

Save that checklist somewhere before you restart. If your screen uses different labels, share which BIOS or motherboard menu you found—the menu name can help show where the standard UEFI and Secure Boot steps differ.

DH

Written by Dennis Haymon

Dennis Haymon is a security professional and manager at Safe & Sound Security LLC. With experience in security guard and patrol services, he shares practical information about protecting homes, businesses, and properties. Through Safe & Sound Security LLC, Dennis and the team provide security-focused guidance designed to help individuals and businesses better understand their security needs and available protection options.