Fix Valorant error VAN 1067

Error VAN 1067 usually stops Valorant right at launch and shows you a message from Riot Vanguard, the game's anti-cheat system. The good news up front: nothing is broken and your account is not banned. VAN 1067 almost always just means that on Windows 11 two of your PC's security features that Vanguard strictly needs are turned off - TPM 2.0 and Secure Boot. In this guide we fix error VAN 1067 and enable both step by step, without you needing any technical background and without any data being lost.

What does error VAN 1067 mean?

VAN 1067 is an error code from Riot Vanguard. Vanguard is the anti-cheat program that runs in the background and ensures no one plays with cheats in Valorant. So that Vanguard can work securely, Riot requires two hardware features on Windows 11: an enabled TPM 2.0 (Trusted Platform Module) and switched-on Secure Boot. If both or one of them is disabled, Vanguard refuses to start and throws exactly this error.

Important to understand: VAN 1067 appears almost exclusively on Windows 11. On Windows 10, Vanguard usually does not impose this requirement. So anyone who recently upgraded to Windows 11 or uses a new PC with Windows 11 and suddenly sees this error has, very likely, simply not enabled TPM or Secure Boot yet. Every Windows 11-capable machine supports these features - on many PCs they are just not switched on.

So the error has nothing to do with your Valorant account, your internet connection or the Riot servers. If you are unsure with other launch problems whether it is your PC or Riot, a look at the Valorant server status is worthwhile beforehand. With VAN 1067, though, the cause is practically always local on your own machine.

Why does Vanguard require TPM 2.0 and Secure Boot?

Both features make it considerably harder for cheat developers to deeply manipulate the operating system. Secure Boot ensures that at boot only trustworthy, signed software is loaded. TPM 2.0 is a small security chip on the mainboard that protects cryptographic keys. Together they form a trusted startup environment. This is exactly what Vanguard builds on to fend off manipulated drivers and kernel cheats. These features are part of the official Windows 11 requirements anyway - so Valorant only uses what Microsoft mandates for Windows 11 in any case.

Before you start: check the current state

Before you change anything in the BIOS, a quick look at what is already active on your PC is worthwhile. That saves time and you know exactly which switch to flip.

1. Press Windows key + R at the same time. The small "Run" window opens.
2. Type tpm.msc and confirm with Enter.
3. The TPM management opens. If it says "The TPM is ready for use", your TPM is active. In the details you ideally see 2.0 under "Specification version".
4. If instead "Compatible TPM cannot be found" appears, TPM is disabled in the BIOS or not switched on yet - we will take care of that in a moment.

You can also quickly check the Secure Boot status: press Windows key + R, type msinfo32 and confirm. In the "System Information" window, look for the line "Secure Boot State". If it says "On", Secure Boot is already active. If it says "Off" or "Unsupported", you have to enable it in the BIOS (and possibly switch from Legacy to UEFI mode first). Note the result of both checks, then you know exactly what to do.

Fix 1: Enable TPM 2.0 in the BIOS/UEFI

If the check showed that TPM is not ready for use, you enable it in your mainboard's BIOS/UEFI. That sounds more technical than it is - at its core it is a single switch.

1. Restart your PC and repeatedly press the BIOS key while it boots. Depending on the manufacturer this is usually Del, F2, F10 or Esc. Alternatively you reach the BIOS from within Windows - how that works is below.
2. In the BIOS, find the area for security or advanced settings. The relevant option is named differently depending on the platform.
3. On Intel mainboards the setting is usually called PTT or "Intel Platform Trust Technology". Set it to "Enabled".
4. On AMD mainboards it is usually called fTPM or "AMD CPU fTPM". Set it to "Enabled" as well.
5. Save the change and leave the BIOS - usually with the F10 key ("Save & Exit"). The PC restarts.

After the restart you can check again with tpm.msc whether "The TPM is ready for use" now appears. In many cases VAN 1067 disappears after this single step, because on modern PCs Secure Boot is already active and only the TPM was missing.

Fix 2: Enable Secure Boot

If Secure Boot is still missing, you enable it in the BIOS/UEFI too. One thing matters here: Secure Boot only works if your PC starts in UEFI mode and not in the old Legacy/CSM mode.

