VAN 152 Valorant

VAN 152 - Vanguard Not Starting | Valorant Fix Guide

📅 Published: 2026-02-05 🔄 Updated: 2026-02-05 👥 Reports: 54 ⚡ Severity: 🔴 High

🎯 Quick Answer

Restart the Vanguard service and your PC, then run Valorant as an administrator to resolve the VAN 152 error.

SECTION 1: OVERVIEW

Error code VAN 152 is a system-level error indicating the Vanguard anti-cheat service failed to initialize during the Valorant client startup sequence. This error exclusively affects the Windows platform, as Vanguard is a kernel-mode driver designed for Windows 10 and Windows 11. The error manifests after game updates, particularly following the February 01, 2026 patch, indicating a correlation with changes to the Vanguard component. This is a common error with a high severity impact, as it completely prevents the game application from launching. The exact error message presented to the user is "Vanguard not starting" accompanied by the code VAN 152. The error signifies a failure in the communication chain between the Vanguard user-mode service (vgc) and its kernel-mode driver (vgk).

SECTION 2: SYMPTOMS

The Valorant client terminates during the initial loading phase, immediately after the Riot Games logo splash screen. A modal error dialog box appears with the title "Vanguard Anti-Cheat" and the message "Vanguard not starting" alongside the specific error code VAN 152. The game process does not proceed to the main menu or login screen. The system tray may lack the Vanguard icon (a red shield), or the icon may display an error state. Attempting to relaunch the client without a system restart results in the same termination sequence and error message.

SECTION 3: COMMON CAUSES

Category: Software Conflict Specific technical explanation: Third-party security software (antivirus, anti-malware, firewall) or system optimization utilities interfere with the Vanguard driver (vgk.sys) loading or with the vgc service. These programs can block driver installation, quarantine essential files, or prevent service communication. Why this causes the problem: Vanguard requires unhindered kernel-level access. Blocking actions break the integrity check between the client and the anti-cheat service, triggering the VAN 152 error. Category: Configuration Error Specific technical explanation: The Vanguard service (vgc) is set to a manual or disabled startup type, or its process has terminated unexpectedly. The service status is not "Running" when the Valorant client requests a handshake. Why this causes the problem: The Valorant client has a dependency on the vgc service. If the service is not active, the client cannot establish the required secure connection, resulting in startup failure. Category: Software Conflict Specific technical explanation: Outdated or corrupted system files, particularly Windows Management Instrumentation (WMI) or Service Control Manager databases, prevent proper service enumeration and control. Why this causes the problem: Vanguard relies on standard Windows service management APIs. Corruption in these subsystems leads to failures when attempting to start or query the vgc service. Category: Configuration Error Specific technical explanation: Insufficient system permissions prevent the Vanguard installer or service from creating necessary registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vgc and vgk, or from accessing protected system directories. Why this causes the problem: Vanguard installation is incomplete or damaged, leaving the system in a state where the driver is registered but non-functional. Category: Game Bug Specific technical explanation: A flawed game or Vanguard update results in a version mismatch between the installed Vanguard components and the version expected by the Valorant client executable. Why this causes the problem: The client performs a version check on the anti-cheat service. A mismatch causes the client to reject the connection and report the VAN 152 error. Category: Hardware Issue Specific technical explanation: Certain motherboard BIOS/UEFI settings, such as disabling virtualization features (VT-x, VT-d) or having Legacy/CSM boot enabled instead of UEFI, conflict with Vanguard's low-level operation. Why this causes the problem: Vanguard utilizes modern CPU and system firmware features for isolation and security. Incompatible BIOS settings can prevent the driver from initializing correctly.

SECTION 4: SOLUTIONS

Solution 1: Restart Vanguard Service and System

Difficulty: Easy Time Required: 5 minutes Success Rate: High Prerequisites: None Steps:

Press Windows Key + R, type services.msc, and press Enter.
In the Services window, locate the "vgc" service in the list.
Right-click "vgc" and select Restart. If the service is stopped, select Start.
Close the Services window.
Fully shut down your Windows PC using the Start Menu -> Power -> Shut Down. Do not use "Restart."
After the system powers off completely, turn it back on.
Launch Valorant as an administrator (right-click the shortcut and select "Run as administrator").

Technical Explanation: This forces a clean reload of the Vanguard kernel driver (vgk.sys) and its associated user-mode service (vgc). A full shutdown clears the driver from memory, while running as administrator ensures the client has necessary privileges to interface with the service. Verification: The Vanguard red shield icon appears in the system tray before the Valorant client launches, and the game proceeds past the splash screen to the login interface without the VAN 152 error.

Solution 2: Reinstall Vanguard Manually

Difficulty: Medium Time Required: 10 minutes Success Rate: High Prerequisites: Administrator access required Steps:

Right-click the system tray Vanguard icon (if present) and select "Exit Vanguard." If absent, proceed.
Press Windows Key + R, type appwiz.cpl, and press Enter to open Programs and Features.
Locate and uninstall "Riot Vanguard."
Restart your computer when prompted.
After reboot, navigate to the Valorant installation directory, typically C:\Riot Games\VALORANT\live.
Locate and run the installer file named VALORANT-Win64-Shipping.exe as an administrator.
Follow the installation prompts. This will reinstall both the game client and Vanguard.
Launch Valorant normally after installation completes.

Technical Explanation: A manual reinstall replaces all Vanguard binaries and registry entries, correcting issues caused by corrupted files, incomplete updates, or incorrect registry permissions from a previous installation. Verification: Check in services.msc that the "vgc" service status is "Running" and startup type is "Automatic." The game launches without error.

Solution 3: Configure Antivirus and Windows Security Exclusions

