VAN 138 in VALORANT: Vanguard won't run in a virtual machine

Connection Error: VALORANT encountered a connection error. Please relaunch the client to reconnect.

Both of Riot's sources agree

VAN 138 is one of the clearer codes. Riot's VALORANT table and its Vanguard article both say the same thing: VALORANT and Vanguard are being run from a virtual machine, and that isn't permitted. Vanguard needs to load as a driver on a real Windows install, so no VM setting will make it pass.

That includes running Windows inside a VM on a Mac or on Linux. The game and Vanguard both have to live on Windows installed on the machine itself.

If you aren't using a VM

Riot's article keeps going for players who get 138 without knowingly running a virtual machine. After the VM step come a Vanguard reinstall, a clean boot, a firewall check and a VALORANT reinstall. The firewall step on this page uses Riot's VALORANT firewall guide, with the exact files to allow.

Riot's fix, in Riot's order

1. Run the game on Windows itself, not inside a virtual machine

   Vanguard refuses to run inside VirtualBox, VMware, Parallels or any other virtualized setup. The game and Vanguard have to be installed on a normal Windows install on the PC itself.

2. Uninstall Vanguard, restart, and let the game reinstall it

   1. Close the game and exit the Riot Client from the system tray.
   2. Right-click the red Vanguard icon in the tray, choose Advanced, then Uninstall Vanguard. If the icon isn't there, search Windows for Add or remove programs and uninstall Riot Vanguard from the list.
   3. Restart the PC. Vanguard is gone if its tray icon doesn't come back.
   4. Open the Riot Client and launch the game. It reinstalls Vanguard and will ask for one more restart before Play unlocks.

   Riot's guide: Uninstall Vanguard, restart, and let the game reinstall it

3. Do a clean boot

   This switches off every non-Microsoft service for one boot, so you can tell whether something in the background is the problem.

   1. Press Win+R, type msconfig and press Enter.
   2. On the Services tab, tick Hide all Microsoft services first (skip it and you'll switch off parts of Windows).
   3. Click Disable all, then tick vgc again so Vanguard still starts.
   4. Apply, OK, restart, and test.

   Some programs ignore a clean boot anyway, third-party antivirus and networking tools most of all. If the error goes away, turn services back on a few at a time until it returns, and you've found it.

   Riot's guide: Do a clean boot

4. Let the Riot Client through your firewall

   In Windows Defender Firewall, open Allow an app through Windows Firewall and click Change settings. Delete the VALORANT and Riot Client entries already there, then use Allow another app to add three fresh ones with every box ticked:

   • C:\Riot Games\VALORANT\live\VALORANT.exe
   • C:\Program Files\Riot Vanguard\vgc.exe
   • C:\Riot Games\Riot Client\RiotClientServices.exe

   Those are the default install paths. If you put VALORANT on another drive, point at that copy instead.

   Riot's guide: Let the Riot Client through your firewall

5. Reinstall the game

   Close the Riot Client first, then uninstall VALORANT from Windows' Installed apps list. For a clean reinstall, Riot's guide has you remove the VALORANT and Riot Client folders inside C:\Riot Games, empty the Recycle Bin, then delete the Riot Games and VALORANT folders under %localappdata%. Restart, then download the installer again from Riot's site.

   Riot's guide: Reinstall the game

Related VALORANT errors

• VAN 128
• VAN -81
• VAN 289

Source: Riot Games Player Support, Error VAN 138, updated July 14, 2026, and Riot's VALORANT code table, Error Codes and Solutions in VALORANT. Riot's steps are paraphrased here, not copied; checked October 8, 2026.