VALORANT articles ↗
WALKER BEX›VALORANT›VAN 138 · VIRTUAL MACHINE
VALORANT · VANGUARD FIX

VAN 138 Virtual Machine Fix

If Vanguard says a virtual machine was detected, the real fix is simpler than most guides make it sound: stop running the game in a virtualized environment.

Walker Bex Guides••7 min read
ON THIS PAGE

The quick answer

Run VALORANT and Vanguard on a normal Windows installation, not a VM.

Riot says VAN 138 appears when VALORANT or Riot Vanguard is being run from a virtual machine or unsupported virtualized environment. The main fix is to install and launch both on a regular Windows instance. If you already are on a normal PC, reinstall Vanguard and test again. If the detection still looks wrong, send Riot a ticket with logs.

Jump into the guide

01 What does VAN 138 mean?

This is a Vanguard environment check. Riot treats virtual machines and unsupported virtualized environments as incompatible with Vanguard, so the game refuses to continue.

That means the fix is not about tweaking graphics or network settings. It is about where the game is running and how Vanguard sees the system underneath it.

02 First, make sure you are using regular Windows

  1. If you are actually using a VM, stop there

    Install VALORANT and Riot Vanguard on a standard Windows installation instead. Riot’s support guidance is clear that virtual machines are not supported for this use case.

  2. If you are using cloud or remote-hosted Windows, treat it the same way

    Unsupported virtualized environments can trigger the same type of detection.

  3. If you are on your own physical PC, continue to the next section

    False or confusing detections can happen, so the next step is to restore Vanguard cleanly.

Short version: VAN 138 is not something you “work around” on a VM. The supported path is a normal Windows installation.

03 Reinstall Vanguard after moving or if you are already on a normal PC

  1. Close VALORANT and Riot Client

    Make sure everything Riot-related is fully closed.

  2. Uninstall Riot Vanguard

    Use Windows Settings → Apps or the current Riot uninstall guide.

  3. Restart Windows

    This helps clear the old Vanguard state.

  4. Launch Riot Client / VALORANT again

    Let Vanguard reinstall normally, then test the game.

04 If it still says virtual machine detected

You were definitely on a VMThe fix is to switch to a regular Windows installation. No article can make the VM itself supported.
You are on a physical PCRecheck after reinstalling Vanguard. If the detection still seems wrong, gather logs for Riot Support.
You changed several system tools recentlyTell Riot about that in the ticket, especially if you use advanced virtualization or isolation tools.
You also see startup or Vanguard errorsNote the exact codes; they may point to a second issue happening alongside VAN 138.

Do not start disabling random Windows security features to fight VAN 138. That is more likely to create new Vanguard errors than solve this one.

05 Frequently asked questions

Can I play VALORANT inside a virtual machine?

Riot’s support guidance says no. VALORANT and Vanguard need to run on a regular Windows installation.

What if I am not using a VM?

Reinstall Vanguard and test again. If the alert still appears, send Riot a ticket with logs because the detection may need support-side review.

Is VAN 138 a network error?

No. It is an environment / Vanguard compatibility issue, even though Riot labels it under a broader connection-style message.

Should I keep trying workaround tools?

No. Use the supported route: regular Windows, clean Vanguard reinstall, then Riot Support if needed.

06 Sources & update notes

This article is written independently for Walker Bex. Support guidance checked October 10, 2026.