How to Fix VAN: STATUS_SB_POLICY (Secure Boot Policy) – 2026

6 min to read

How to Fix VAN: STATUS_SB_POLICY (Secure Boot Policy) – 2026

VAN: STATUS_SB_POLICY means Secure Boot is on, but Vanguard cannot verify its policy, usually because the Secure Boot keys were changed, cleared or replaced with custom keys. Restart into the BIOS, reset Secure Boot to the factory default keys, install every Windows update for the 2023 certificates, and restart.

VAN: STATUS_SB_POLICY

Secure Boot policy can't be verified
Riot Vanguard: VAN: STATUS_SB_POLICY

What causes VAN: STATUS_SB_POLICY

Secure Boot works with a chain of keys stored in the firmware. Vanguard expects the standard Microsoft keys. The check fails when the keys were cleared (Setup Mode), replaced by custom keys (common after installing Linux with your own keys), or are out of date while Microsoft rolls out new Secure Boot certificates in 2026.

How to fix VAN: STATUS_SB_POLICY in Windows

1

Suspend BitLocker first (if it is on)

Changing TPM, Secure Boot or boot settings can make BitLocker ask for its 48-digit recovery key at the next start. Open Start, type Manage BitLocker and, if drive C: shows BitLocker on, click Suspend protection. On Windows Home look under Settings > Privacy & security > Device encryption. Or run this in Terminal (Admin): manage-bde -protectors -disable C: -RebootCount 2. It turns itself back on after two restarts. Check that you can see your recovery key at aka.ms/myrecoverykey before you go on.
2

Install the Secure Boot certificate updates

Microsoft is replacing the Secure Boot certificates from 2011 (they expire in June and October 2026). The new ones come with Windows Update, so install every update, then also check your motherboard or laptop maker for a BIOS update. Never use tools that write Secure Boot keys from Windows.

How to fix it in the BIOS

This part happens in your PC's firmware setup (the BIOS), so open this page on your phone first. Menu names change a little between BIOS versions: if a path below does not match, look for the words in bold.

1

Restart into the BIOS

Open Settings > System > Recovery, click Restart now next to Advanced startup, then Troubleshoot > Advanced options > UEFI Firmware Settings > Restart. Or run shutdown /r /fw /t 0 in Terminal (Admin). You can also press Del right after switching the PC on (desktops; F2 on many laptops and some ASRock and MSI boards).
2

Update the BIOS

Download the newest BIOS for your exact board or laptop model from the maker's support page and flash it with the board's own tool from inside the BIOS (ASUS EZ Flash, MSI M-Flash, Gigabyte Q-Flash, ASRock Instant Flash; laptops: the maker's updater). Never switch the PC off while it flashes. A BIOS update often resets settings, so check TPM and Secure Boot again afterwards. The PC restarts after flashing: open the BIOS again for the next step.
3

Change these settings

  • Turn on Secure Boot and install the default keys (Install default Secure Boot keys or Restore Factory Keys). Secure Boot mode Standard, OS type Windows UEFI mode.

Where to find them on your board:

ASUS

Press F7 for Advanced Mode.
Secure Boot: Boot > Secure Boot > OS Type: Windows UEFI mode, then Key Management > Install Default Secure Boot keys

MSI

Press F7 for Advanced mode.
Secure Boot: Settings > Advanced > Windows OS Configuration > Secure Boot: Enabled, Secure Boot Mode: Standard

Gigabyte (AORUS)

Press F2 to switch to Advanced Mode.
Secure Boot: Boot > Secure Boot: Enabled, Secure Boot Mode: Standard (or Restore Factory Keys)

ASRock

Press F6 to switch to Advanced Mode.
Secure Boot: Security > Secure Boot: Enabled, then Install Default Secure Boot Keys

Laptops and prebuilt PCs

Dell: F2, Boot Configuration > Secure Boot, Security > TPM 2.0 Security On, Virtualization Support > VT / VT-d.
HP: Esc then F10, Advanced > Secure Boot Configuration, Security > TPM Embedded Security, Advanced > System Options > Virtualization Technology.
Lenovo: F1 on ThinkPad, F2 or the Novo button on IdeaPad and Legion, Security > Secure Boot, Security > Security Chip, Security > Virtualization.
ASUS: F2, Security > Secure Boot Control, Advanced > Trusted Computing.
Acer: F2, set a Supervisor password first or Secure Boot stays greyed out, then Boot > Secure Boot and Security > TPM.
MSI: Del, Security > Secure Boot, Advanced > Trusted Computing.
Gigabyte / AORUS: F2, Security > Secure Boot, Advanced > Trusted Computing.
4

Save and restart

Press F10 and confirm with Yes. Windows starts normally.

Fix it in one click with RIP Tweaks (free)

RIP Tweaks 6.9.3 has a free anti-cheat error fixer. Open Fixes, then Anti-cheat errors, and paste VAN: STATUS_SB_POLICY or pick your game. The app first checks what your PC has right now (for example Secure Boot: Off, TPM: On) and shows only the steps still missing.

The anti-cheat error fixer in RIP Tweaks

It fixes the Windows side itself

Memory integrity, the Windows hypervisor, test signing, Control Flow Guard, the vulnerable driver blocklist and services that an optimizer switched off: the app changes them for you, saves what it changed first, and can put every change back.

It takes you into the BIOS with the right card

What only the BIOS can change (TPM, Secure Boot, CSM, virtualization, IOMMU), the app shows for your exact board maker, suspends BitLocker for you and restarts straight into the BIOS. A QR code opens this page on your phone.

It checks again after the restart

Back in Windows, the fixer checks again and shows green, or exactly what is still missing.

The fixer is free in every plan, also without an account. Download RIP Tweaks (free)

Check that it worked

In msinfo32, Secure Boot State says On. Start the Riot Client.

Frequently asked questions

I use custom Secure Boot keys for Linux. Can I keep them?

Vanguard expects the factory keys. Restoring them is the reliable fix; most big Linux distributions boot with the default keys through Microsoft's signed shim.

What are the 2023 Secure Boot certificates?

Microsoft's original Secure Boot certificates from 2011 expire in 2026. Windows Update installs the new 2023 ones, and some boards also need a BIOS update for them.

Is it safe to turn on Secure Boot?

Yes. Secure Boot is a standard UEFI feature that only lets signed boot software start. Windows 11 PCs ship with it on, and turning it on does not touch your files, games or settings.

Will Secure Boot break my Linux dual boot?

Most big Linux distributions (Ubuntu, Fedora, openSUSE) boot fine with Secure Boot on. Custom kernels or unsigned drivers may not. Keep Windows Boot Manager first in the boot order so Windows starts directly.

My settings were gone after a BIOS update. Is that normal?

Yes. BIOS updates often reset every setting to the default, and on some boards that turns fTPM, Secure Boot or virtualization off again. Check them again after every BIOS update.

Sources

All anti-cheat errors: Anti-Cheat Error Fixes. Related: How to Fix VAN: RESTRICTION 1, 3, 4 and 5 in Valorant – 2026 and How to Fix VAN 9003 in Valorant (Secure Boot) – 2026.