How to Fix “VANGUARD ERROR: VAN 1067” in League of Legends?

League of Legends can show VAN 1067 before the game opens or several minutes into a match. The timing matters because the two failures usually occur at different points in Riot Vanguard’s Windows check.

Riot uses VAN 1067 when Vanguard encounters an unexpected problem while starting or checking in with Windows. The code confirms an anti-cheat failure, but it does not identify the component responsible.

On one PC, the vgc service never starts. On another, it starts normally and is then stopped by a conflicting service, driver, or connected device.

VAN 1067 alone also does not prove that TPM 2.0 or Secure Boot is disabled. Change firmware security settings only when Vanguard displays a second, specific requirement message.

1. Check Windows, USB Devices, and Riot Client Permissions

Vanguard can fail before League opens when an update is unfinished, the Riot Client lacks permission, or a USB device interrupts startup.

Restarting prevents a stale boot session from carrying forward. Do not use a Vanguard reinstall until these checks are complete.

1. Exit League of Legends and the Riot Client. Right-click the Riot icon in the system tray and select Exit if it remains open.
2. Open Settings > Windows Update, select Check for updates, and install the available Windows updates.
3. Restart the PC. Shutting the lid, signing out, or reopening only the Riot Client does not reload Vanguard’s Windows services and drivers.
4. Disconnect controllers, SD cards, and nonessential USB devices for this test. Keep the keyboard and mouse connected.
5. Right-click the Riot Client shortcut and select Run as administrator once, then launch League.

These are the opening checks in Riot’s VAN 1067 guidance. If League opens normally, reconnect the devices one at a time to identify the one causing the failure.

If the Riot Client cannot finish an update, resolve that problem before continuing. If League opens first and then closes, go to the next method and isolate a software conflict. For an immediate error, inspect vgc in Method 3.

2. Isolate the Software or Driver Terminating Vanguard

A delayed VAN 1067 usually indicates that Vanguard started and then encountered another Windows component. A clean boot isolates that conflict by loading Windows without nonessential services and startup apps.

The clean boot is not needed when vgc is missing or never starts. Pay particular attention to audio, remote-access, network-discovery, virtualization, monitoring, RGB, and controller software.

Do not uninstall whole software categories on suspicion. First reproduce the error in a clean Windows session, then remove or update only the program that the comparison identifies.

1. Open Settings > Apps > Installed apps. Note software installed shortly before VAN 1067 began, especially anything that added virtual audio, remote-control, device-emulation, or hardware-monitoring components.
   
2. Press Ctrl + Shift + Esc. In Task Manager, close nonessential overlays, recorders, game boosters, RGB tools, hardware monitors, and remote-control apps for one launch.
   
3. Perform Riot’s clean-boot procedure, making sure vgc remains enabled. The detailed Windows steps are also available in Appuals’ clean-boot guide.
4. Test League in the Practice Tool or a custom game. If VAN 1067 no longer appears, re-enable the disabled services and startup items in small groups until the error returns.
5. Once one program is confirmed, update it first. If no compatible update exists and you do not need the program, remove it through Installed apps and restart Windows.
   
6. If the culprit is still unclear, open Event Viewer > Windows Logs > Application and inspect errors recorded at the same time vgc.exe stopped. A named faulting module can identify the parent software.

Exact-error reports have identified conflicts involving Audinate/Dante, National Instruments or Bonjour discovery components such as mdnsNSP.dll, some audio-interface packages, and remote-access software.

These are clues, not a removal list. Do not delete a DLL by hand. Update or uninstall its parent application only after a clean boot or Event Viewer points to it.

Disconnect VPN software during the same baseline test. If Cloudflare WARP is installed, turn it off rather than adding it as another variable. WARP changes the network route, but it does not repair a Windows service that is crashing locally.

If League opens and remains stable in the clean boot, a disabled third-party component caused the conflict. Restore normal startup after identifying it. If vgc never starts even in the clean boot, go to the next method and check its service configuration.

3. Configure the Vanguard Service to Start Automatically

Vanguard can fail when vgc is disabled or stopped even though the anti-cheat remains installed. Automatic startup prevents the Riot Client from reaching League before the service is ready. This check is not needed when vgc does not appear in Services.

1. Press Windows + R, enter services.msc, and press Enter.
   
2. Find vgc, right-click it, and select Properties.
   
3. Set Startup type to Automatic.
4. Select Start, then Apply > OK.
   
5. Restart the PC and launch League again.

Riot documents the same automatic vgc configuration.

If the service remains running and League opens, its startup setting caused the error. If vgc is absent, refuses to start, or stops again immediately, go to the next method and reinstall Vanguard instead of repeatedly pressing Start.

4. Reinstall Riot Vanguard

A Vanguard reinstall is appropriate only if vgc is missing, cannot start, or still fails after its startup type is corrected. This rebuilds service files that may no longer match after an incomplete update, without removing League first.

1. Open Settings > Apps > Installed apps.
2. Find Riot Vanguard, select its menu, and choose Uninstall.
   
3. Restart the PC after the uninstall completes.
4. Open the Riot Client and launch League. Allow the client to reinstall Vanguard.
5. Restart Windows again when Riot requests it, then test League.

Riot’s Vanguard removal guide also provides manual service-removal commands, but those are necessary only when normal uninstall fails.