UEFI Secure Boot Valorant guide showing how to fix Vanguard Secure Boot errors and launch Valorant without VAN 9003 issues in 2026.
UEFI Secure Boot Valorant errors usually appear when Riot Vanguard detects that your Windows system does not meet Valorant’s security requirements. In most cases, the problem is connected to Secure Boot, TPM 2.0, BIOS Mode, outdated BIOS firmware, or incorrect Secure Boot keys.
Valorant uses Riot Vanguard as its anti-cheat system. On Windows 11 especially, Vanguard may require features such as TPM 2.0 and Secure Boot to be enabled before the game can launch properly. Riot’s own support pages list Vanguard restriction errors such as VAN 9001, VAN 9003, VAN 9090, VAN 9005, and Secure Boot policy-related issues.
This UEFI Secure Boot Valorant guide explains what UEFI Secure Boot means, why Valorant needs it, and how to fix Vanguard Secure Boot errors safely in 2026.
UEFI Secure Boot Valorant errors occur when Riot Vanguard detects that Secure Boot, TPM 2.0, UEFI mode, or related Windows security requirements are not configured correctly.
To fix UEFI Secure Boot Valorant errors, check msinfo32 and confirm:
If Secure Boot is disabled, enter BIOS/UEFI settings, disable CSM/Legacy Boot, enable Secure Boot, enable TPM 2.0, save changes, restart Windows, and relaunch Valorant.
This guide is useful if:
If any of these situations apply to your PC, the troubleshooting steps in this guide can help identify the cause and walk you through the most effective solutions.
People searching for UEFI Secure Boot Valorant are usually experiencing a Vanguard error that prevents the game from launching. Most users want a fast solution for errors such as VAN 9001, VAN 9003, VAN 9090, VAN 9005, or Secure Boot policy issues.
The search intent is mainly informational and troubleshooting-focused. Users usually want to know why Valorant requires Secure Boot, how Riot Vanguard checks system security, how to enable Secure Boot and TPM 2.0, how to fix VAN errors, whether Secure Boot is safe, whether Valorant can run without Secure Boot, and how to fix BIOS or UEFI configuration problems.
This guide covers all of these topics and provides step-by-step solutions for Windows 10 and Windows 11 users.
| Topic | Status | Details |
| Valorant uses Riot Vanguard | Confirmed | Riot uses Vanguard as Valorant’s anti-cheat system. |
| Secure Boot may be required | Confirmed | Vanguard may require Secure Boot on supported systems. |
| TPM 2.0 may be required | Confirmed | Windows 11 systems may require TPM 2.0 for Vanguard security checks. |
| VAN 9003 is linked to Secure Boot | Confirmed | VAN 9003 is commonly connected to Secure Boot not being enabled correctly. |
| Secure Boot bypass tools are safe | Not Confirmed | These tools can create security risks and may violate game rules. |
| Every PC requires Secure Boot | Not Always | Requirements can vary by operating system, hardware, and configuration. |
This distinction helps separate verified information from common online myths.
UEFI Secure Boot is a firmware security feature that helps Windows start only with trusted boot software. Microsoft explains that Secure Boot works through UEFI firmware and verifies trusted software during the boot process.
For Valorant, Secure Boot matters because Riot Vanguard uses system-level security checks to reduce cheating and unauthorized system manipulation. If your PC is running in Legacy BIOS mode, has Secure Boot disabled, or has missing Secure Boot keys, Vanguard may block the game from launching.
The purpose of Secure Boot is to help prevent unauthorized drivers, bootloaders, and low-level software from loading before Windows starts. This adds layer of protection against certain types of malware and system modifications that could compromise security or game integrity. Because Riot Vanguard operates at a deep system level, it relies on trusted startup processes to verify that the operating system has not been tampered with before Valorant launches.
Understanding UEFI Secure Boot Valorant requirements is important because many Vanguard restriction errors are caused by BIOS configuration issues rather than problems with the game itself. Ensuring that UEFI mode, Secure Boot, and TPM 2.0 are configured correctly can help prevent launch errors and improve overall system security.
Riot Vanguard uses Secure Boot as part of its anti-cheat security model. Secure Boot helps ensure that Windows starts using trusted boot components and reduces the risk of low-level software manipulation during the startup process.
Because some cheats attempt to load before Windows fully starts, Secure Boot provides Vanguard with an additional layer of system verification. By validating trusted boot files and firmware settings, Vanguard can better detect systems that do not meet its security requirements.
This approach helps protect competitive integrity by making it more difficult for unauthorized software to interfere with the operating system before Valorant launches.
As modern cheats become more sophisticated, security technologies such as UEFI, TPM 2.0, and Secure Boot have become increasingly important. This is one reason Secure Boot plays a larger role in Riot Vanguard’s security framework, particularly on newer Windows systems. Understanding UEFI Secure Boot Valorant requirements can help players identify configuration issues that may trigger Vanguard security restrictions or launch errors.
It is important to note that Secure Boot is not designed specifically for Valorant. It is a standard security feature built into modern PCs that helps protect the Windows boot process from untrusted software and certain types of malware.
Many players assume Valorant itself is causing the error, but in most cases the problem is related to Windows security settings, BIOS configuration, or TPM requirements. Checking Secure Boot status, TPM 2.0 status, and BIOS mode before making major system changes can save significant troubleshooting time.
Valorant may show a Vanguard Secure Boot error when:
Before changing anything in BIOS, always check your current system status using msinfo32 and tpm.msc.
| Feature | Windows 10 | Windows 11 |
| Secure Boot Support | Recommended | Often required for Vanguard checks |
| TPM 2.0 | Optional on some systems | Frequently required |
| Vanguard Security Checks | Active | Usually stricter |
| UEFI Requirement | Recommended | Strongly recommended |
| Common Error Risk | Lower on older setups | Higher if Secure Boot or TPM is disabled |
Many players encounter Secure Boot issues after upgrading from Windows 10 to Windows 11 because Vanguard security checks can be stricter on newer systems. If Valorant worked before but stopped after a Windows upgrade, check Secure Boot, TPM 2.0, and BIOS Mode first.
Common Meaning: TPM or Secure Boot requirement issue.
Main Fix: Enable TPM 2.0 and Secure Boot in BIOS.
Common Meaning: Secure Boot is not enabled.
Main Fix: Enable Secure Boot in BIOS and verify that UEFI mode is active.
Common Meaning: Vanguard security restriction.
Main Fix: Check TPM 2.0, UEFI mode, and Secure Boot configuration.
Common Meaning: The system does not meet Vanguard security requirements.
Main Fix: Update BIOS firmware and enable the required security settings.
Common Meaning: Secure Boot policy or configuration issue.
Main Fix: Reset or load the default Secure Boot keys.
The following table provides a more detailed explanation of the most common Riot Vanguard security errors associated with UEFI Secure Boot Valorant issues.
| Error Code | Meaning | Usually Caused By |
| VAN 9001 | Security requirement failure | TPM 2.0 or Secure Boot is disabled |
| VAN 9003 | Secure Boot issue | Secure Boot is disabled or misconfigured |
| VAN 9090 | Vanguard restriction | Security settings do not meet Vanguard requirements |
| VAN 9005 | System security failure | TPM, BIOS, firmware, or security configuration issue |
| STATUS_SB_POLICY | Secure Boot policy problem | Missing, corrupted, or incorrect Secure Boot keys |
While these errors can appear for different reasons depending on your hardware and Windows configuration, they are most commonly linked to Secure Boot, TPM 2.0, UEFI mode, BIOS settings, or Riot Vanguard security checks. Identifying the exact error code can help you apply the correct fix more quickly.
Before changing BIOS settings, check your current system status.
Your result should ideally show:
| Setting | Correct Value |
| BIOS Mode | UEFI |
| Secure Boot State | On |
If BIOS Mode is Legacy, Secure Boot may not work correctly. If the Secure Boot state is off, you need to enable it from the BIOS/UEFI settings.
A common situation occurs after a Windows 11 upgrade. A player discovers that Valorant suddenly displays VAN 9003 even though the game worked previously. In many cases, the upgrade did not cause the issue directly. Instead, a BIOS update, firmware reset, or TPM setting change disabled Secure Boot, causing Riot Vanguard to block the game until the required security settings were restored.
Before changing BIOS settings, restart your PC. Sometimes, Vanguard does not load properly after a Windows update, Riot Client update, or failed system startup.
After restarting:
If the same Vanguard error appears again, continue with the next steps.
TPM 2.0 is another security feature often required with Secure Boot. Riot’s Vanguard restriction guidance includes TPM-related checks for supported systems.
To check TPM:
If TPM is disabled, enable it from BIOS. Depending on your motherboard, TPM may appear as:
| Brand/Platform | TPM Name in BIOS |
| Intel | PTT |
| AMD | fTPM |
| General BIOS | TPM Device or Security Device Support |
Enable it, save changes, and restart your PC.
Secure Boot works with UEFI firmware. If your system is running in Legacy BIOS mode, Valorant may keep showing Vanguard Secure Boot errors.
To check:
If it says UEFI, you can move to Secure Boot settings.
If it says Legacy, be careful. Switching from Legacy to UEFI may require converting your system disk from MBR to GPT. Do not randomly change this setting unless you understand your disk setup or have a backup.
Many users discover that Secure Boot cannot be enabled because Windows was originally installed in legacy BIOS mode using an MBR partition. This is a common issue behind certain UEFI Secure Boot Valorant errors, especially when Vanguard requires both UEFI mode and Secure Boot to be active.
Before changing the BIOS mode from Legacy to UEFI:
mbr2gpt /validate
mbr2gpt /convert
Important: Do not continue if validation fails. Fix the disk issue first or ask a technician for help. Changing boot mode incorrectly can stop Windows from booting.
Many BIOS menus have a setting called CSM or Compatibility Support Module. If CSM is enabled, Secure Boot may stay unavailable or show as disabled in Windows.
Common BIOS path:
BIOS > Boot > CSM > Disable
After disabling CSM:
Microsoft’s support page explains that Secure Boot can be enabled through Advanced Startup and UEFI firmware settings.
The Secure Boot option is usually under:
| Brand | Common Secure Boot Location |
| ASUS | Boot → Secure Boot |
| MSI | Settings → Advanced → Secure Boot |
| Gigabyte | BIOS Features → Secure Boot |
| ASRock | Security → Secure Boot |
| Dell | Secure Boot Configuration |
| HP | Security → Secure Boot |
| Lenovo | Security → Secure Boot |
This helps users locate the correct setting more quickly because BIOS layouts vary between manufacturers.
If Secure Boot is enabled in BIOS but Windows still shows Secure Boot State as Off, your Secure Boot keys may be missing or misconfigured.
Look for one of these options in BIOS:
This is especially useful for errors like STATUS_SB_POLICY, where Riot says the system may require Secure Boot key reset even if Secure Boot is already active.
Important: Choose restore/reset default keys, not “clear keys,” unless your motherboard manual specifically tells you to.
If Secure Boot or TPM settings are missing, outdated BIOS firmware may be the reason. Riot’s support information notes that if Secure Boot cannot be enabled or TPM is enabled but errors continue, the motherboard may need a BIOS firmware update.
Download BIOS updates only from your official manufacturer website, such as:
Do not download BIOS files from random websites.
If your BIOS settings are correct but Valorant still shows the error, reinstall Vanguard.
Steps:
This can fix Vanguard service issues after updates or corrupted installs.
Open:
Windows Security > Device Security
Check whether Windows shows Secure Boot as active. Microsoft says Windows Security can show Secure Boot status under Device Security, including status indicators for Secure Boot certificate updates.
If Windows shows Secure Boot problems, install Windows updates and check your device manufacturer’s BIOS updates.
Do not use random “Valorant Secure Boot bypass” tools. These can be unsafe and may violate Riot’s rules. Avoid:
These tools may damage Windows, create security risks, or lead to account penalties.
| Problem | Best Fix |
| VAN 9003 | Enable Secure Boot |
| VAN 9001 | Enable TPM 2.0 and Secure Boot |
| Secure Boot is enabled, but still an error | Load default Secure Boot keys |
| BIOS Mode shows Legacy | Convert carefully to UEFI/GPT |
| Secure Boot option missing | Disable CSM or update BIOS |
| Valorant worked before the update | Restart PC and reinstall Vanguard |
| STATUS_SB_POLICY | Reset Secure Boot keys |
Use this checklist before launching Valorant:
On many Windows 11 systems, Valorant may not run properly without Secure Boot and TPM 2.0 enabled. Vanguard uses these requirements to verify system integrity. If your system does not support Secure Boot, you may need newer hardware or official manufacturer firmware support.
Whether Valorant can run without Secure Boot depends on your operating system, hardware configuration, and Riot Vanguard requirements at the time. On newer systems, especially Windows 11 devices, Secure Boot and TPM 2.0 are often important parts of the security checks used by Vanguard. Because of this, many UEFI Secure Boot Valorant errors occur when one or both of these features are disabled or incorrectly configured.
If Valorant previously worked without Secure Boot but now reports Vanguard restriction errors, check your BIOS settings, Windows security configuration, and TPM status. Firmware updates, BIOS resets, or operating system upgrades can sometimes change security settings without the user realizing it.
Yes, Secure Boot is a standard Windows security feature when configured correctly. It helps protect the boot process from untrusted software. However, BIOS changes should always be done carefully. Before changing firmware settings, save important work and back up important files.
Secure Boot is designed to help prevent unauthorized bootloaders, drivers, and low-level software from loading before Windows starts. This additional protection can reduce certain security risks and improve system integrity. For most users, enabling Secure Boot is considered a recommended security practice rather than a gaming-specific requirement.
When troubleshooting UEFI Secure Boot Valorant issues, users should avoid modifying unrelated BIOS settings and should always follow guidance from their motherboard manufacturer. If Secure Boot is already enabled and Vanguard still reports errors, additional troubleshooting may be required, such as verifying Secure Boot keys, checking TPM 2.0 status, or updating BIOS firmware.
Do not switch Legacy to UEFI blindly. If your Windows drive uses MBR, changing boot mode may stop Windows from booting.
Some systems require CSM to be disabled before Secure Boot works properly.
After enabling Secure Boot, press the correct key to save and exit. Usually this is F10, but it depends on your motherboard.
Do not clear Secure Boot keys unless you know what you are doing. Most users should restore or install default keys instead.
Do not use third-party tools that claim to bypass Valorant Vanguard requirements.
Most UEFI Secure Boot Valorant errors can be fixed by enabling Secure Boot, enabling TPM 2.0, disabling CSM, updating BIOS firmware, or reinstalling Riot Vanguard. However, some situations may require direct assistance from Riot Support.
You should contact Riot Support if:
Before contacting Riot Support, gather the following information:
Providing these details can help Riot Support diagnose the issue more quickly.
At this stage, Riot Support may be able to identify account-specific, Vanguard-specific, hardware-specific, or configuration-specific issues that cannot be resolved through standard troubleshooting steps.
This guide was created using publicly available Riot Vanguard documentation, Microsoft Secure Boot guidance, and current Windows security requirements. The troubleshooting steps, Secure Boot recommendations, TPM 2.0 guidance, and Vanguard error references are based on information available from official sources and widely accepted Windows security practices.
Because BIOS and UEFI menus differ between motherboard manufacturers, laptop brands, and firmware versions, some settings may appear under different names or locations on your system. Users should always consult their motherboard manual, device documentation, or manufacturer support resources before making firmware changes.
When modifying BIOS settings, it is also recommended to create a backup of important files and verify system compatibility before changing boot modes, Secure Boot settings, TPM configurations, or partition structures.
While this guide covers the most common UEFI Secure Boot Valorant issues reported by players, individual hardware configurations may require additional troubleshooting or assistance from Riot Support or the device manufacturer.
The time required to fix a UEFI Secure Boot Valorant error depends on the underlying cause. Some fixes take only a few minutes, while others may require BIOS updates or disk conversion procedures.
| Issue | Typical Fix Time |
| Enable Secure Boot | 5–10 minutes |
| Enable TPM 2.0 | About 5 minutes |
| Disable CSM | About 5 minutes |
| Reinstall Riot Vanguard | 10–15 minutes |
| BIOS Update | 15–30 minutes |
| MBR to GPT Conversion | 15–30 minutes |
Most players resolve UEFI Secure Boot Valorant errors within 10 to 20 minutes, especially when the issue is caused by Secure Boot, TPM 2.0, or CSM settings. More advanced fixes, such as BIOS updates or MBR to GPT conversion, may take longer and should be performed carefully.
Modern games increasingly rely on advanced security technologies to combat cheating and protect competitive environments. As Windows 11 adoption continues to grow and firmware-level security becomes more important, players are more likely to encounter Secure Boot, TPM 2.0, and UEFI-related requirements than in previous years. Understanding these technologies can help prevent future launch issues and improve overall system security.
UEFI Secure Boot Valorant errors are usually fixable by enabling TPM 2.0, switching to UEFI mode, disabling CSM, enabling Secure Boot, loading default Secure Boot keys, and reinstalling Riot Vanguard if needed.
The safest method is to first check msinfo32. If BIOS Mode shows UEFI and Secure Boot State shows On, your system is mostly ready. If not, adjust BIOS settings carefully and follow your motherboard or laptop manufacturer’s official guide.
For most players, the best fix is simple: enable TPM 2.0, enable Secure Boot, restart the PC, and relaunch Valorant. Following the troubleshooting steps in this UEFI Secure Boot Valorant guide can help resolve the majority of Vanguard security restriction errors and get the game running normally again.
In some cases, yes. A BIOS update can add Secure Boot support, improve TPM compatibility, fix firmware bugs, and resolve configuration issues that prevent Riot Vanguard from recognizing Secure Boot correctly. Always download BIOS updates from your device manufacturer’s official website.
While antivirus software does not usually disable Secure Boot, some security programs can interfere with Vanguard services or system security checks. If Valorant continues showing errors after Secure Boot is enabled, temporarily disable non-essential security software for testing and ensure Vanguard services are running properly.
Secure Boot requirements can vary depending on hardware, firmware version, Windows installation type, TPM availability, and BIOS configuration. Two systems running the same version of Valorant may behave differently if one uses Legacy BIOS mode or has Secure Boot disabled.
Yes. Resetting BIOS settings may disable Secure Boot, TPM 2.0, or UEFI mode. After a BIOS reset, players should verify all security settings before launching Valorant because default firmware settings can differ between manufacturers.
Reinstalling Windows is rarely necessary. Most Secure Boot-related Vanguard errors can be resolved by enabling TPM 2.0, enabling Secure Boot, disabling CSM, updating BIOS firmware, or reinstalling Riot Vanguard. Windows reinstallation should generally be considered a last resort.
Yes. Features such as Legacy Boot, CSM, custom Secure Boot keys, overclocking-related firmware settings, or advanced boot configurations can sometimes interfere with Vanguard security checks. Returning BIOS settings to a stable configuration may help resolve persistent issues.
To reduce the chance of future errors, keep Windows updated, install BIOS updates when recommended by your manufacturer, avoid changing Secure Boot settings unnecessarily, maintain TPM 2.0 support, and verify BIOS settings after firmware updates or system resets.
Girl Scout Cookies 2026 brings exciting changes for cookie fans, including the debut of Exploremores, a brand-new rocky road-inspired cookie,…
If you bought a new phone, reset your old phone, switched from Android to iPhone, or moved from iPhone to…
New Boot Goofin means showing off, joking around, dancing, posing, or feeling confident while wearing a new pair of boots.…
Decoradhouse Renovation Tips From DecoratorAdvice provide practical strategies for homeowners who want to improve comfort, functionality, energy efficiency, and property…
Vendor selection sits upstream of every other engagement decision because it shapes velocity, cost predictability, and how much engineering attention…
In a general hospital, 650 claims are denied every week. After treating a patient, the hospital sends a bill to…