VALORANT VAN 57 Fix: Vanguard Not Initialized

 

VALORANT Vanguard Startup Error

VALORANT VAN 57 Fix: Vanguard Not Initialized

Restart Vanguard correctly, check the vgc service, repair the installation, and separate VAN 57 from Secure Boot and network-related errors.

Last updated: July 13, 2026

The VALORANT VAN 57 error and Vanguard Not Initialized message usually mean that Riot Vanguard did not initialize correctly before the game started.

The first action is a full Windows restart. If the same code returns, check whether the vgc service exists and can start, then reinstall Riot Vanguard. Reinstall the entire game only after the smaller Vanguard repair steps fail.

Fast VAN 57 repair order

Restart Windows → launch VALORANT before other apps → check the vgc service → set vgc to Automatic and start it → restart again → reinstall Riot Vanguard → restart after installation → reinstall VALORANT only when the error still returns.

Do not begin with BIOS changes

VAN 57 primarily points to Vanguard initialization. Secure Boot, TPM 2.0, and UEFI checks belong to errors such as VAN 9003 or a specific Vanguard compliance message, not the first VAN 57 repair step.

VAN 57 Symptoms

VAN 57 normally appears during startup, before a match begins. The symptoms below point toward Vanguard initialization rather than graphics quality or internet latency.

Symptom Likely category Check first
VAN 57 appears when VALORANT starts Vanguard initialization failure Restart Windows and check vgc
Vanguard Not Initialized The anti-cheat service is not ready Check whether vgc exists and starts
The Riot Client opens, but the game closes immediately Vanguard service or driver did not load Restart and reinstall Vanguard
A restart message repeats after installation The driver has not loaded during Windows startup Use Restart, not only Shut down
vgc is missing from Services Incomplete or damaged Vanguard installation Reinstall Riot Vanguard
VALORANT VAN 57 fix for Vanguard Not Initialized and vgc service

Different VAN codes require different checks

Do not use a Secure Boot tutorial only because the message begins with VAN. Record the exact number and wording before changing services, firmware, or security settings.

What Causes VALORANT VAN 57?

VAN 57 can occur when Vanguard is installed but its service or driver does not initialize correctly during Windows startup.

Area Problem state Check location
vgc service Stopped, disabled, or missing services.msc
Startup type Manual or Disabled vgc properties
Riot Vanguard Incomplete update or damaged installation Installed apps
Windows restart The PC was not restarted after Vanguard installation Windows power menu
Security software A third-party tool blocks or disables the service Security history and exclusions
System Configuration vgc was disabled during service cleanup msconfig
Windows updates A restart or component update remains pending Windows Update

The error may begin after a Vanguard update, Windows update, forced shutdown, security-software installation, startup-service cleanup, or an incomplete reinstall. Write down what changed immediately before the first failure.

1. Restart Windows Correctly

Riot’s first recommendation for Vanguard initialization errors is to restart the PC. Vanguard includes components that load during Windows startup, so closing and reopening the Riot Client is not equivalent to restarting Windows.

  1. Close VALORANT.
  2. Exit the Riot Client from the notification area.
  3. Save open work.
  4. Open the Windows power menu.
  5. Select Restart.
  6. After Windows loads, do not open monitoring or optimization tools.
  7. Launch the Riot Client and VALORANT.
  8. If VAN 57 returns, continue to the vgc service check.

Use Restart before Shut down

Windows Fast Startup can preserve parts of the previous session after a normal shutdown. Restart more reliably reloads services and drivers for this test.

2. Check the vgc Service

The vgc Windows service is associated with Riot Vanguard. Checking it is a useful diagnostic step when restarting does not resolve VAN 57.

Windows + R → services.msc → vgc
  1. Press Windows + R.
  2. Type services.msc.
  3. Press Enter.
  4. Find vgc.
  5. Double-click it.
  6. Set Startup type to Automatic.
  7. If Service status is Stopped, select Start.
  8. Select Apply and OK.
  9. Restart Windows.
  10. Launch VALORANT again.
