VAN 1067 is a Riot Vanguard error: according to Riot Support, Vanguard ran into an unexpected issue while starting or checking in with your system. Riot recommends a Windows update, unplugging controllers, running the Riot Client as admin, setting the Vanguard service to "Automatic", a clean boot and, if needed, reinstalling Vanguard. Vanguard reports TPM 2.0 and Secure Boot with their own codes (VAN 9001 and VAN 9003) – only then do you need the BIOS. Details in Riot’s support article on 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. According to Riot Support, VAN 1067 usually means Vanguard ran into an unexpected issue while starting or checking in with your system. Riot’s steps for it don’t mention TPM 2.0 or Secure Boot – those have their own codes (VAN 9001 and VAN 9003). In this guide, we go through Riot's official steps in order and explain in a separate section what to do in the BIOS for VAN 9001 or VAN 9003 – no technical background needed, and without losing any data.
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. According to Riot's official support article (as of July 2026), VAN 1067 usually means Vanguard ran into an unexpected issue while starting or checking in with your system. Riot recommends nine steps for it – from a Windows update to reinstalling the game – which you’ll find in order further below. Separately, Vanguard requires two security features on Windows 11: an enabled TPM 2.0 (Trusted Platform Module) and Secure Boot turned on. If they’re missing, Vanguard reports its own codes: VAN 9001 for TPM and VAN 9003 for Secure Boot.
Important to understand: according to Riot, TPM 2.0 and Secure Boot are mandatory on Windows 11. On Windows 10, Vanguard can also require TPM 2.0, Secure Boot, Memory Integrity (HVCI) or IOMMU via “VAN: RESTRICTION”. If one of these features is missing, Riot says Vanguard reports its own codes – VAN 9001, VAN 9003 or VAN: RESTRICTION – and there’s a separate BIOS section for those further below. Every Windows 11-capable machine supports TPM 2.0 and Secure Boot – on many PCs they just aren’t turned on.
So the error has nothing to do with your Valorant account and isn’t a ban. With VAN 1067, Riot’s steps focus mainly on your PC – Riot only has you check your internet connection in step eight. If you’re having other launch problems and aren’t sure whether it’s your PC or Riot, take a look at the Valorant server status first.
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 only trusted, signed software is loaded at boot. TPM 2.0 is a small security chip on the motherboard 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.
VAN 1067 in brief
- Cause per Riot: Vanguard hit an unexpected issue while starting or checking in with your system.
- Riot’s fix: update Windows, unplug controllers, run the Riot Client as admin, set the Vanguard service to “Automatic”, clean boot, scan for malware, reinstall Vanguard, check your connection, reinstall the game.
- Don’t mix them up: Vanguard reports a missing TPM 2.0 or Secure Boot as VAN 9001 or VAN 9003 – only then do you go into the BIOS.
- Harmless: no account ban, no deleted data.
Riot's official steps against VAN 1067
Riot's official support article (as of July 2026) recommends this order. Work through it from top to bottom and restart Valorant after each step:
- Update Windows – install all available updates and restart.
- Unplug controllers – temporarily disconnect gamepads and other USB input devices.
- Run the Riot Client as administrator.
- Set the Vanguard service to “Automatic” – open services.msc, find “vgc”, set startup type to “Automatic” (unless you use Riot’s Vanguard Pre-Check, which runs Vanguard on demand).
- Perform a clean boot – start Windows with only the essential services to rule out conflicts with other software.
- Scan your PC for malware.
- Uninstall and reinstall Riot Vanguard.
- Check your internet connection.
- Reinstall Valorant.
If none of the steps help, Riot recommends submitting a ticket to Player Support with your logs, which you collect with the Riot Repair Tool. The following fixes explain the key steps in detail – you only need BIOS settings if Vanguard explicitly mentions TPM or Secure Boot or reports VAN 9001 or VAN 9003.
🔐 If Valorant shows VAN 9001, VAN 9003 or VAN:RESTRICTION instead of VAN 1067, TPM 2.0, Secure Boot or another Windows protection feature is missing. The detailed guide with BIOS paths and MBR to GPT is at Valorant: enable Secure Boot & TPM 2.0.
Fix 1: Update Windows and drivers
Riot’s first step against VAN 1067: install all available Windows updates and restart. Up-to-date drivers don’t hurt either – though Riot doesn’t list them for VAN 1067:
- Open Settings → Windows Update and install all available updates. Restart afterward.
- Update your graphics drivers (Nvidia, AMD or Intel) via the respective manufacturer software or website.
- Update your motherboard's chipset drivers. BIOS and chipset updates can also help fTPM/PTT and Secure Boot work reliably – useful if Vanguard ever reports VAN 9001 or VAN 9003.
If your motherboard 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. Follow the manufacturer's instructions.
Fix 2: Check and restart the Vanguard service
Riot’s fourth step concerns the Vanguard service “vgc”: it has to be running when you play. If it isn’t set to “Automatic” or has been stuck since the last start, restarting the service helps. Before that, Riot recommends unplugging controllers and unneeded USB devices and running the Riot Client as administrator.
- Press Windows key + R, type services.msc and confirm.
- In the list, find the entry vgc (the Vanguard client service).
- Right-click "vgc" → Restart. If the option is grayed out, first click "Properties" and set the startup type to Automatic, then click "Start". Riot’s exception: if you use Vanguard Pre-Check, which runs Vanguard on demand, you don’t need to change the startup type.
- Close Valorant and the Riot client completely and restart the game.
Often the simplest fix: quit the game completely, restart the PC once and open Valorant again. A full restart loads Vanguard fresh. If that doesn’t help, Riot’s next steps are a clean boot and a malware scan before you reinstall Vanguard.
Fix 3: Reinstall Riot Vanguard
If the error persists after a clean boot and malware scan, a damaged Vanguard installation can be the cause. Riot lists reinstalling as step seven:
- Open the Windows Settings → Apps → "Installed apps".
- Find Riot Vanguard in the list and uninstall it.
- After that, be sure to restart the PC.
- Open Valorant again. The Riot Client automatically reinstalls Vanguard – after that, you usually have to restart once more, and 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.
Only for VAN 9001 or 9003: check TPM 2.0 & Secure Boot
This section isn’t about VAN 1067 itself: Vanguard reports a missing TPM 2.0 as VAN 9001 and a missing Secure Boot as VAN 9003. If you see one of these codes, take a quick look at what’s already active on your PC before you change anything in the BIOS. That saves time, and you’ll know exactly which switch to flip.
- Press Windows key + R at the same time. The small "Run" window opens.
- Type tpm.msc and confirm with Enter.
- The TPM Management console opens. If it says "The TPM is ready for use", your TPM is active. Ideally, the details show 2.0 under "Specification version".
- If instead "Compatible TPM cannot be found" appears, TPM is disabled in the BIOS or hasn’t been turned on yet – we’ll 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 results of both checks – then you’ll know exactly what to do.
Enable TPM 2.0 in the BIOS/UEFI (VAN 9001)
If the check showed that TPM isn’t ready for use, enable it in your motherboard's BIOS/UEFI. That sounds more technical than it is – at its core it is a single switch.
- 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 can get into the BIOS from within Windows – see below for how.
- In the BIOS, find the section for security or advanced settings. The relevant option is named differently depending on the platform.
- On Intel motherboards the setting is usually called PTT or "Intel Platform Trust Technology". Set it to "Enabled".
- On AMD motherboards it is usually called fTPM or "AMD CPU fTPM". Set it to "Enabled" as well.
- 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. Once the TPM is ready, launch Valorant again – that’s all Riot asks for with VAN 9001.
Enable Secure Boot (VAN 9003)
If Vanguard reports VAN 9003, Secure Boot is 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.
- Enter the BIOS/UEFI (as described above) and find the "Boot" or "Startup" section.
- 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".
- If present, set the "OS Type" to Windows UEFI mode.
- Now find the Secure Boot option (often in the "Security" or "Boot" area) and set it to "Enabled".
- Save with F10 and leave the BIOS. The PC restarts.
After the restart, check the status again with msinfo32 ("Secure Boot State" should now be "On"). If TPM 2.0 and Secure Boot are both active, VAN 9001 and VAN 9003 should no longer appear.
Important note about the drive (MBR vs. GPT)
Secure Boot needs the UEFI boot mode, and that in turn requires a drive in GPT format. If your Windows drive is still in the old MBR format, simply switching to UEFI can cause Windows to no longer start.
The good news: the vast majority of Windows 11 PCs already use GPT and UEFI anyway – then this does not concern you at all. If your drive is MBR after all, Microsoft's free tool mbr2gpt offers a safe way to convert it to GPT without losing the data. Still, proceed carefully and make a backup of your important files beforehand. When in doubt, check the format in Windows Disk Management (right-click the disk, "Properties", "Volumes" tab, "Partition style" line).
How to get into the BIOS/UEFI from Windows 11
If you can’t hit the BIOS key fast enough at startup, there’s a convenient route straight from Windows 11:
- Open Settings (Windows key + I).
- Go to System and then to Recovery (on older versions: "Update & Security" → "Recovery").
- Under "Advanced startup" click Restart now.
- The PC restarts into a blue menu. Choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.
- 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.
The most common causes of VAN 1067 at a glance
Riot doesn’t say how often each cause occurs, but its steps show where the causes lie. It’s worth sorting them out once – that way, you’ll find faster which of the fixes above solves your problem.
- The Vanguard service isn’t starting or is stuck. Riot’s steps 3 and 4: run the Riot Client as administrator, set the “vgc” service to “Automatic”. Fix 2 helps.
- Conflict with other software. Background programs or malware interfere with Vanguard – Riot recommends a clean boot and a malware scan (steps 5 and 6).
- Corrupted Vanguard installation. Fix 3 (reinstall) clears this up.
- Outdated Windows. Riot’s first step: install all updates and restart. Fix 1 covers this.
- Connected controllers or USB devices. Riot suggests unplugging them for a test (step 2).
- Connection or corrupted game files. Riot’s last steps: check your connection and reinstall Valorant.
- Only if the message mentions TPM or Secure Boot or you see VAN 9001 or VAN 9003: check the BIOS – see the separate section above.
Read the exact code and wording of the message: for VAN 1067 you start with Riot’s official steps; if Vanguard mentions TPM or Secure Boot or shows VAN 9001 or VAN 9003, the BIOS section helps.
VAN 1067 after a Windows update
A typical scenario: Valorant ran fine for a long time, and suddenly VAN 1067 appears after a major Windows update. First check whether updates are still pending, install them and restart – that’s Riot’s first step – then work through the remaining steps. If Vanguard instead reports VAN 9001 or VAN 9003 after a switch to Windows 11 or a BIOS update, TPM or Secure Boot may have been reset. Then it’s often enough to set that one switch back to “Enabled” in the BIOS.
VAN 1067 on a new or self-built PC
On a new or self-built machine, the rule for VAN 1067 is the same: Riot’s steps first. Newly set-up systems, though, often still boot in Legacy mode or have fTPM/PTT turned off out of the box – on Windows 11, Vanguard reports that as VAN 9001 or VAN 9003. Then work through the BIOS section above: 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. They won’t slow your PC down or 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. Shortcuts like these can put your PC at risk and, in the worst case, get your account banned. The right way is always to simply enable the features Windows and Vanguard require the normal way – which is exactly what we did here.
If it still doesn’t work
If Valorant still won’t start after all these steps, work through the following points one by one:
- Go through Riot’s nine steps again in order and launch Valorant after each step.
- Repeat Fix 2 (Vanguard service) and Fix 3 (reinstall) after a fresh restart.
- If Vanguard reported VAN 9001 or VAN 9003 along the way, check with tpm.msc and msinfo32 whether TPM 2.0 is really “ready for use” and the “Secure Boot State” really “On” – and whether CSM/Legacy is disabled in the BIOS. Sometimes a BIOS setting wasn’t saved.
- To be safe, sign out of Riot completely and sign back in once. Help on this is on our page about Valorant login.
- If you’re still stuck, Riot recommends submitting a ticket to Player Support with your logs from the Riot Repair Tool. How that works is on our Valorant support page.
If you’re just starting out with Valorant and still struggling with the client, Vanguard and your first settings, you’ll find a calm step-by-step introduction in our Valorant beginner guide. There, we also explain how Vanguard works and why it starts along with your system.
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 identify your case correctly so you don’t look in the wrong place. While, according to Riot, VAN 1067 stands for an unexpected issue during Vanguard startup, other codes (overview: all Valorant VAN error codes with fixes) point to completely different causes – such as a missing TPM 2.0 (VAN 9001), missing Secure Boot (VAN 9003), a virtual machine (VAN 138) or a hardware ban (VAN 152).
The key takeaway: 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: Riot's official steps in order; TPM and Secure Boot concern VAN 9001 and VAN 9003. If instead you see a different VAN code, other steps often apply, such as simply restarting your PC or closing programs that dig deep into the system. When in doubt, write down the full wording of the message before you begin troubleshooting or contact support.
A common related message is the prompt to restart your PC because Vanguard isn’t active yet after an installation or update. That’s completely normal: Vanguard loads at system startup and therefore needs a fresh boot after every major change. If you skip this restart, you may see error messages that vanish after a single clean restart. If something still isn’t working afterward, our Valorant tech fix guide helps.
After the fix: everything back under control
Once VAN 1067 is fixed and Valorant starts again, it’s worth quickly checking two things. First: does the fix stick? 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 security settings – for example, enable two-factor authentication if you haven’t 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 motherboard, 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 quick way back.
Terms briefly explained
So you don’t have to guess what the individual BIOS options mean, here are the most important terms in plain English:
- BIOS/UEFI – the firmware of your motherboard that starts before Windows. UEFI is the modern successor to the classic BIOS. This is where you set basic hardware options.
- TPM 2.0 – a security chip that stores cryptographic keys. On Intel systems, it’s often implemented as the firmware feature "PTT"; on AMD, as "fTPM".
- Secure Boot – ensures that only trusted, signed software is loaded at startup.
- 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 Windows Services.
With this vocabulary, you’ll find your way around almost any BIOS, even if the menus look a bit different depending on the manufacturer. The option names, however, are similar everywhere.
Myths around VAN 1067
A few half-truths about this error circulate online. Here’s how to tell fact from fiction:
- "VAN 1067 is a ban." Wrong. It is a technical Vanguard startup error on your PC 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. Riot’s steps against VAN 1067 need no new hardware, and every Windows 11-capable PC already has TPM 2.0 and Secure Boot support on board – with VAN 9001 or VAN 9003 they are just not switched on.
Don’t let claims like these lure you into anything risky. The clean solution is always the one we described here step by step.
Quick checklist against VAN 1067
- Update Windows: install all updates and restart.
- Unplug controllers and unneeded USB devices, run the Riot Client as administrator.
- Vanguard service: services.msc → vgc → startup type “Automatic” (unless you use Vanguard Pre-Check), then restart the service or the PC.
- Perform a clean boot and scan your PC for malware.
- If needed: uninstall Riot Vanguard and restart – Valorant reinstalls it automatically; then check your connection and reinstall Valorant if necessary.
- Only for VAN 9001/9003: check tpm.msc and msinfo32, enable PTT (Intel) or fTPM (AMD) and Secure Boot in the BIOS (UEFI mode, CSM off; if MBR, convert to GPT with mbr2gpt first, backup).
- Still no luck? Submit a ticket to Riot Support with your logs (Riot Repair Tool).
With these steps you’ve covered everything Riot recommends against VAN 1067. As soon as Valorant runs again, you can get 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 for getting an overview of your collection again after the fix.
Running again? See what your locker is worth
As soon as Valorant starts, Valorant-Spind shows you the euro value of your skins and coaching from real matches – locally, without login, for free.
🎮 Download Valorant-Spind for free🧹 Nothing helps? Then set up Valorant and Vanguard fresh – step by step: uninstall & reinstall Valorant.
Frequently asked questions (FAQ)
What does error VAN 1067 mean in Valorant?
VAN 1067 is a Riot Vanguard error. According to Riot Support, Vanguard ran into an unexpected issue while starting or checking in with your system. Follow Riot's steps (update Windows, set the Vanguard service to “Automatic”, clean boot, reinstall Vanguard). TPM 2.0 and Secure Boot have their own codes (VAN 9001 and VAN 9003).
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 can 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. Only be careful 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 a technical Vanguard startup error on your PC.
What if VAN 1067 remains after Riot’s steps?
Go through Riot’s steps again in order and launch Valorant after each one – especially the vgc service set to Automatic, a clean boot and reinstalling Vanguard. If the error persists, Riot recommends a Player Support ticket with your logs from the Riot Repair Tool.
