VALORANT VAN9005 Fix 2026: TPM, UEFI and VBS
VAN9005 is not a normal connection error. It is a Vanguard compliance warning tied to Virtualization-based Security, UEFI Mode and TPM 2.0. This guide gives you a safe decision tree before you change BIOS settings or disable Windows security features.
Sources: Riot’s VAN 9005 support page, Riot’s VBS settings guide for Windows 10 VAN9005, and the official VALORANT Support Vanguard section.
How do you fix VALORANT VAN9005?
The safest VALORANT VAN9005 fix is to check whether your system supports UEFI Mode and TPM 2.0, confirm whether those features are enabled, then check whether Virtualization-based Security is running. If your system supports the required firmware path, enable UEFI Mode and TPM 2.0 correctly. If Riot’s Windows 10 VBS path applies and UEFI/TPM support is not available, follow Riot’s guidance for disabling VBS instead.
VAN9005 can involve firmware, boot mode, TPM, Windows security and Vanguard all at once. A careful check order is safer than changing five settings and hoping one works.
Check Windows version, BIOS Mode, TPM 2.0 and VBS first. Then choose either the UEFI/TPM path or the Riot Windows 10 VBS path. Do not treat VAN9005 like VAN9003 or VAN 1067.
What does VAN9005 mean in VALORANT?
VAN9005 means Vanguard is not satisfied with your current system security configuration. Riot’s support guidance points to UEFI Mode, TPM 2.0 and Virtualization-based Security, also called VBS. In plain English, Vanguard is checking whether Windows security features and firmware support line up correctly.
The common wording around this issue says this version of Vanguard requires TPM 2.0 and UEFI-compliant firmware to use Virtualization-based Security. Focus on VBS, UEFI and TPM, not generic lag, server status or account login fixes.
VAN9005 vs VAN9003 vs VAN Restriction 5
VAN9005 overlaps with other Vanguard errors, but it is not the same page intent. VAN9003 is mainly a Secure Boot and TPM compliance issue. VAN Restriction 5 is more focused on HVCI or Memory Integrity failing to initialize. VAN9005 is the VBS, UEFI Mode and TPM 2.0 decision tree.
| Error | Main focus | Best next guide |
|---|---|---|
| VAN9005 | VBS, UEFI Mode, TPM 2.0 | Use this page first. |
| VAN9003 | Secure Boot and TPM | Use the VAN9003 Secure Boot and TPM guide. |
| VAN Restriction 5 | HVCI / Memory Integrity | Use the HVCI and Secure Boot guide. |
| VAN 1067 | Vanguard service / Windows stability | Use the VAN 1067 fix guide. |
Check your Windows version first
Before changing firmware settings, confirm whether you are on Windows 10 or Windows 11. This matters because Windows 11 and Windows 10 do not always land on the same practical path for Vanguard security requirements.
For Windows 11, TPM 2.0 and UEFI-compliant firmware are normally part of the expected setup. The VALORANT VAN9005 Windows 11 path is usually about confirming those security requirements are actually enabled. For Windows 10, Riot’s VAN9005 guidance specifically includes a VBS path for systems where UEFI Mode or TPM 2.0 is not supported. That makes the VALORANT VAN9005 Windows 10 path slightly different, but it still does not mean everyone should disable VBS; the correct path depends on your system.
Check BIOS Mode in msinfo32
Press the Windows key, type msinfo32, open System Information and look for BIOS Mode. If it says UEFI, your system is already using UEFI Mode. If it says Legacy, VAN9005 may appear because Vanguard expects UEFI-compliant firmware for the VBS path.
Be careful here: switching from Legacy to UEFI is not always a simple toggle. It can depend on disk partition style, motherboard firmware and Windows installation. If you are not comfortable with boot settings, check your device manual or motherboard support before changing anything.
Check TPM 2.0 with tpm.msc
Press the Windows key, type tpm.msc and open the Trusted Platform Module tool. Look for TPM status and specification version. For Riot’s VAN9005 path, the important phrase is TPM 2.0. If TPM is missing, disabled or older than 2.0, Vanguard may continue to complain.
TPM can appear under different names depending on your hardware. Intel systems may call it Intel PTT. AMD systems may call it AMD fTPM. Laptop firmware can hide it under security, trusted computing or advanced tabs.
Check VBS and Virtualization-based Security
Open msinfo32 again and look for Virtualization-based security. If VBS is running while your firmware path does not support UEFI Mode and TPM 2.0 properly, that is the classic VAN9005 situation Riot’s Windows 10 support page addresses.
VBS is a Windows security feature, not a VALORANT graphics setting. Changing it can affect system security, so keep VBS advice tied to Riot’s VAN9005 steps.
Prefer fixing the firmware support path and enabling the required features correctly.
On Windows 10, Riot’s VAN9005 guidance may point toward disabling VBS as the fallback.
Enable UEFI Mode and TPM 2.0 if supported
If your PC supports the required features, the cleaner fix is to make the system compliant: UEFI Mode enabled and TPM 2.0 active. This may involve BIOS or UEFI menus, but the exact names vary by motherboard and laptop brand.
Do not guess inside firmware menus. Search your motherboard or laptop model plus TPM, fTPM, Intel PTT, UEFI and Secure Boot. This is the VALORANT TPM 2.0 UEFI branch of the fix, so if you are changing boot mode from Legacy to UEFI, check whether your Windows installation and disk partition style support it before saving changes.
Disable VBS only when Riot’s Windows 10 path applies
If your Windows 10 machine cannot support UEFI Mode or TPM 2.0, Riot’s VAN9005 guidance includes a fallback path to disable VBS so VALORANT can run. This is not a universal recommendation for every player, and it is not the first thing to try on a system that can be made compliant.
If you do follow the VBS path, use Riot’s official steps and understand the security tradeoff. Do not paste unknown commands from comment sections, and avoid stacking random tweaks like disabling every Windows security feature at once.
Secure Boot and Memory Integrity: what not to confuse
Secure Boot and Memory Integrity often appear in the same conversations, but VAN9005 should not become a generic Secure Boot article. Secure Boot is more central to VAN9003. Memory Integrity and HVCI are more central to VAN Restriction 5. VAN9005 is about whether VBS has the firmware support Vanguard expects.
If your exact message mentions Secure Boot or TPM without VBS wording, compare it with the VALORANT VAN9003 Secure Boot and TPM fix. If your message mentions HVCI or Memory Integrity failing to initialize, compare it with the VAN Restriction 5 HVCI guide.
What not to do when fixing VAN9005
Do not change boot mode, Secure Boot, virtualization, Memory Integrity and TPM all at once. If Windows fails to boot afterward, you no longer know which change caused it.
When to contact Riot Support or motherboard support
Contact Riot Support if your system appears compliant but VAN9005 still appears after a full restart. Contact your motherboard or laptop support if you cannot find TPM, Intel PTT, AMD fTPM, UEFI Mode or Secure Boot settings in firmware.
When you ask for help, include your Windows version, BIOS Mode from msinfo32, TPM status from tpm.msc, VBS status, motherboard or laptop model and the exact VAN9005 wording. That gives support a useful technical picture.
Fix the PC before judging the account.
VAN9005 is a device compliance issue. Once your system is stable, then it makes sense to focus on rank, region, skins or a new VALORANT account.
VALORANT VAN9005 FAQ
What does VAN9005 mean in VALORANT?
VAN9005 means Vanguard is out of compliance with the current system security configuration. Riot’s guidance points to UEFI Mode, TPM 2.0 and Virtualization-based Security (VBS), especially on Windows 10 systems where VBS is running without the required firmware support.
How do I fix VALORANT VAN9005?
Check Windows version first, then use msinfo32 to verify BIOS Mode and VBS status, use tpm.msc to verify TPM 2.0, enable UEFI Mode and TPM 2.0 if your system supports them, and only use the VBS-disable path when Riot’s Windows 10 guidance applies.
Do I need TPM 2.0 for VAN9005?
Riot’s VAN9005 guidance focuses on TPM 2.0 and UEFI-compliant firmware when VBS is involved. Windows 11 systems normally require TPM 2.0 for VALORANT, while some Windows 10 cases may use Riot’s VBS-disable path if TPM 2.0 or UEFI support is unavailable.
What is VBS in the VAN9005 error?
VBS means Virtualization-based Security. It is a Windows security feature that uses virtualization to protect sensitive parts of the system. VAN9005 can appear when VBS is running but the firmware configuration does not meet Vanguard’s requirements.
Can I disable VBS to fix VAN9005?
Only follow the VBS-disable path if it matches Riot’s guidance for your Windows version and system support situation. Do not randomly disable security features without understanding the tradeoff or checking official Riot and device support documentation.
Is VAN9005 the same as VAN9003?
No. VAN9003 is mainly a Secure Boot and TPM compliance error. VAN9005 is focused on Vanguard’s VBS, UEFI Mode and TPM 2.0 compliance path. They overlap, but they should not be treated as the same error.
Should I change BIOS settings myself?
Only change BIOS or UEFI settings if you understand your motherboard or laptop firmware. If you are unsure, check your device manual, motherboard support page or Riot Support before changing boot mode, TPM or Secure Boot settings.
Why does VAN9005 still appear after enabling TPM?
VAN9005 can still appear if BIOS Mode is Legacy instead of UEFI, TPM is enabled incorrectly, VBS remains in a conflicting state, Windows needs a full restart, or your firmware settings do not match Vanguard’s requirements.