1. Go into the BIOS/UEFI (as described above) and find the "Boot" or "Startup" area.
2. Make sure the boot mode is set to UEFI and not to "Legacy". If there is an option called CSM (Compatibility Support Module), switch it to "Disabled".
3. Set - if present - the "OS Type" to Windows UEFI mode.
4. Now find the Secure Boot option (often in the "Security" or "Boot" area) and set it to "Enabled".
5. Save with F10 and leave the BIOS. The PC restarts.

After the restart you check the status again with msinfo32 ("Secure Boot State" should now be "On"). If TPM 2.0 and Secure Boot are both active, Valorant usually starts again without VAN 1067.

How to get into the BIOS/UEFI from Windows 11

If you cannot manage to press the BIOS key quickly at startup, there is a convenient route straight from Windows 11:

1. Open Settings (Windows key + I).
2. Go to System and then to Recovery (on older versions: "Update & Security" -> "Recovery").
3. Under "Advanced startup" click Restart now.
4. The PC starts into a blue menu. There choose Troubleshoot -> Advanced options -> UEFI Firmware Settings -> Restart.
5. The PC now boots directly into the BIOS/UEFI, where you can enable TPM and Secure Boot.

This route is especially helpful if your PC boots very fast and the time window for the BIOS key is hard to hit.

Fix 3: Restart the Vanguard service

Sometimes TPM and Secure Boot have long been active, and Vanguard is still stuck on the old state - for example because the service was not cleanly reloaded since the last start. Then restarting the Vanguard service helps.

1. Press Windows key + R, type services.msc and confirm.
2. In the list, find the entry vgc (the Vanguard client service).
3. Right-click "vgc" -> Restart. If the option is greyed out, first click "Properties" and set the startup type to Automatic, then to "Start".
4. Close Valorant and the Riot client completely and restart the game.

The simplest is often: quit the game completely, restart the PC once and open Valorant again. A full restart "re-arms" Vanguard and freshly reads the changed BIOS settings. Very often VAN 1067 disappears exactly then.

Fix 4: Reinstall Riot Vanguard

If the error remains despite active TPM and Secure Boot, a damaged Vanguard installation can be the cause. A clean reinstall reliably solves such cases.

1. Open the Windows Settings -> Apps -> "Installed apps".
2. Find Riot Vanguard in the list and uninstall it.
3. After that, be sure to restart the PC.
4. Open Valorant again. The Riot client automatically installs Vanguard fresh - after that you usually have to restart once more, then the game launches.

This method is completely harmless: no game data and no skins are deleted. Your inventory sits on the Riot servers and remains untouched.

Fix 5: Update Windows 11 and drivers

An outdated Windows or old drivers can also trigger VAN 1067 or hinder enabling TPM and Secure Boot. Keep both up to date:

• Open Settings -> Windows Update and install all available updates. Restart afterwards.
• Update your graphics drivers (Nvidia, AMD or Intel) via the respective manufacturer software or website.
• Update your mainboard's chipset drivers. It is precisely the BIOS and chipset updates that ensure fTPM/PTT and Secure Boot work reliably.

If your mainboard has an older BIOS, a BIOS update from the manufacturer can be what makes the TPM and Secure Boot options properly available in the first place. Proceed according to the manufacturer's instructions.

The most common causes of VAN 1067 at a glance

Even though TPM and Secure Boot are by far the most common triggers, it is worth sorting the various causes clearly once. That way you find faster which of the fixes above holds your specific solution.

• TPM 2.0 is switched off in the BIOS. By far the most common case. Many mainboards ship PTT or fTPM disabled from the factory, even though the chip is present. Fix 1 solves it.
• Secure Boot is off. The second most common case, often combined with a boot in Legacy mode. Fix 2 solves it.
• The PC boots in Legacy/CSM mode. Then Secure Boot cannot even be enabled while CSM is active. First force UEFI, then enable Secure Boot.
• Vanguard is stuck on the old state. TPM and Secure Boot are already active, but the service was not reloaded. Fix 3 helps.
• The Vanguard installation is damaged. Rare, but possible after aborted updates. Fix 4 (reinstall) clears this up.
• Outdated Windows or old drivers/BIOS. Can block enabling or trigger the error indirectly. Fix 5 covers this.

In practice, fixes 1 and 2 - that is TPM 2.0 and Secure Boot - solve around nine out of ten cases. The remaining steps are meant for the rarer situations in which the hardware features are already active and something still jams.

