VALORANT won't launch or shows a Vanguard error? Try 8 checks
✓ Reviewed & updated July 19, 2026Use the complete Riot or Vanguard message before changing anything. A VAN code, a "failed to launch" message, a Riot Client loop and a crash after the game window appears are different problems. Riot maintains code-specific Vanguard guidance; a generic reinstall can waste time and may not satisfy a security requirement named by the error.
The safest order is status and restart, client repair, Windows and driver updates, then a supported Vanguard or game reinstall. Firmware settings are a separate, higher-risk branch: do not change UEFI/BIOS values unless Riot's article for your exact code requires them and you have device-specific instructions.
Quick checklist
- Copy the complete VAN or Riot error
- Check Riot service status
- Restart Windows and the Riot Client
- Use Riot Client's repair option
- Install Windows and graphics updates
- Review a named security block or conflict
- Reinstall Vanguard using Riot's method
- Reinstall VALORANT or submit Riot logs
Match the message before choosing a branch
| What you see | Best first check | What it helps isolate |
|---|---|---|
| A message beginning with VAN and a number | Open Riot's article for that exact code | A Vanguard requirement or service condition |
| Riot Client opens but VALORANT will not start | Use client repair and capture the launch message | Damaged game files or a client handoff problem |
| The game window appears and then crashes | Use Riot's launch-crash guide and collect logs | A graphics, software-conflict or game-file branch |
| Many players cannot sign in | Check Riot service status | A service incident rather than this PC |
| The message explicitly names Secure Boot, TPM or Exploit Protection | Use the exact Riot code article | A Windows security or firmware requirement |
The 8 checks, from lowest to highest impact
Copy the exact error and check Riot status
Record the whole message, including a VAN code and any requirement named beneath it. Check Riot's official service-status page for your region. Search Riot Support with the exact code, not only "VALORANT won't launch."
Restart Windows and open Riot Client once
Close Riot Client from its tray icon when possible, restart Windows, then open Riot Client normally. Vanguard components and Windows security state may require a complete restart after an update.
Use Riot Client's repair option
Open Riot Client settings and use its repair feature for VALORANT when available. Allow the scan to finish without closing the client or interrupting the network.
Install Windows and graphics updates
Install pending Windows updates, restart, then obtain the supported graphics driver from the PC or GPU manufacturer. Do not use an unrelated driver-downloader utility.
Review a specific security block or software conflict
Check Windows Security protection history and any managed security console for an event that names Riot Client, VALORANT or Vanguard. Riot's launch-crash guidance may also ask you to test a clean boot to isolate a conflicting application.
- Do not disable antivirus or the firewall globally.
- Do not restore a file from an unofficial installer.
- Re-enable normal startup items after the controlled test.
Use only the code-specific security requirement
If the error explicitly names Exploit Protection, Secure Boot, TPM or another requirement, open Riot's current page for that exact code. Verify Windows version and current state first. For firmware changes, use manufacturer documentation and the safety note above.
Reinstall Riot Vanguard using Riot's method
If Riot's error guide points to Vanguard installation damage, uninstall Riot Vanguard through Windows Settings according to Riot's instructions. Restart, open Riot Client to reinstall Vanguard, then restart again if prompted.
Reinstall VALORANT or submit Riot logs
Use Riot's current uninstall-and-reinstall guide, not a third-party cleaner. Confirm the Riot account, installation location and available storage first. If the same message survives a fresh install, use Riot's log-collection instructions and submit a ticket with the code, Windows build, hardware, recent changes and every step tested.
Primary references: Riot Support's launch-crash troubleshooting, game uninstall and reinstall guidance, Vanguard error-code guide, service status, and Riot Games' Vanguard security overview.
Frequently asked questions
Should I start the vgc service manually?
Only when Riot's current instructions for your exact code call for it. A stopped service can be an effect of a damaged installation or policy, so recording the code first matters.
Do I need Secure Boot and TPM?
Requirements depend on Windows version, Vanguard state and the exact error. Follow Riot's current code-specific page. Do not change firmware based on a generic guide.
Should VALORANT always run as administrator?
No. Normal launch through Riot Client is the baseline. Permanent elevation is not a universal fix and can create mismatched permissions.
Will reinstalling Vanguard remove VALORANT?
They are separate components, but other Riot games may also use Vanguard. Read Riot's current uninstall article and restart when instructed.
If Vanguard explicitly names MsIo64.sys, use the driver-conflict path. If Riot Client instead shows “Could not call proc” or Windows reports Bad Image error 0xc0000020, follow that exact dialog.
Send us the details →