vgc state Meaning Next action
Running / Automatic The service appears ready Restart and test VALORANT
Stopped / Automatic Configured for startup but not currently running Start it and restart Windows
Stopped / Manual It may not initialize when expected Change to Automatic, start it, and restart
Disabled The service cannot start Change to Automatic and start it
Missing from the list Vanguard may not be installed correctly Reinstall Riot Vanguard
Starts, then stops immediately Installation damage or software conflict is possible Reinstall Vanguard instead of repeating Start

Automatic does not mean currently running

Check both Startup type and Service status. After changing the service, restart Windows so that the Vanguard driver and service load through the normal startup process.

3. Reinstall Riot Vanguard

Reinstall Vanguard when vgc is missing, cannot start, stops immediately, or VAN 57 returns after the service and restart checks.

  1. Close VALORANT and the Riot Client.
  2. Open Settings → Apps → Installed apps.
  3. Find Riot Vanguard.
  4. Select Uninstall.
  5. Restart Windows after removal.
  6. Open the Riot Client.
  7. Launch VALORANT.
  8. Allow Vanguard to install again.
  9. Restart Windows when installation completes.
  10. Launch VALORANT and check the result.

VALORANT VAN 57 fix for Vanguard Not Initialized and vgc service

Restart after both removal and installation

The first restart clears the old service and driver state. The second restart loads the newly installed Vanguard components before VALORANT starts.

4. Check Startup and Security Conflicts

Confirm vgc in System Configuration

Windows + R → msconfig → Services → Hide all Microsoft services → vgc
  1. Press Windows + R.
  2. Type msconfig.
  3. Open the Services tab.
  4. Select Hide all Microsoft services.
  5. Find vgc.
  6. Make sure it is selected.
  7. Apply the change and restart Windows.

Do not enable or disable every service

Change only the confirmed Vanguard entry during this step. Broad service changes can create unrelated Windows, audio, network, or hardware-control problems.

Review recent security and optimization software

  • Check whether VAN 57 began after installing antivirus, firewall, or system-optimization software.
  • Review the security application’s blocked-item or quarantine history.
  • Use a temporary diagnostic pause only when you understand how to restore protection.
  • Do not leave security software disabled permanently.
  • When the conflict is confirmed, use the product’s documented exclusion or compatibility process.
  • Remove unofficial Vanguard patches or service-management scripts.

Too many startup tools were recently disabled?

Use the Windows 11 startup-app guide to restore necessary apps carefully. Do not treat security and anti-cheat services like ordinary media or launcher startup items.

5. Install Windows Updates and Restart

  1. Open Settings → Windows Update.
  2. Check for updates.
  3. Install pending quality and security updates.
  4. Restart Windows.
  5. Open services.msc and recheck vgc.
  6. Launch VALORANT before unnecessary background tools.

If VAN 57 began immediately after a Windows or Vanguard update, note the installation date. Complete pending restarts before deciding that the update itself is permanently incompatible.

6. Reinstall VALORANT Only When Necessary

A full reinstall takes longer and should follow the Vanguard-only repair. Use it when Vanguard reinstalls correctly but VAN 57 still appears, the Riot Client repeatedly repairs files, or the installation is incomplete.

  1. Uninstall Riot Vanguard.
  2. Uninstall VALORANT through Installed apps.
  3. Restart Windows.
  4. Download the installer from Riot’s official VALORANT site.
  5. Install VALORANT.
  6. Allow Riot Vanguard to install.
  7. Restart Windows again.
  8. Launch the Riot Client and VALORANT.

VAN 57 is fixed, but the game stutters?

Use the VALORANT FPS and frame-drop guide after the game launches normally. Graphics settings and FPS limits do not repair Vanguard initialization.

VAN 57 Still Appears

