Have you been met with the Valorant TPM 2.0 Error? Valorant players continue to report TPM 2.0 incidents caused by a VAN9001 Secure Boot Issue. So, how do you fix it?
Just like the frustrating Valorant Error Code Van-81, the TPM 2.0 error can leave you unable to play Valorant. However, where it differs is that you can't even open up Valorant with this boot issue.
In an effort to tighten up security on the game, and overcome the insidious scourge of cheating, Riot Games are constantly looking for ways to make their game more secure. But sometimes, the results impact honest players, rather than the intended targets.
In an effort to reduce the collateral damage, we've come up with a few suggestions, to help you sort out this particular problem. You'll be back in action in no time, with these tips.
How To Fix Valorant TPM 2.0 Error
In order to fix this issue, gamers need to ensure that they have enabled both TPM and Secure Boot on their computers. To do this:
- Start by opening BIOS. You can either press delete during the bootup process, or follow these steps:
- Go to Settings > Update and Security > Recovery
- Under Advanced Startup, hit Restart Now
- Your computer will reboot to a new menu
- Select Troubleshoot > Advanced Options> UEFI Firmware Settings> Restart
- This will then give you access to BIOS
- Once in BIOS, make sure it is in advanced mode, and then make sure that TPM is enabled. On AMD builds, this will be labelled as TPM, while Intel builds will show PTT.
- Once you've enabled TPM, find Secure Boot. This will usually be under a Boot Tab, but it can vary.
- Once found, enable Secure Boot.
- After enabling Secure Boot, set it to Standard to allow it to run on your PC.
- Save and exit to confirm the changes.
Once you've completed these steps, the VAN9001 Secure Boot problem should be a thing of the past. But it's worth reading on, to fully understand what you've just done.
Read More: Valorant Ping Fix: How To Fix High Ping In Valorant
What Is Valorant TPM 2.0 Error?
As we mentioned earlier, Riot Games are constantly trying to find ways to combat cheating in Valorant. A recent innovation has been to use Secure Boot and TPM. TPM 2.0 is a security feature which is common on many computers, and compulsory on Windows 11. Secure Boot meanwhile, is another security software that only allows trusted software to boot.
This error has primarily been affecting players who have been using a preview version of Windows 11. Riot Games are taking this opportunity to enforce these security features, as they make it considerably harder for players to cheat. If you are on Windows 11, you won't be able to play Valorant without TPM 2.0 active. Indeed, this isn't exclusive to Valorant, with Windows 11 TPM Error also frustrating users who upgraded to the latest version.
While this may be irritating to some, it is arguably necessary to crack down on cheating. Because that's even more irritating than having to change a few settings on your computer. But if you are struggling, then reach out to Riot Games for additional support. You can also find them on Twitter @RiotSupport.
Hopefully, you won't need to contact them because one of our solutions has worked for you. But it's nice to know they are there if you need them.
What is Secure Boot?
As I mentioned earlier, the Vanguard anti-cheat system used in Valorant is designed to operate at the kernel-level of your computer's operating system. This means that it has elevated privileges to monitor and block any suspicious activity that may occur within the game.
In order to ensure the integrity of Vanguard, Riot Games has implemented a security feature called "secure boot" on both Windows and macOS systems. Secure boot is a technology that prevents the loading of unauthorized operating systems, drivers, and software during the boot process.
When you encounter a secure boot error while trying to launch Valorant, it means that Vanguard is unable to start because it has detected an issue with the secure boot configuration on your system.
Since you are here, have a look at how to fix Valorant screen tearing and low client FPS error.