VAN 1067 after a Windows update

A typical scenario: Valorant ran fine for a long time, and suddenly VAN 1067 appears after a larger Windows update or a switch from Windows 10 to Windows 11. That is no coincidence. With the move to Windows 11 the stricter Vanguard requirements kick in, and sometimes a BIOS or firmware update also resets a previously active setting. In such cases you usually only need to look into the BIOS settings once and check whether TPM and Secure Boot are still as before. Often it is enough to set the one reset switch back to "Enabled".

VAN 1067 on a new or self-built PC

Anyone who assembled or bought a new machine encounters VAN 1067 especially often. Freshly set up systems frequently still start in Legacy mode or have fTPM/PTT off from the factory. Here it is best to go through fixes 1 and 2 directly one after the other: first enable TPM, then set the boot mode to UEFI, disable CSM and switch on Secure Boot. With a fresh Windows installation, make sure you installed Windows in UEFI mode from the start - then the drive is already GPT and the MBR issue is eliminated entirely.

Is enabling TPM and Secure Boot safe?

Yes. Enabling TPM 2.0 and Secure Boot is completely safe and deletes no data - apart from the MBR-to-GPT conversion exception described above. Both features are part of the official Windows 11 requirements anyway. You do not make your PC slower with them, nor do you weaken anything. On the contrary: Secure Boot and TPM increase your system's security.

Very important: never solve VAN 1067 by switching off security features, bypassing Vanguard or installing dubious "fix tools" from third parties. Such routes can endanger your PC and, in the worst case, lead to an account ban. The right way is always to simply enable the features required by Windows and Vanguard normally - which is exactly what we did here.

If it still jams afterwards

If Valorant still does not start after all the steps, work through the following points one by one:

• Check again with tpm.msc and msinfo32 whether TPM 2.0 is really "ready for use" and the "Secure Boot State" really "On". Sometimes a BIOS setting was not saved.
• Make sure that in the BIOS CSM/Legacy is really disabled and UEFI mode is active.
• Repeat Fix 3 (Vanguard service) and Fix 4 (reinstall) after a fresh restart.
• To be safe, sign in to Riot completely fresh once. Help on this is on our page about Valorant login.
• If you get stuck, Valorant Support is the right point of contact - there you can describe your case with the exact error messages.

Anyone just starting out with Valorant who still struggles with the client, Vanguard and the first settings finds a calm step-by-step introduction in our Valorant beginner guide. There we also explain how Vanguard fundamentally works and why it runs along at system startup.

VAN 1067 and other Vanguard errors

VAN 1067 is only one of several error codes that begin with the "VAN" prefix and all come from Riot Vanguard. It helps to place your own case correctly so you do not search at the wrong end. While VAN 1067 refers very specifically to missing TPM 2.0 and Secure Boot, other codes point to completely different causes - such as a crashed service, a needed restart or a compatibility problem with other software.

The key message: always read the exact number and text of the message. Just because two errors both start with "VAN" does not mean they have the same solution. For VAN 1067 the path is clear and unambiguous - turn on TPM and Secure Boot. If instead you see a different VAN code, other steps often apply, such as a simple restart of the PC or closing programs that intervene deeply in the system. When in doubt, note down the complete wording of the message before you begin troubleshooting or contact support.

A common accompanying error is the prompt to restart the PC because Vanguard is not yet armed after installation or an update. That is completely normal: Vanguard anchors itself at system startup and therefore needs a fresh boot after every larger change. Anyone who skips this restart sometimes sees error messages that dissolve into thin air after a single clean restart.

After the fix: everything back under control

Once VAN 1067 is dealt with and Valorant starts again, it is worth briefly checking two things. First: does the success last? Restart the PC a few times and open the game to make sure the BIOS settings were really saved and do not reset at every start. Second: use the opportunity to tidy up your Riot client and your security settings once - such as checking two-factor authentication if you have not enabled it yet.

If all settings are stable, Vanguard runs unobtrusively in the background from now on. You normally never have to deal with TPM or Secure Boot again, as long as you do not swap the mainboard, reset the BIOS or reinstall Windows completely. In those cases the options may jump back to factory settings - then, thanks to this guide, you already know the short way back.

Terms briefly explained

