Does Valorant Require TPM 2.0? | Fix VAN 9001 & Errors

Let’s cut straight to the chase, because if you’re reading this, you’re likely staring at a screen that says VAN 9001 or VAN: RESTRICTION, and you’re wondering, “Why can’t I just play the game?”

The short answer to "does Valorant require tpm 2.0" is: Yes. But it’s not as simple as a binary "yes/no" switch on your BIOS. Riot’s anti-cheat system, Vanguard, is deeply integrated into the Windows kernel, and it relies on Trusted Platform Module (TPM) 2.0 to verify that your hardware hasn’t been tampered with. This requirement is what drives the error codes you’re seeing, specifically when VBS core isolation or processor-based data protection settings conflict with the anti-cheat’s integrity checks.

I’ve spent the last few years troubleshooting security stack issues for both enterprise and consumer clients, and this specific pain point—where the game’s security layer clashes with the OS’s security layer—is one of the most common requests I get. It’s frustrating because the requirement feels arbitrary to a gamer who just wants to queue up. But understanding the difference between a discrete TPM chip (dTPM) and a firmware-based TPM (fTPM/PTT) is crucial. Many users think they’ve "fixed" it by enabling a generic TPM, only to find out they enabled the wrong type for their specific error code.

In this guide, we’re going to map out exactly where your hardware stands, whether you’re on Windows 10 or 11, and how to actually flip the right switches in your BIOS. We’ll distinguish between the "Intel PTT" path and the "AMD fTPM" path, because confusing these two is where most troubleshooting efforts go off the rails.

Understanding Vanguard's Security Requirements: TPM, VBS & Secure Boot

Why Riot Requires TPM 2.0

To understand why this requirement exists, you have to look at how Vanguard operates. Unlike standalone anti-cheat software, Vanguard runs at Ring 0 (kernel level). This means it has deep access to your system’s memory and processes. For security reasons, Riot Games mandates that this kernel module be verified against a hardware root of trust. That root of trust is the TPM 2.0.

It’s not just about stopping cheaters; it’s about ensuring the integrity of the operating environment. If the TPM isn’t reporting a secure boot chain, Vanguard assumes the system might be compromised and refuses to launch the client to prevent potential exploitation of its kernel-level privileges.

Important Note: TPM 1.2 is simply not enough. The industry standard shifted years ago, and both Windows 11 and Vanguard’s modern integrity checks rely on the TPM 2.0 specification. If your PC only supports 1.2, you are looking at a hard hardware blocker. Additionally, Secure Boot and UEFI boot mode are typically prerequisites. You generally cannot enable a modern fTPM configuration if your system is still booting in Legacy BIOS mode.

Discrete TPM vs. Firmware TPM (Intel PTT & AMD fTPM)

This is where the confusion usually starts, and it’s the key to solving your specific error code.

There are two ways your PC can provide TPM 2.0:

1. Discrete TPM (dTPM): A physical chip soldered onto the motherboard or inserted into a dedicated header.
2. Firmware TPM (fTPM): Logic built directly into the CPU.

For Intel systems (4th Gen and newer), this is called Platform Trust Technology (PTT). For AMD systems (Ryzen 1000 series and newer), it’s called fTPM.

Here is the critical distinction I’ve found in my testing:

• A dTPM will often satisfy basic Vanguard requirements, such as fixing VAN 9001.
• However, if you are hitting a VAN: RESTRICTION error, Vanguard is specifically demanding fTPM/PTT. A discrete module alone will not be enough for this stricter check.

Comparison of CPU Generations & TPM Capability:

Step-by-Step: How to Check If Your PC Supports TPM 2.0

Before you dive into the BIOS, which is a risky place to mess around if you’re not careful, you need to know what you’re working with. Here is how to verify your current status in Windows.

Using the tpm.msc Diagnostic Tool

This is the fastest way to check.

1. Press Windows Key + R on your keyboard.
2. Type tpm.msc and hit Enter.
3. Look at the "Status" column on the right-hand panel.

You’ll typically see one of three states:

• "The TPM is ready for use": Great. Look at "TPM Specification Version." If it says 2.0, you’re good to go. You can launch the game.
• "The TPM is ready for use," but version is 1.2: This is a blocker. Vanguard does not support TPM 1.2. You need to check your BIOS to see if you can switch to a 2.0 compatible mode (fTPM/PTT).
• "Compatible TPM cannot be found": This usually means TPM is disabled in the BIOS, or your hardware doesn’t support it.

If the console doesn’t open at all, don’t panic. It’s often a sign that the TPM is completely off, or the Windows service for it is stopped. Move to the next check.

Alternative: Windows Security App

If tpm.msc gives you a blank screen or fails to load, use the built-in Windows Security app. This is also where you’ll see the context for Windows security processor-based data protection.