Difficulty: Medium Time Required: 7 minutes Success Rate: Medium Prerequisites: Administrator access may be required for some security software. Steps:

Add the following folders to your antivirus and Windows Security virus & threat protection exclusions list:

- C:\Program Files\Riot Vanguard\ - C:\Riot Games\VALORANT\live\ - C:\Riot Games\Riot Client\

For Windows Security: Go to Settings > Update & Security > Windows Security > Virus & threat protection > Manage settings under "Virus & threat protection settings." Scroll to "Exclusions" and add the folders.
Add the following processes to your antivirus allow list: VALORANT-Win64-Shipping.exe, RiotClientServices.exe, vgc.exe, and vgk.sys.
Temporarily disable any third-party firewall or "game mode" in security suites.
Restart your computer and attempt to launch Valorant.

Technical Explanation: Real-time scanning of Vanguard's kernel driver (vgk.sys) during loading can cause timeouts or file locks. Exclusions prevent the security software from intercepting and blocking the driver's initialization routine. Verification: Monitor your security software's logs or notifications to confirm no blocks occur on the listed Vanguard files during the next game launch, which then proceeds successfully.

Solution 4: Repair System Files and Check Disk

Difficulty: Advanced Time Required: 15-20 minutes Success Rate: Medium Prerequisites: Administrator access required. An active internet connection is needed for DISM. Steps:

Open Command Prompt as Administrator (search "cmd," right-click, "Run as administrator").
Execute the System File Checker scan: sfc /scannow. Allow the scan to complete and repair files.
Execute the Deployment Image Servicing and Management tool: DISM /Online /Cleanup-Image /RestoreHealth.
To check for disk errors that may affect system files, run: chkdsk C: /f. You will be prompted to schedule the scan for the next restart. Type Y and restart your computer.
After the chkdsk scan completes and Windows loads, run Command Prompt as Administrator again.
Reset the Windows Management Instrumentation repository by executing:

` net stop winmgmt winmgmt /resetrepository net start winmgmt `

Restart your PC and test Valorant.

Technical Explanation: Corrupted Windows system files, a damaged component store, or a faulty disk sector can break the Service Control Manager, which Vanguard depends on. These commands repair core OS files and the WMI database, which manages system services. Verification: The sfc /scannow command will output a message confirming it found and repaired corrupt files. The vgc service should start without errors reported in the Windows Event Viewer under System logs.

Solution 5: Verify UEFI/BIOS and Secure Boot Settings

Difficulty: Advanced Time Required: 10 minutes Success Rate: Low (but definitive for specific hardware) Prerequisites: Knowledge of accessing your system's BIOS/UEFI. Steps:

Reboot your computer and enter the BIOS/UEFI setup (typically by pressing F2, Del, or F10 during startup).
Navigate to Advanced or Security settings.
Ensure the following features are Enabled:

- Virtualization Technology (Intel VT-x or AMD-V) - IOMMU or VT-d (if present) - Secure Boot (should be in "Standard" or "Windows UEFI" mode, not "Custom" or "Disabled")

Ensure the boot mode is set to UEFI, not Legacy or CSM (Compatibility Support Module).
Save changes and exit the BIOS/UEFI.
Upon booting into Windows, open Command Prompt as Administrator and run msinfo32.
Confirm that "Secure Boot State" is "On" and "BIOS Mode" is "UEFI."
Attempt to launch Valorant.

Technical Explanation: Vanguard's highest security level requires UEFI Secure Boot and utilizes CPU virtualization features for hardening. Legacy boot modes or disabled virtualization can prevent the driver from loading with the required privileges. Verification: System Information (msinfo32) confirms Secure Boot is On and BIOS Mode is UEFI. Vanguard loads without generating related error entries in the Windows Event Viewer's System log.

Solution 6: Perform a Clean Boot and Diagnostic Launch

Difficulty: Medium Time Required: 12 minutes Success Rate: Medium (diagnostic) Prerequisites: Administrator access. Steps:

Press Windows Key + R, type msconfig, and press Enter.
In the System Configuration window, go to the Services tab.
Check the box "Hide all Microsoft services," then click Disable all.
Go to the Startup tab and click Open Task Manager. Disable all startup items in Task Manager.
Close Task Manager, click OK in System Configuration, and restart your PC.
After booting into the clean environment, launch Valorant as an administrator.
If the error is resolved, return to msconfig and re-enable services/startup items in groups to identify the conflicting software.

Technical Explanation: This process starts Windows with a minimal set of drivers and startup programs, isolating the conflict. If Vanguard works in this state, a third-party application is interfering with its operation. Verification: Valorant launches successfully in the clean boot state. The conflicting software is identified when the VAN 152 error reappears upon re-enabling a specific group of services or startup items.

SECTION 5: PREVENTION

Maintain a regular schedule for updating Windows via Windows Update, including optional driver updates. Configure your security software exclusions permanently for the Vanguard and Riot Games directories. Before installing major Valorant updates, perform a full system shutdown instead of a restart to ensure a clean driver state. Monitor the Vanguard system tray icon; its absence on boot indicates the service failed to start and requires investigation via services.msc. Avoid using system "debloater" scripts or registry cleaners that may modify service permissions or remove components Vanguard depends on.

SECTION 6: WHEN TO CONTACT SUPPORT

Contact Riot Games Support if all solutions fail and the error persists across multiple full system restarts. Escalation is required if the vgc service will not start and reports a specific Windows error code in Event Viewer. Provide the diagnostic logs located in C:\Program Files\Riot Vanguard\Logs and the system specification report from msinfo32. Official support channels are accessed via the Riot Games support website. Do not share these logs on public forums.