How to Fix the vanguard 216 error (VAN 216)
If you see the vanguard 216 error when launching VALORANT, you are almost certainly looking at Riot Vanguard’s VAN 216 code. The full message reads: “Vanguard Error: VAN 216. An unexpected error with Vanguard has occurred and the client will now close.”
This guide covers what that code means, why it happens, and the fixes in order from simplest to most involved. The most important point comes first: do not keep pressing Play. That is what extends the problem. Related reading: Can you play VALORANT on Mac? League of Legends Wild Rift APK and OBB.

What the vanguard 216 error Is
Vanguard is Riot Games’ kernel-level anti-cheat software. It was first released alongside VALORANT and is now also used in League of Legends, so the same VAN code can appear in either game. Vanguard must complete a check with the game client before you can play. When that launch sequence is attempted too many times in a short period, Vanguard shows VAN 216 and closes the client.
This is not the same as every other “error 216” you may find online. An older, separate VALORANT installation problem from 2020 was worded as “Failed to create process. Last error code: 216” and related to installing a required dependency. That is a different error from the VAN 216 launch code covered here, and its install-era fixes should not be mixed in with the steps below.
Why the vanguard 216 error Happens
According to Riot Games Support’s dedicated VAN 216 article, updated July 17, 2026, VAN 216 can appear when too many launch attempts are made within a short period. In practice, that usually means:
- The game or client crashed, and you immediately tried to relaunch several times in a row.
- The Riot Client was closed and reopened multiple times in one sitting.
- A rocky patch day or server problem led to repeated retries, which pushed you over the same limit.
Riot’s explanation is a rate limit on launch attempts, not a statement that a file on your PC is broken. That is why the official fix is waiting, not repairing. One guide notes that a stuck Vanguard service, a clock out of sync, or background software conflicts can produce a similar-looking failure, but Riot’s current VAN 216 article does not list those as the cause of this code. Treat the steps after the wait as fallback troubleshooting for a persistent case, not as Riot’s stated cause of VAN 216.
VAN 216 is not a ban. It is a temporary, self-resolving cooldown tied to how often you tried to launch, not an enforcement action against your account.
How to Fix the vanguard 216 error
Work through these steps in order, from simplest to most involved. Only move to the next step if the previous one did not work.
Fix 1: Stop Relaunching and Wait at Least 30 Minutes (Riot’s Official Fix)
This is the only fix Riot lists for VAN 216, and it should be tried in full before changing any setting.
- Close the VAN 216 error and leave the Riot Client alone.
- Do not reopen the client “just to check,” and do not click Play again to see if it has cleared.
- Set a timer for at least 30 minutes from the last launch attempt.
- After the full, uninterrupted 30 minutes have passed, open the Riot Client and launch the game normally.
Riot states explicitly that pressing Play before the 30 minutes are up will restart the timer. So, for example, if the error first appeared at 8:00 PM and you press Play at 8:15 PM, the countdown starts over from zero. Every early attempt adds time rather than saving it. If you have been clicking Play every few minutes since the error appeared, that alone may be why it keeps showing up.
Fix 2: Restart Your PC
If you have waited the complete, uninterrupted 30 minutes without pressing Play and VAN 216 still returns, restart your PC, then launch the game again. A full restart gives Vanguard’s background service a clean chance to start from scratch instead of recovering from whatever state it was in.
Note: do not use this restart as a shortcut around Fix 1. Restarting and immediately pressing Play again during the cooldown window can still count as another early launch attempt.
Fix 3: Check Your Windows Date, Time, and Time Zone
A drifted system clock is a documented cause of Vanguard connection problems more broadly, though Riot’s VAN 216 article does not list it as the cause of this code. Check it only after the full wait has failed.
- Open Settings and go to Time and Language, then Date and Time.
- Turn on Set time automatically, if it is not already on.
- Confirm your time zone matches your actual location.
- Use Sync now, if the option is available.
- Restart your PC, then launch the game again.
Fix 4: Make Sure the Vanguard Service (vgc) Starts Automatically
Vanguard’s background service is called vgc. If it is not running when the game launches, there is nothing for the client to authenticate against. This is a standard Vanguard troubleshooting step, not a VAN 216-specific instruction from Riot.
- Press Windows key + R, type services.msc, and press Enter.
- Scroll down and find vgc in the list.
- Right-click it and select Properties.
- Set Startup type to Automatic.
- If the service shows as stopped, click Start.
- Apply the changes, restart your PC, and try launching the game.
Fix 5: Check Your Internet Connection
Disconnect and reconnect your Wi-Fi, or unplug and replug an Ethernet cable, then reopen the Riot Client and try again. Vanguard needs a stable connection to complete its readiness check, and a brief drop can interrupt that handshake. This is a general Vanguard troubleshooting step, not a VAN 216-specific instruction from Riot.
Fix 6: Reinstall Riot Vanguard
If the steps above have not worked, reinstall Vanguard itself. This does not touch the game files.
- Close the Riot Client completely.
- Open Settings, then Apps, and uninstall Riot Vanguard.
- Restart your PC.
- Launch the Riot Client and start the game. Vanguard will reinstall itself automatically as part of the launch process.
- Restart once more if prompted.
Vanguard does not have its own standalone download page. It is only installed automatically through the Riot Client, so do not download a supposed standalone Vanguard installer from a third-party site.
Fix 7: Check Secure Boot and TPM 2.0 (Windows 11)
On Windows 11, Vanguard enforces Secure Boot and TPM 2.0, and a missing requirement can block the anti-cheat check. This step is documented for Vanguard generally and for League of Legends’ Vanguard install, not as Riot’s VAN 216-specific fix, so only try it if the earlier steps have failed and you are on Windows 11.
- Press Windows key + R, type msinfo32, and press Enter. Confirm Secure Boot State reads On and BIOS Mode reads UEFI.
- Press Windows key + R, type tpm.msc, and press Enter. It should read TPM 2.0, ready for use.
- If either is missing, enable it in your PC’s BIOS/UEFI settings, following your motherboard manufacturer’s guide. BIOS menus differ by manufacturer, so do not change other BIOS settings while you are there.
Fix 8: Reinstall the Game as a Last Resort
If every step above has been tried and VAN 216 still appears, a full game reinstall replaces any game files that may be interfering with Vanguard’s checks. This is the most time-consuming option, which is why it is saved for last, and it is uncommon for VAN 216 specifically. If you need to redownload the installer, get it from Riot’s official VALORANT site rather than a third-party mirror.
If Nothing Works: Contact Riot Player Support
If you have completed a full, uninterrupted 30-minute wait and then worked through the steps above in order, and VAN 216 still appears, open a ticket with Riot Player Support and attach your logs. At that point the problem is no longer the standard launch-attempt cooldown, and support can check account- or system-specific causes that a guide cannot.
How to Prevent the vanguard 216 error From Coming Back
- After a crash, resist the urge to immediately mash Play. Waiting even a minute or two before your first retry reduces the odds of triggering the same cooldown again.
- Let any pending Windows update fully complete, including follow-up restarts, before opening the game. Launching mid-update can catch Vanguard’s service in an inconsistent state.
- If you run third-party antivirus software, make sure it is not quarantining or restricting Vanguard’s files. Check your antivirus provider’s own support site for its exclusion steps, since the process varies by vendor.
FAQs About the vanguard 216 error
What does the vanguard 216 error mean?
According to Riot’s current VAN 216 support article, it means too many launch attempts were made within a short period, and Vanguard is enforcing a cooldown before the next attempt is allowed. The full message is: “Vanguard Error: VAN 216. An unexpected error with Vanguard has occurred and the client will now close.”
How long do I need to wait for the vanguard 216 error to clear?
At least 30 minutes without pressing Play. Riot states that pressing Play before that window ends resets the timer.
Can I check if it is fixed by trying every few minutes?
No. That is the one thing to avoid. Each early attempt restarts the 30-minute countdown rather than shortening it.
Does the vanguard 216 error mean I have been banned?
No. It is a temporary launch-frequency cooldown, not an enforcement action, and by itself it does not damage your PC or put your account at risk.
What if I waited the full 30 minutes and the vanguard 216 error still appears?
Move on to the fallback steps in order: restart your PC, check your Windows clock, confirm the vgc service is set to Automatic, check your internet connection, and reinstall Vanguard if needed. Save a full game reinstall for last, and contact Riot Player Support if the error survives all of them.
Should I reinstall the whole game right away?
No. Save that for last. It rarely addresses VAN 216 specifically, since the official cause is launch frequency, not a corrupted game file, and it takes the most time of any step in this guide.
Does the vanguard 216 error affect League of Legends too?
Yes, it can. League of Legends uses the same Riot Vanguard install as VALORANT, so the same VAN code can turn up in both games. The 30-minute wait is Riot’s stated fix for the VALORANT VAN 216 article; the generic Vanguard steps in this guide apply to the shared install.
Is the vanguard 216 error the same as the old “Last error code: 216” install error?
No. The older 2020 VALORANT install message, “Failed to create process. Last error code: 216,” was a different installation/dependency problem, not the VAN 216 launch-attempt cooldown covered here.
A Note on What Is and Is Not Confirmed for VAN 216
To avoid overstating the evidence: Riot’s VAN 216 article gives exactly one cause (too many launch attempts in a short period) and exactly one fix (wait at least 30 minutes without pressing Play). Fixes 2 through 8 above are real Vanguard troubleshooting steps taken from the reputable guides listed under Sources, but they are generic Vanguard steps, not Riot’s VAN 216-specific instructions. They are included only as fallbacks for the case where a full, uninterrupted wait does not clear the error.
UNVERIFIED for VAN 216 specifically: Secure Boot and TPM 2.0 being off, a drifted Windows clock, a stopped vgc service, an unstable internet connection, corrupted Vanguard files, and antivirus blocking Vanguard have NOT been confirmed by Riot as causes of VAN 216 itself. Do not present them as confirmed VAN 216 causes. They are included above only as generic Vanguard fallbacks, clearly labelled as such.
Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech
More Guides You May Like
minecraft boat error: Why Boats Vanish, Break, or Get Stuck and How to Fix Them
error: unable to access jarfile minecraft_server.26.2.jar
Connectivity hssgamepad: How to Fix Gamepad Pairing, Drops, and Lag
mo2 ssl error: How to Fix the Mod Organizer 2 Nexus SSL Error
diablo 4 error code 300024: How to Fix the Reliquary Claim Error
pokemon tcg live error 10011: How to Fix PTCGL Error 10011
error code 1756 battlefront 2: How to Fix the Battlefront 2 Inventory Error
How to Fix Error Code is-eo-failed_op_start in the Epic Games Launcher