1. Open Windows Security (search for it in the Start menu).
2. Go to Device Security.
3. Look for the section titled "Security processor-based data protection."

On Windows 11, this section explicitly tells you if TPM 2.0 and Secure Boot are enabled. On Windows 10, this information is less visible but still present under "Device Security" if you have a modern UEFI system. If this section is missing or shows no hardware security support, your PC likely lacks the necessary firmware capabilities, or they are disabled in the UEFI settings.

Enabling TPM 2.0 in BIOS: Intel PTT & AMD fTPM Guide

Now for the hands-on work. I always recommend making a note of your current BIOS settings before you change anything. It’s a rare but possible scenario where tweaking a setting prevents your PC from POSTing (Power On Self Test).

Accessing UEFI/BIOS Settings

You need to get into the firmware interface. There are two reliable ways to do this:

1. The Hardware Key Method: Restart your PC and spam the BIOS key before the Windows logo appears. This key varies by manufacturer (Del, F2, F10).
   • Dell/Alienware: F2
   • HP: F10
   • Lenovo: F1 or Enter then F1
   • Asus/MSI/Gigabyte/ASRock: Usually Del or F2
2. The Windows Method (More Reliable): This avoids timing issues.
   • Go to Settings > Update & Security > Recovery (Windows 10) or Settings > System > Recovery (Windows 11).
   • Under "Advanced startup," click Restart now.
   • Boot into Troubleshoot > Advanced options > UEFI Firmware Settings.
   • Click Restart.

Crucial Prerequisite: Ensure your system is set to UEFI boot mode, not Legacy BIOS. TPM 2.0 functionality, especially fTPM/PTT, relies on the UEFI stack. If you are in Legacy mode, you likely won’t see the option to enable PTT or fTPM.

Intel Systems: Enabling Platform Trust Technology (PTT)

On Intel systems, you are looking for PTT (Platform Trust Technology). This is the firmware-based TPM.

General BIOS Path:

• Advanced > PCH-FW Configuration > PTT > Set to Enabled.

However, the menu names change drastically depending on the motherboard vendor. Here’s what I’ve seen in the major brands:

• ASUS: Advanced > PCH-FW Configuration > PTT > Enabled
• MSI: Settings > Security > Trusted Computing > PTT > Enabled
• Gigabyte: Settings > Miscellaneous > Intel Platform Trust Technology > Enabled
• ASRock: Security > Intel Platform Trust Technology > Enabled

If you don’t see "PTT," look for "Trusted Computing Module State" or "TPM State" and set it to "Enabled."

AMD Systems: Enabling fTPM

On AMD systems, the option is usually labeled AMD fTPM or Firmware TPM.

General BIOS Path:

• Advanced > AMD fTPM Configuration > TPM Device Selection > Set to AMD CPU fTPM.

Brand-Specific Paths:

• ASUS: Advanced > AMD fTPM Configuration > AMD fTPM switch > Enabled
• MSI: Settings > Security > Trusted Computing > TPM Device Selection > AMD CPU fTPM
• Gigabyte: Settings > Miscellaneous > AMD CPU fTPM > Enabled
• ASRock: Advanced > CPU Configuration > AMD fTPM Switch > AMD CPU fTPM

⚠️ Warning: Enabling fTPM will generate new encryption keys. If you have BitLocker enabled on your Windows drive, you must suspend BitLocker or have your recovery key available before toggling this setting. If you clear the TPM keys without a backup, you could be locked out of your own files. I cannot stress this enough—check your BitLocker status in Control Panel before touching the BIOS.

Troubleshooting: Valorant Not Launching Due to TPM Errors

You’ve enabled the setting, rebooted, and the game still won’t start? Or you’re getting a new error? Let’s map out the specific failure points.

Fixing VAN 9001, 9003, and VAN: RESTRICTION

These codes tell you exactly what’s wrong.

• VAN 9001: "TPM 2.0 is not enabled or available."
  • Fix: You likely have a dTPM enabled, or nothing is enabled. Switch to fTPM/PTT in BIOS as detailed above.
• VAN 9003: "TPM 2.0 is not initialized."
  • Fix: This often happens if the BIOS firmware is outdated. The TPM module exists, but the initialization handshake with the OS fails. You need to update your BIOS to the latest version from your manufacturer’s website.
• VAN: RESTRICTION: This is the big one. It usually lists "TPM 2.0 (Firmware)" as the missing component.
  • Fix: A discrete TPM chip is not enough. You must have Intel PTT or AMD fTPM enabled. If you have enabled PTT/fTPM and you still see this, your BIOS version likely lacks the correct AGESA or PCH firmware to properly expose the fTPM to the OS.

Step-by-Step for Persistent Errors:

