How to Fix VAN 9005 in Valorant (VBS, TPM 2.0 and UEFI) – 2026

8 min to read

How to Fix VAN 9005 in Valorant (VBS, TPM 2.0 and UEFI) – 2026

VAN 9005 means Riot Vanguard wants Virtualization-based Security (VBS) running on your PC, and VBS cannot start because TPM 2.0, UEFI boot, CPU virtualization or the Windows hypervisor is missing. Fix it by turning on TPM, Secure Boot and virtualization in the BIOS, then Memory integrity in Windows Security. After one restart VBS runs and Valorant starts.

VAN 9005

Vanguard requires TPM 2.0 and UEFI-compliant firmware to use Virtualization-based Security (VBS)
Riot Vanguard: VAN 9005

What causes VAN 9005

VBS is a Windows feature that uses the CPU's virtualization to protect the kernel. Riot asks for it on some PCs. It only runs when all of these are true:

  • the PC starts in UEFI mode with a TPM 2.0 and Secure Boot,
  • CPU virtualization (SVM on AMD, VT-x on Intel) is on in the BIOS,
  • the Windows hypervisor is allowed to start (tweak tools often set hypervisorlaunchtype off),
  • Memory integrity or VBS is turned on in Windows.

How to fix VAN 9005 in Windows

1

Used RIP Tweaks before? Turn our Windows tweaks off first

If you turned on Disable Windows Hypervisor, Windows 10 Optimization or Windows 11 Optimization in RIP Tweaks, turn them off in the app and restart. They switch off the Windows hypervisor and Memory integrity, which this check needs. Turning them off puts back the settings your PC had.
2

Check your TPM

Press Win + R, type tpm.msc and press Enter. The TPM is ready for use with Specification Version 2.0 is what you want. Compatible TPM cannot be found means the firmware TPM is switched off in the BIOS. Almost every AMD Ryzen CPU (fTPM) and Intel CPU of the last years (PTT) has one built in.
3

Check that virtualization is on

Open Task Manager > Performance > CPU. Under the graph, Virtualization must say Enabled. If it says Disabled, turn it on in the BIOS (steps below).
4

Suspend BitLocker first (if it is on)

Changing TPM, Secure Boot or boot settings can make BitLocker ask for its 48-digit recovery key at the next start. Open Start, type Manage BitLocker and, if drive C: shows BitLocker on, click Suspend protection. On Windows Home look under Settings > Privacy & security > Device encryption. Or run this in Terminal (Admin): manage-bde -protectors -disable C: -RebootCount 2. It turns itself back on after two restarts. Check that you can see your recovery key at aka.ms/myrecoverykey before you go on.
5

Let the Windows hypervisor start

Memory integrity and VBS run on the Windows hypervisor. If a tweak tool switched it off, Memory integrity stays off even when the switch says on. In Terminal (Admin) run bcdedit /set hypervisorlaunchtype auto and restart.
6

Turn on Memory integrity

Open Windows Security > Device security > Core isolation details and switch Memory integrity on, then restart. If Windows refuses and shows Review incompatible drivers, click it: it lists the driver files in the way (often old RGB, fan, overclocking or anti-virus tools). Update or uninstall the app that installed each one, then try again. Never delete driver files by hand.
7

Check that VBS is running

Open msinfo32 again. Virtualization-based security should say Running. If it says Enabled but not running, virtualization is off in the BIOS (SVM on AMD, Intel Virtualization Technology on Intel) or the hypervisor is not allowed to start (step above). Turning on Memory integrity turns VBS on by itself.

How to fix it in the BIOS

This part happens in your PC's firmware setup (the BIOS), so open this page on your phone first. Menu names change a little between BIOS versions: if a path below does not match, look for the words in bold.

1

Restart into the BIOS

Open Settings > System > Recovery, click Restart now next to Advanced startup, then Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. Or run shutdown /r /fw /t 0 in Terminal (Admin). You can also press Del right after switching the PC on (desktops; F2 on many laptops and some ASRock and MSI boards).
2

Change these settings

  • Turn on the firmware TPM: AMD fTPM (often Firmware TPM) on AMD, Intel PTT (Platform Trust Technology) on Intel.
  • Turn on Secure Boot and install the default keys (Install default Secure Boot keys or Restore Factory Keys). Secure Boot mode Standard, OS type Windows UEFI mode.
  • Turn on CPU virtualization: SVM Mode on AMD, Intel Virtualization Technology (VT-x) on Intel.

Where to find them on your board:

ASUS

Press F7 for Advanced Mode.
TPM 2.0 (AMD fTPM / Intel PTT): Advanced > AMD fTPM configuration > Firmware TPM (AMD), or Advanced > PCH-FW Configuration > PTT (Intel)
Secure Boot: Boot > Secure Boot > OS Type: Windows UEFI mode, then Key Management > Install Default Secure Boot keys
CPU virtualization (SVM / VT-x): Advanced > CPU Configuration > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

MSI

