Fix the error.
Get back in game.
Clear, hardware-specific fixes for Vanguard errors, Secure Boot, TPM 2.0, Intel PTT, AMD fTPM and the BIOS settings that usually send players digging through Reddit threads.
Start with the error you see.
Each guide answers one specific problem instead of mixing every Vanguard issue into a giant generic article.
VAN 9003 — Secure Boot required
Start here if Vanguard says Secure Boot is required. Check UEFI mode, Secure Boot state, TPM 2.0 and motherboard-specific firmware settings.
VAN 9001 — TPM not detected
Check tpm.msc, then find the correct firmware option: Intel PTT or AMD fTPM.
Enabled in BIOS. Still VAN 9003.
For the frustrating case where Secure Boot says Enabled but Windows or Vanguard still sees it as Off.
Not sure which guide you need?
Pick what Windows or Vanguard is telling you and VAN//FIX points you to the shortest route.
Check Secure Boot from Windows first.
Do not begin by changing random BIOS settings. Windows can tell you whether Secure Boot is actually active.
Motherboard names are half the problem.
Secure Boot and TPM are not labeled the same way on every board. Our guides translate the common vendor wording.
Secure Boot, Key Management, PCH-FW, Intel PTT and AMD fTPM paths.
Security, Windows OS Configuration, PTT, AMD CPU fTPM and Secure Boot modes.
CSM Support, Secure Boot, factory keys and TPM/fTPM platform settings.
CSM, Secure Boot, default keys, Intel PTT and AMD fTPM options.
Why VAN//FIX exists.
Most Vanguard troubleshooting gets annoying because the useful answer is split between Riot support, motherboard manuals and community threads.
“Don’t tell me to enable Secure Boot. Tell me why it’s enabled and still not working.”
That is the whole design philosophy: answer the exact thing the player is stuck on, then stop.
See an error code?
Start with the exact code or message Vanguard gives you. The page should answer that problem directly.