1. Note your current BIOS version in the main BIOS screen.
2. Download the latest BIOS from your motherboard or laptop manufacturer’s support page.
3. Flash the BIOS. (Follow manufacturer instructions strictly).
4. Re-enter BIOS and ensure PTT/fTPM is still enabled.
5. Restart and check tpm.msc again.

AMD Ryzen Stuttering Bug & VBS Core Isolation

There is a known issue with older AMD Ryzen systems where enabling fTPM can cause random micro-stutters or frame hitches every few minutes. This was caused by a bug in the older AGESA (AMD Generic Software Abstraction Layer) firmware.

Do NOT disable fTPM to fix the stuttering. If you do, you will lose the ability to run Vanguard.

Instead, update your BIOS. AMD released updates specifically to fix the fTPM stutter issue. Check your motherboard support page for the latest "AGESA" version notes.

You might also encounter VBS core isolation (Virtualization-Based Security) errors. VBS uses memory isolation to protect the kernel, which can conflict with Vanguard’s own kernel protection. On Windows 10, Riot recommends disabling VBS if you have no TPM support. However, if you do have TPM 2.0 (fTPM/PTT), you should keep VBS enabled, as Vanguard is designed to coexist with it. If you are on Windows 11, VBS and TPM are mandatory components of the OS security model, so disabling them is not a viable option.

Can You Play Valorant Without TPM 2.0? (Workarounds & Realities)

This is the "can I cheat the system" section. I know many users are searching for "valorant without tpm 2.0" options. Let’s look at the reality.

The Windows 10 'Grace Period' & Compatibility

There is a persistent myth that Windows 10 allows you to bypass these requirements. It doesn’t.

While Windows 10 itself doesn’t strictly require TPM 2.0 for installation (unlike Windows 11), Vanguard anti-cheat does. Riot has updated the Vanguard kernel driver to enforce TPM 2.0 checks on both Windows 10 and 11 to close off cheat vectors.

• TPM 1.2: Not supported. It’s a dead end.
• No TPM: Not supported for Vanguard-enabled titles.

Is there a "bypass" method? No. There is no legitimate software bypass. Any tool claiming to "bypass TPM 2.0 for Valorant" is either malware, a scam, or a temporary hack that will result in a permanent account ban. I’ve seen plenty of users get banned for attempting to modify the Vanguard service files. The risk/reward ratio is completely wrong.

Hardware Upgrade Recommendations for Low-End PCs

If you are stuck with a pre-4th Gen Intel or pre-Ryzen 1000 Series CPU, your hardware is a hard blocker. You cannot "enable" fTPM on a CPU that doesn’t have the logic for it.

Your options are:

1. Upgrade the CPU:
   • Intel: Move to 4th Gen Haswell or newer.
   • AMD: Move to Ryzen 1000 series (Summit Ridge) or newer.
2. Add a Discrete TPM 2.0 Chip:
   • Some older motherboards have a TPM header. You can buy a discrete TPM 2.0 chip.
   • Caveat: This will fix VAN 9001, but it may not fix VAN: RESTRICTION. If you get the RESTRICTION error, you likely need the firmware-based TPM, which means a CPU upgrade is unavoidable.
3. Play Non-Vanguard Titles:
   • If you can’t upgrade, consider games that use EAC (Easy Anti-Cheat) or BattlEye, which do not have the same strict TPM 2.0 hardware requirements.

Decision Tree:

• Check CPU.
• If CPU is old (pre-2014) -> Upgrade CPU or switch games.
• If CPU is modern -> Enable PTT/fTPM in BIOS.
• If still error -> Update BIOS.

FAQ

Is TPM 1.1 or 1.2 enough for Valorant?

Definitively No. Vanguard requires TPM Specification Version 2.0. TPM 1.2 is a legacy standard that lacks the cryptographic algorithms and command sets required by modern anti-cheat integrity checks. If tpm.msc shows 1.2, you must switch to a 2.0 compatible mode (fTPM/PTT) if your hardware supports it.

Does Valorant require Secure Boot on Windows 10?

Secure Boot is not a hard requirement for the game files themselves, but it is almost always required to enable TPM 2.0 in the BIOS on modern UEFI systems. Most UEFI firmware boards will not let you enable PTT or fTPM if Secure Boot is disabled. So, while you might technically play the game with Secure Boot off (if TPM is somehow enabled), you’ll likely need it on to get the TPM working in the first place.

How to check if my motherboard supports TPM 2.0?

Use tpm.msc. If it shows "No TPM," check your BIOS for "PTT" (Intel) or "fTPM" (AMD). If you see those options, your motherboard supports TPM 2.0 via firmware. If you don’t see those options and your CPU is older than 4th Gen Intel / Ryzen 1000, your hardware likely predates TPM 2.0 support and cannot run Vanguard.

Conclusion

Navigating the TPM 2.0 requirement for Valorant can feel like decoding an ancient artifact