VAN 152 Valorant: What It Means and How to Fix It
Valorant error VAN 152 means Vanguard has blocked your access. Learn whether it signals a ban or a fixable issue, and how to resolve it step by step.
By SensePublished
What Is VAN 152?
VAN 152 is a Valorant error code tied to Riot Vanguard, the game's kernel-level anti-cheat system. When you see VAN 152, it means Vanguard has determined that something about your system does not meet its requirements or that your access has been restricted. The error typically prevents you from launching into a game entirely.
The tricky part about VAN 152 is that it can appear for very different reasons. For some players, it is a temporary technical glitch that resolves with a reboot. For others, it is the visible symptom of an HWID ban. Understanding which situation you are in determines your course of action.
The Two Faces of VAN 152
VAN 152 as a Technical Issue
In many cases, VAN 152 appears because Vanguard is not running correctly. This can happen when:
- Vanguard's kernel driver failed to load at boot
- A Windows update changed something that conflicts with Vanguard
- Secure Boot or TPM settings were altered in BIOS
- Vanguard's files were corrupted
- Another kernel-level driver is conflicting with Vanguard
In these cases, the error is fixable and does not indicate any problem with your account.
VAN 152 as a Ban Indicator
VAN 152 can also appear when Vanguard has flagged your hardware. If your machine's HWID has been banned, Vanguard blocks access at the anti-cheat level, and VAN 152 is one of the error codes that surfaces. In this case, technical fixes will not help because the block is intentional and server-side.
The error message itself does not tell you which scenario you are dealing with. You need to work through the technical fixes first. If none of them resolve the issue, an HWID ban is the likely explanation.
Technical Fixes for VAN 152
Start with these. If VAN 152 is a technical issue, one of these steps will resolve it.
Fix 1: Reboot Your Computer
Vanguard's kernel driver (vgk.sys) loads during the Windows boot process. If your system resumed from sleep or hibernation, or if you shut down with Fast Startup enabled, the driver may not have loaded properly.
Do a full restart: Start menu > Restart (not Shut Down, since Fast Startup can skip driver initialization on a cold boot following shutdown).
After the restart, check that the Vanguard tray icon (a small shield near the clock) is visible. If it is, try launching Valorant.
Fix 2: Verify Vanguard Service Is Running
Vanguard runs as a Windows service called vgc. If the service stopped or failed to start, Valorant cannot launch.
- Press Win + R, type
services.msc, and press Enter - Scroll to "vgc" in the list
- Check its status. It should say "Running"
- If it is stopped, right-click and select "Start"
- Set the Startup Type to "Automatic" if it is not already
Alternatively, in an elevated Command Prompt:
net stop vgc
net start vgcIf the service refuses to start, a reboot is necessary to reload the kernel driver.
Fix 3: Enable Secure Boot and TPM 2.0
Since 2023, Valorant on Windows 11 requires both Secure Boot and TPM 2.0 to be enabled. VAN 152 appears if either is disabled.
To check Secure Boot:
- Press Win + R, type
msinfo32, press Enter - Look for "Secure Boot State" — it should say "On"
To check TPM:
- Press Win + R, type
tpm.msc, press Enter - You should see "The TPM is ready for use" and a version of 2.0 or higher
If either is disabled, you need to enable them in your BIOS/UEFI settings:
- Restart your PC and enter BIOS (usually by pressing Del, F2, or F12 during boot — the key depends on your motherboard)
- Navigate to Security or Boot settings
- Enable Secure Boot (you may need to set it to "Windows UEFI" mode first)
- Enable TPM (labeled as "Intel PTT" on Intel boards or "AMD fTPM" on AMD boards)
- Save and exit
After enabling these settings, Windows may need a moment to recognize the changes. Restart once more and try Valorant.
Fix 4: Update Windows
Outdated Windows builds can conflict with Vanguard's driver. Riot regularly updates Vanguard to work with the latest Windows patches, and running an old build can cause VAN 152.
- Open Settings > Windows Update
- Click "Check for updates"
- Install all available updates, including optional ones
- Restart when prompted
Pay special attention to cumulative updates and driver updates. Some VAN 152 waves have been traced to specific Windows updates that temporarily broke compatibility with Vanguard.
Fix 5: Reinstall Vanguard
A corrupted Vanguard installation can cause persistent VAN 152. Reinstalling gives you a clean copy:
- Open Settings > Apps > Apps & features
- Search for "Riot Vanguard"
- Click Uninstall
- Restart your computer
- Launch Valorant through the Riot Client
- The client will detect Vanguard is missing and prompt installation
- Install and restart again
Two restarts are key here. The first removes the old driver, and the second ensures the new driver loads cleanly at boot.
Fix 6: Check for Driver Conflicts
Vanguard operates at the kernel level (Ring 0) and can conflict with other kernel-level software. Known conflict sources include:
- Other anti-cheat engines running simultaneously (FaceIT, ESEA, other game anti-cheats)
- Virtualization software like VMware, VirtualBox, or Hyper-V in some configurations
- Certain RGB or fan control software that installs kernel drivers
- Overclocking utilities that use low-level hardware access
- Some antivirus products with kernel-level components
To test for conflicts:
- Open Task Manager > Startup tab
- Disable non-essential startup items
- Restart and test Valorant
- If it works, re-enable items one at a time to find the conflict
For a more thorough test, perform a clean boot:
- Press Win + R, type
msconfig, press Enter - Under the Services tab, check "Hide all Microsoft services"
- Click "Disable all" (this will disable third-party services)
- Under the Startup tab, open Task Manager and disable all startup items
- Restart and test Valorant
- If it works, gradually re-enable services to isolate the conflict
Fix 7: Repair Valorant Installation
Use the Riot Client's built-in repair:
- Open the Riot Client (not through the Valorant shortcut, but the Riot Client directly)
- Click your profile icon > Settings
- Select Valorant from the sidebar
- Click "Repair"
- Wait for the process to complete
- Restart Valorant
Fix 8: Check BIOS Settings for Virtualization
Some players have reported that VAN 152 relates to virtualization settings in BIOS. Vanguard has, at various times, had issues with certain virtualization configurations.
In BIOS:
- Intel VT-x (Intel Virtualization Technology): Try both enabled and disabled to see which resolves VAN 152
- AMD-V (AMD Virtualization): Same approach
- Hyper-V in Windows: If enabled and not needed, try disabling it via "Turn Windows features on or off"
The relationship between virtualization settings and VAN 152 has changed across Vanguard updates, so what worked for one version may not apply to the current one.
When VAN 152 Means You Are HWID Banned
If you have tried every technical fix above and VAN 152 persists, or if VAN 152 appeared immediately after you were banned on another account, the error is likely indicating an HWID ban.
Additional signs that point to an HWID ban rather than a technical issue:
- The error appeared right after a ban on a different account. If account A was banned for cheating and you immediately see VAN 152 on account B using the same PC, that is an HWID ban.
- Fresh Windows install does not help. Reinstalling Windows changes the Machine GUID and volume serials but does not change hardware serials, motherboard identifiers, or the system UUID. If VAN 152 survives a clean OS install, it is hardware-level.
- Other games work fine. If Steam, Epic, and other clients work normally but Valorant specifically shows VAN 152, the issue is specific to Vanguard's checks on your hardware.
- Riot Support confirms the ban. You can submit a ticket to Riot asking about your account status. If they confirm a ban associated with your hardware, that settles it.
What to Do About an HWID Ban
If VAN 152 is confirmed to be an HWID ban, your options are:
Appeal Through Riot Support
Submit a ticket explaining your situation. Be honest. If you cheated, acknowledge it and ask about the possibility of a second chance. If you believe the ban is a mistake (for example, you bought a used computer), explain that.
Riot's success rate for reversing HWID bans is low, but it is not zero. Mistaken bans do happen, and Riot has reversed them in documented cases.
Replace Key Hardware Components
Replacing your motherboard and primary storage drive would change the most significant identifiers in the fingerprint. However, Vanguard checks a wide range of identifiers at the kernel level, and partial hardware changes may not be enough.
Use an HWID Spoofer
An HWID spoofer intercepts Vanguard's hardware queries at the kernel level and returns spoofed values. Because Vanguard itself operates at Ring 0, the spoofer must also operate at this level to be effective.
Sense AC's spoofer is built for exactly this scenario. It works at the kernel level to spoof the full range of identifiers that Vanguard checks, including disk serials, motherboard and BIOS information, system UUID, MAC addresses, and other hardware fingerprinting data. By presenting Vanguard with a completely new hardware identity, it allows you to create a fresh account and play without triggering the HWID ban.
VAN 152 vs Other Valorant Error Codes
Valorant has many error codes, and knowing which is which helps with troubleshooting:
| Error Code | Meaning |
|---|---|
| VAL 5 | Client cannot connect to platform services |
| VAN 9001 | Vanguard not initialized, requires restart |
| VAN 68 | Connection timeout to Vanguard |
| VAN 81 | Vanguard encountered an error |
| VAN 128 | Vanguard requires Secure Boot |
| VAN 152 | Vanguard has restricted access (technical or ban) |
| VAN 1067 | Vanguard service failed to start |
VAN 152 is unique in that it can be either a technical issue or a ban indicator. Most other VAN codes point to specific technical problems.
Preventing VAN 152
To minimize your chances of encountering VAN 152 as a technical issue:
- Keep Vanguard and Windows updated. Compatibility issues are usually patched quickly.
- Do not disable Secure Boot or TPM. Some tweaking guides suggest disabling these for performance, but they are required for Valorant.
- Avoid kernel-level software conflicts. If you run other anti-cheats or low-level utilities, be aware of potential conflicts.
- Use a full restart, not sleep or hibernate, if you have been experiencing issues. This ensures Vanguard's driver loads cleanly.
Summary
VAN 152 is Vanguard's way of saying something is wrong, but it does not specify what. For most players, it is a technical issue resolved by rebooting, checking BIOS settings, or reinstalling Vanguard. For players who have been HWID banned, VAN 152 is the wall that stops them from playing on any account. If you have exhausted every technical fix and the error persists, an HWID ban is almost certainly the cause. In that case, Sense AC's kernel-level HWID spoofer provides a way to reset your hardware identity and get past the restriction.