🔧 Valorant Error Fix · 8 Proven Fixes

How to Fix Valorant VAN 1067: TPM 2.0 and Secure Boot Error

By GameAddaUpdated November 1, 20268 min read

You launch Valorant on Windows 11 and instead of the main menu you get VAN 1067, telling you that this build of Vanguard requires TPM 2.0 and Secure Boot to be enabled. In plain English, VAN 1067 means Vanguard checked your PC for two security features and the check failed. TPM 2.0 is a security chip (or a built-in processor feature) that stores encryption keys, and Secure Boot is a BIOS setting that makes sure your PC only boots trusted software. On Windows 11, Valorant requires both, because they prove your PC booted cleanly and was not tampered with before the anti-cheat loads. If either one is off, undetected, or misconfigured, Vanguard refuses to run and Valorant stops right there.

The good news is that VAN 1067 is almost never missing hardware. Most PCs built since 2016 already have TPM built into the processor — Intel calls it PTT and AMD calls it fTPM — and it is simply switched off in BIOS. The same goes for Secure Boot: it is usually present but disabled, or blocked because the PC is still booting in Legacy mode. That is why the fixes below start with two quick Windows checks that tell you exactly which half of the problem you have, then move into the BIOS settings that solve it. Work through them in order and test a Valorant launch after each change, so you know which setting did it.

What causes Valorant VAN 1067?

Vanguard runs its compliance check before Valorant starts, and it fails when any of these are true:

TPM disabled in BIOS — the most common cause. Your processor has TPM (Intel PTT or AMD fTPM), but the BIOS setting is off, so Windows cannot see it.
Secure Boot disabled in BIOS — Secure Boot is off, or set to a custom mode Vanguard does not accept.
Legacy boot mode instead of UEFI — Secure Boot only works under UEFI. A PC booting in Legacy or CSM mode cannot enable Secure Boot at all.
Outdated BIOS firmware — older firmware may not detect TPM correctly, or may hide the Secure Boot options entirely.
BIOS settings reset — a BIOS update, a dead CMOS battery, or a cleared CMOS can silently turn TPM or Secure Boot back off.
Vanguard service stuck or corrupted — the vgc service fails to start, or Vanguard's files are damaged, so the check fails even though the hardware is fine.
A Windows 11 upgrade that skipped the checks — upgrading from Windows 10 without meeting the requirements leaves TPM or Secure Boot off while Valorant now demands them.

Quick check first: Before changing any BIOS setting, run the two Windows checks in Fixes 1 and 2. They take two minutes and tell you whether you need TPM, Secure Boot, or both — so you change exactly one setting instead of guessing through your whole BIOS.

1Check your TPM 2.0 status in Windows

Press Windows + R, type tpm.msc, and press Enter. The TPM Management window tells you the truth about your hardware:

If it says "The TPM is ready for use" and shows Specification Version 2.0, your TPM is fine — skip to Fix 2, because Secure Boot is your problem.
If it says "Compatible TPM cannot be found", TPM is disabled in BIOS or your hardware truly lacks it — go to Fix 3.

This one check splits VAN 1067 in half, so do not skip it. Players who jump straight into BIOS often change the wrong setting and end up back at the same error.

2Check Secure Boot state in System Information

Press Windows + R, type msinfo32, and press Enter. Look for two lines:

Secure Boot State — should say On. If it says Off or Unsupported, you need Fix 4.
BIOS Mode — should say UEFI. If it says Legacy, Secure Boot cannot be enabled until you fix that with Fix 5.

If TPM is ready and Secure Boot State is already On, your hardware is fine and Vanguard itself is the problem — jump to Fix 7. Otherwise, the BIOS fixes below are your path.

3Enable TPM in BIOS or UEFI settings