So that you do not guess what the individual options mean in the BIOS, here are the most important terms in simple words:

• BIOS/UEFI - the base program of your mainboard that starts before Windows. UEFI is the modern variant of the classic BIOS. Here you set fundamental hardware options.
• TPM 2.0 - a security chip that stores cryptographic keys. On Intel systems often implemented as the firmware feature "PTT", on AMD as "fTPM".
• Secure Boot - ensures that at startup only trustworthy, signed software is loaded.
• CSM/Legacy - an old compatibility mode. If it is active, Secure Boot cannot be used. For Windows 11 it should be off.
• MBR and GPT - two partition styles for drives. GPT belongs to UEFI and Secure Boot, MBR to the old Legacy start.
• vgc - the name of the Vanguard service in the Windows service management.

With this vocabulary you find your way in almost any BIOS, even if the menus look somewhat different depending on the manufacturer. The names of the options, however, are similar everywhere.

Myths around VAN 1067

Some half-truths circulate online around the error. You should be able to place these:

• "VAN 1067 is a ban." Wrong. It is a pure configuration hint and has nothing to do with your account.
• "You have to disable Vanguard completely." Wrong and dangerous. Without Vanguard, Valorant does not start at all. The right way is to switch on the required features, not to turn off the anti-cheat.
• "TPM slows down my PC." Wrong. The chip has no noticeable influence on in-game performance whatsoever.
• "I need new hardware." Usually wrong. Every Windows 11-capable PC already has TPM 2.0 and Secure Boot support on board - they are just not switched on.

Do not let such claims lure you into risky actions. The clean solution is always the one we described here step by step.

Quick checklist against VAN 1067

1. Check status: tpm.msc (TPM 2.0 ready for use?) and msinfo32 (Secure Boot State "On"?).
2. Enable TPM: in the BIOS set PTT (Intel) or fTPM (AMD) to "Enabled".
3. Enable Secure Boot: boot mode to UEFI, CSM off, OS Type "Windows UEFI mode", Secure Boot "Enabled".
4. Mind the drive: if MBR, carefully convert to GPT with mbr2gpt, backup first.
5. Restart Vanguard: services.msc -> vgc -> Restart, or restart the PC completely.
6. If needed: uninstall Riot Vanguard, restart, Valorant reinstalls it fresh.
7. Keep up to date: Windows Update, GPU and chipset drivers, possibly a BIOS update.

With these steps VAN 1067 is resolved in almost all cases. As soon as Valorant runs again, you can also turn back to your locker. By the way: the free Valorant-Spind reads your inventory and shows you the euro value of all your skins at a glance - ideal to get an overview of your collection again after the fix.

Frequently asked questions (FAQ)

What does error VAN 1067 mean in Valorant?

VAN 1067 is a Riot Vanguard error that occurs almost only on Windows 11. It means Vanguard requires enabled TPM 2.0 and Secure Boot, but these are currently switched off. As soon as you enable both in the BIOS, Valorant starts again.

How do I enable TPM 2.0 for Valorant?

Boot into the BIOS/UEFI and find the TPM option. On Intel boards it is called PTT or Intel Platform Trust Technology, on AMD boards fTPM or AMD CPU fTPM. Set it to Enabled, save with F10 and restart. With tpm.msc you can then check the status.

How do I turn on Secure Boot?

In the BIOS/UEFI the boot mode must be set to UEFI (not Legacy/CSM). Disable CSM, set OS Type to Windows UEFI mode and set Secure Boot to Enabled. Save and restart. You check the status in Windows with msinfo32 under Secure Boot State.

Does enabling TPM and Secure Boot delete my data?

No. Switching on both features is harmless and deletes no data. Caution only if your drive is still MBR instead of GPT: then the switch to UEFI can make Windows unbootable. Convert the drive with mbr2gpt beforehand and make a backup.

Is VAN 1067 an account ban?

No. VAN 1067 has nothing to do with your account and is not a ban. It is purely a hint that your Windows 11 PC is still missing the security features TPM 2.0 and Secure Boot that Vanguard requires.

What to do if VAN 1067 remains after enabling?

Restart the Vanguard service vgc via services.msc or restart the PC completely. If that does not help, uninstall Riot Vanguard, restart and let it install fresh when you open Valorant. Also keep Windows and your drivers up to date.