Press F7 for Advanced mode.
TPM 2.0 (AMD fTPM / Intel PTT): Settings > Security > Trusted Computing > Security Device Support: Enable, then AMD CPU fTPM or Intel PTT
Secure Boot: Settings > Advanced > Windows OS Configuration > Secure Boot: Enabled, Secure Boot Mode: Standard
CPU virtualization (SVM / VT-x): OC > Advanced CPU Configuration > SVM Mode (AMD) or Intel Virtualization Tech (Intel)

Gigabyte (AORUS)

Press F2 to switch to Advanced Mode.
TPM 2.0 (AMD fTPM / Intel PTT): Settings > Miscellaneous > AMD CPU fTPM (AMD) or Intel Platform Trust Technology (PTT) (Intel)
Secure Boot: Boot > Secure Boot: Enabled, Secure Boot Mode: Standard (or Restore Factory Keys)
CPU virtualization (SVM / VT-x): Tweaker > Advanced CPU Settings > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

ASRock

Press F6 to switch to Advanced Mode.
TPM 2.0 (AMD fTPM / Intel PTT): Advanced > CPU Configuration > AMD fTPM switch (AMD), or Security > Intel Platform Trust Technology (Intel)
Secure Boot: Security > Secure Boot: Enabled, then Install Default Secure Boot Keys
CPU virtualization (SVM / VT-x): Advanced > CPU Configuration > SVM Mode (AMD) or Intel Virtualization Technology (Intel)

Laptops and prebuilt PCs

Dell: F2, Boot Configuration > Secure Boot, Security > TPM 2.0 Security On, Virtualization Support > VT / VT-d.
HP: Esc then F10, Advanced > Secure Boot Configuration, Security > TPM Embedded Security, Advanced > System Options > Virtualization Technology.
Lenovo: F1 on ThinkPad, F2 or the Novo button on IdeaPad and Legion, Security > Secure Boot, Security > Security Chip, Security > Virtualization.
ASUS: F2, Security > Secure Boot Control, Advanced > Trusted Computing.
Acer: F2, set a Supervisor password first or Secure Boot stays greyed out, then Boot > Secure Boot and Security > TPM.
MSI: Del, Security > Secure Boot, Advanced > Trusted Computing.
Gigabyte / AORUS: F2, Security > Secure Boot, Advanced > Trusted Computing.
3

Save and restart

Press F10 and confirm with Yes. Windows starts normally.

Fix it in one click with RIP Tweaks (free)

RIP Tweaks 6.9.3 has a free anti-cheat error fixer. Open Fixes, then Anti-cheat errors, and paste VAN 9005 or pick your game. The app first checks what your PC has right now (for example Secure Boot: Off, TPM: On) and shows only the steps still missing.

The anti-cheat error fixer in RIP Tweaks

It fixes the Windows side itself

Memory integrity, the Windows hypervisor, test signing, Control Flow Guard, the vulnerable driver blocklist and services that an optimizer switched off: the app changes them for you, saves what it changed first, and can put every change back.

It takes you into the BIOS with the right card

What only the BIOS can change (TPM, Secure Boot, CSM, virtualization, IOMMU), the app shows for your exact board maker, suspends BitLocker for you and restarts straight into the BIOS. A QR code opens this page on your phone.

It checks again after the restart

Back in Windows, the fixer checks again and shows green, or exactly what is still missing.

The fixer is free in every plan, also without an account. Download RIP Tweaks (free)

Check that it worked

Open msinfo32: Virtualization-based security must say Running, and Virtualization-based security Services Running should list Hypervisor enforced Code Integrity. Then start the Riot Client.

Frequently asked questions

What is the difference between VAN 9005 and VAN 9001?

VAN 9001 only asks for TPM 2.0 and Secure Boot. VAN 9005 asks for VBS on top, which also needs CPU virtualization, the Windows hypervisor and Memory integrity.

Why does Riot ask me for VBS and not my friend?

Riot turns on extra checks for some PCs and accounts, for example when the system looks unusual. It is not a ban: once VBS runs, you can play.

Does Memory integrity lower FPS?

It can cost a little performance in some games, and Microsoft says so itself. On recent CPUs the difference is usually small. When an anti-cheat requires it, there is no way around it: it has to be on to play.

Memory integrity will not turn on. Why?

Almost always a driver Windows does not allow under Memory integrity. Click Review incompatible drivers in Core isolation, update or remove the app behind each driver, and restart. If the switch turns itself off again, the Windows hypervisor is blocked (run bcdedit /set hypervisorlaunchtype auto) or virtualization is off in the BIOS.

How do I do this on a laptop?

The same settings exist on laptops, only the key and the menus differ: F2 on most (Dell, ASUS, Acer, Lenovo IdeaPad and Legion), F1 on ThinkPads, Esc then F10 on HP. The Laptops card above lists where each maker puts Secure Boot, the TPM and virtualization.

Can changing these settings get me banned?

No. These are the anti-cheat's own requirements, and the publisher asks you to change them. Bans come from cheats and tools that tamper with the game, never from turning on Windows security features.

Sources

All anti-cheat errors: Anti-Cheat Error Fixes. Related: How to Fix VAN: RESTRICTION 1, 3, 4 and 5 in Valorant – 2026 and How to Fix VAN 9001 in Valorant (TPM 2.0 and Secure Boot) – 2026.