Restart your PC and enter BIOS setup — usually by pressing Delete, F2, or F12 during boot (your motherboard's splash screen shows the key). The TPM setting hides under different names depending on your processor:

Intel: look for PTT (Platform Trust Technology) under Security or Advanced.
AMD: look for fTPM under Security, Advanced, or AMD CBS settings.

Set it to Enabled, save, and exit. When Windows boots again, open tpm.msc and confirm it now says the TPM is ready for use with Specification Version 2.0.

4Enable Secure Boot in BIOS

Back in BIOS setup, open the Boot or Security tab and find Secure Boot. Set it to Enabled. Two common gotchas:

On some boards you must first set OS Type to Windows UEFI mode before the Secure Boot option becomes changeable.
If Secure Boot Mode offers Standard and Custom, choose Standard — Vanguard accepts the standard Microsoft keys, while a custom key set can fail the check.

Save and exit, then open msinfo32 again and confirm Secure Boot State now says On. If the option is greyed out entirely, your BIOS Mode is Legacy — that is Fix 5.

5Switch from Legacy boot to UEFI if needed

Secure Boot only exists under UEFI, so a PC booting in Legacy or CSM mode cannot enable it no matter what you toggle. The fix is to convert your system disk from MBR to GPT and switch the boot mode:

Back up anything important first — this step changes your disk layout, and a backup turns a rare failure into a minor inconvenience.
Boot into Windows Recovery (Settings, System, Recovery, Advanced startup, Restart now), open Command Prompt, and run mbr2gpt /validate and then mbr2gpt /convert.
Restart into BIOS, change the boot mode from Legacy or CSM to UEFI, and enable Secure Boot as in Fix 4.

After the switch, msinfo32 should show BIOS Mode as UEFI and Secure Boot State as On. This is the most involved fix on the list, but it is also the one that permanently ends VAN 1067 for older PCs that were set up in Legacy mode.

Do not force the MBR-to-GPT conversion on a disk you have not backed up. The built-in MBR2GPT tool is designed for this exact job and usually finishes in under a minute, but a power cut mid-conversion can leave the disk unbootable. A backup first, and a charger plugged in for laptops, makes this step safe.

6Update your BIOS firmware

If TPM is enabled and Secure Boot is on yet VAN 1067 persists, your firmware may be misreporting one of them to Vanguard. Visit your motherboard or laptop maker's support page, find your exact model, and download the latest BIOS. Follow their update instructions exactly — usually a file on a USB drive and the built-in BIOS flash tool — and do not power off during the update. Newer firmware commonly fixes TPM detection bugs and exposes Secure Boot options that older versions hid. After the update, re-check tpm.msc and msinfo32 before launching Valorant, since an update can reset BIOS settings to defaults and turn TPM or Secure Boot back off.

7Restart the Vanguard service and repair Vanguard

If both Windows checks are green and VAN 1067 still appears, Vanguard itself is failing the check. First, open Task Manager, go to the Services tab, and confirm vgc is running — if it is stopped, right-click it and start it. If that does not help, repair Vanguard: uninstall Riot Vanguard from Windows Settings (Apps, then Installed apps), then relaunch Valorant so the client installs a fresh copy automatically. Restart your PC after the reinstall so the Vanguard service starts cleanly, then try launching again. This replaces corrupted anti-cheat files that can fail the compliance check even on a perfectly configured PC.

8Reinstall Valorant clean as a last resort

If nothing above worked, do a clean reinstall: uninstall Valorant and the Riot Client, restart your PC, and install fresh from Riot's official site. Your account, skins, agents, Battle Pass progress, and rank live on Riot's servers, so a reinstall loses nothing you earned — it only replaces local game files. After reinstalling, launch the Riot Client as administrator for the first login, so Vanguard installs with the permissions it needs from the start.

Quick checklist

☐ TPM checked in tpm.msc — ready for use, Specification Version 2.0
☐ Secure Boot State On and BIOS Mode UEFI in msinfo32
☐ TPM enabled in BIOS (Intel PTT or AMD fTPM)
☐ Secure Boot enabled in BIOS, Standard mode
☐ Legacy boot converted to UEFI (MBR to GPT) if BIOS Mode said Legacy
☐ BIOS firmware updated, settings re-checked after the update
☐ Vanguard service running, Vanguard repaired, PC restarted
☐ Clean reinstall only if every fix above failed

Frequently asked questions

What does Valorant VAN 1067 mean in plain English?

It means Vanguard, Valorant's anti-cheat, checked your PC for TPM 2.0 and Secure Boot and the check failed. On Windows 11, Valorant requires both to be enabled, because they prove your PC booted securely and was not tampered with. If either is off or undetected, Vanguard refuses to run and Valorant shows VAN 1067.

What is the difference between VAN 1067 and VAN 9001?

Both are about TPM 2.0 and Secure Boot on Windows 11, but they fire at different points. VAN 9001 appears when your system does not meet the requirements, usually because TPM or Secure Boot is disabled. VAN 1067 appears when Vanguard itself fails its compliance check at startup, which can happen even on a capable PC if TPM is not detected, Secure Boot is off, or the BIOS is out of date. The fixes overlap, but VAN 1067 more often points to a BIOS setting or firmware problem.

Is VAN 1067 a ban?

No. VAN 1067 is a hardware and firmware compliance error, not a ban or suspension. Your account, skins, and rank are safe. Once TPM 2.0 and Secure Boot are enabled and detected, the error clears and you can play normally.

Why does VAN 1067 appear on Windows 10?

On Windows 10, TPM 2.0 and Secure Boot are not required for Valorant, so VAN 1067 there usually means Vanguard is misreading your system, or you upgraded to Windows 11 and rolled back, or a BIOS update reset your settings. Repairing Vanguard and confirming your BIOS settings usually clears it.

Will enabling Secure Boot delete my files?

No. Enabling TPM and Secure Boot does not delete files, games, or Windows itself. The one risky step is converting a Legacy disk from MBR to GPT, so back up anything important before that step, and only do it if your BIOS Mode actually says Legacy.

What if my PC has no TPM 2.0 at all?

Most PCs built since 2016 have TPM built into the processor as Intel PTT or AMD fTPM, so it is usually a BIOS setting, not missing hardware. Check your BIOS first. If your hardware genuinely has no TPM 2.0, that PC cannot run Valorant on Windows 11, and the only options are playing on a different PC or on Windows 10 while it is still supported.

For most players, VAN 1067 dies in BIOS — one flipped TPM setting or one Secure Boot toggle and Vanguard's check passes on the next launch. Run the two Windows checks first so you change the right setting, and you will be back in the lobby soon. And while Valorant sorts itself out, the free browser games here on GameAdda need no launcher, no anti-cheat check, and no BIOS visit — just pick one and play. 🎮