Situation Likely area Next action
vgc is missing after reinstall Vanguard installation did not complete Restart, reinstall from Riot Client, and record installer errors
vgc starts, then immediately stops Vanguard damage or software conflict Reinstall and review recent security software
VAN 57 returns after every reboot Service startup or system configuration Recheck vgc in Services and msconfig
The error began after optimization software The tool disabled or altered the service Undo its changes or remove the tool
The error code changed The original issue may be resolved and a different requirement now fails Use the guide for the new exact code
All steps fail on a clean installation Deeper Windows, driver, security, or compatibility issue Gather Riot logs and submit a support ticket

Collect information for Riot Support

  • The exact VAN code and full error wording
  • Windows version and recent update date
  • Whether vgc exists, its startup type, and service status
  • Whether Vanguard was removed and reinstalled
  • Recently installed antivirus, firewall, optimization, or overlay software
  • Whether the error began after a forced shutdown or update
  • Riot Client and VALORANT logs requested by Riot Support

Fixes to Avoid

Avoid Risk Use instead
Deleting Vanguard files manually Incomplete removal and service permission errors Use Installed apps and restart
Unofficial VAN patch tools Malware, account risk, and unsupported changes Use Riot’s installer and support process
Disabling every Windows service New audio, network, security, and hardware problems Check only vgc and known conflicts
Leaving antivirus disabled Reduced PC protection Use a temporary test and documented exclusions
Changing BIOS settings for VAN 57 without another compliance message Unnecessary boot and encryption risk Restart, vgc, and Vanguard reinstall first
Reinstalling Windows immediately Large time cost without isolating the service issue Complete the smaller repair sequence first

VALORANT VAN 57 Checklist

Step 1 — Confirm that the exact code is VAN 57.

Step 2 — Close Riot Client and restart Windows.

Step 3 — Open services.msc and find vgc.

Step 4 — Set vgc to Automatic and start it.

Step 5 — Restart Windows and test VALORANT.

Step 6 — Reinstall Riot Vanguard when vgc is missing or unstable.

Step 7 — Restart after Vanguard installation.

Step 8 — Check msconfig, security software, and Windows updates.

Step 9 — Reinstall VALORANT only after Vanguard-only repair fails.

Step 10 — Gather logs and contact Riot Support when the error remains.

Key takeaway

VAN 57 is usually a Vanguard initialization problem. Restart Windows first, then confirm that vgc exists, is set to Automatic, and can run. Reinstall Riot Vanguard when the service is missing or unstable, restart after installation, and use a full VALORANT reinstall only when the smaller repair sequence fails.

Frequently Asked Questions

Is VAN 57 an account ban?

VAN 57 normally points to Vanguard initialization on the PC rather than an account penalty. Check the service and installation before assuming an account problem.

Can a restart alone fix VAN 57?

Yes. A restart can load the Vanguard driver and service correctly. Repeated VAN 57 errors require the vgc and installation checks.

Should vgc be set to Automatic?

When diagnosing VAN 57, set vgc to Automatic, start the service, apply the change, and restart Windows.

Why does vgc stop immediately after I start it?

The Vanguard installation may be damaged or blocked by another program. Reinstall Vanguard and review recent security or optimization software.

Do I need to reinstall the entire game?

Not first. Reinstall Riot Vanguard before removing VALORANT. Use a full reinstall only when Vanguard-only repair does not work.

Can antivirus software cause VAN 57?

A third-party security or optimization tool can interfere with service startup. Review its history and use documented compatibility settings rather than leaving protection disabled.

Does VAN 57 require Secure Boot or TPM changes?

Not as the first step. Secure Boot and TPM checks are appropriate when the exact message or a different code specifically requests them.

BRAINLESS GAMER EDITOR

생활가전의 오류, 소음, 냄새와 청소·관리 방법을 알기 쉽게 정리합니다. 고장이라고 걱정하기 전에 집에서 안전하게 확인할 수 있는 해결 순서를 소개합니다.

Previous Post Next Post