By /

Valorant VAN 128 Driver Conflict Windows 11 24H2 – Proven Fixes (2026)

Table of Contents

Hub: Gaming Errors Hub

Quick Answer
A Valorant VAN 128 driver conflict Windows 11 24H2 error means Vanguard’s kernel-mode driver failed or detected an incompatible driver on your system. The fastest fixes include disabling Windows Test Mode, turning off Debug Memory Dump, updating or rolling back GPU drivers, and removing conflicting drivers like ene.sys from RGB software. If the error persists, reinstalling Vanguard or identifying unsigned drivers often resolves the problem immediately.

Why Valorant VAN 128 Driver Conflict Windows 11 24H2 Happens

When a Valorant VAN 128 driver conflict Windows 11 24H2 error appears, it typically displays as “Vanguard Not Initialized” or “Vanguard Anti-Cheat has not been initialized” with Error Code 128.[reference:0] This error indicates that Vanguard’s kernel-mode driver failed to load or detected an incompatible driver on your system. Understanding why Valorant VAN 128 driver conflict Windows 11 24H2 happens is the first step toward fixing it.

Windows 11 24H2 has introduced compatibility issues with some drivers, particularly RGB/lighting control software drivers like ene.sys (commonly installed by ASUS, MSI, and other motherboard manufacturers), as well as network adapters and other peripheral drivers.[reference:1][reference:2] Vanguard’s kernel-level anti-cheat is highly sensitive to unsigned, outdated, or incompatible drivers.[reference:3]

The most common causes include Windows Test Mode being enabled, allowing unverified drivers to run[reference:4]; the Debug Memory Dump setting interfering with Vanguard[reference:5]; unsigned drivers that fail Vanguard’s integrity checks[reference:6]; and specific conflicting drivers like ene.sys from RGB lighting software[reference:7].

Other potential causes include Fasoo or CryptoPro Cloud CSP security software[reference:8], outdated or corrupted GPU drivers[reference:9], Secure Boot or TPM 2.0 disabled on Windows 11[reference:10], and corrupted Vanguard installation.[reference:11] For more gaming troubleshooting, visit our Gaming Errors Hub.

⚠️ Warning: Before making any changes, simply restart your PC and try launching Valorant again. Sometimes the error is temporary and resolves after a reboot.[reference:12]

1. Restart Vanguard and Your PC

The simplest and most effective first step when encountering a Valorant VAN 128 driver conflict Windows 11 24H2 error is to restart Vanguard and your PC. Vanguard must load at boot, and a reboot is more reliable than just relaunching the game.[reference:13]

  1. Fully close Valorant and the Riot Client.
  2. In the system tray, right-click the Vanguard (Riot) icon and select Exit or Quit.
  3. Restart your PC—Vanguard loads at boot, so this is essential.[reference:14]
  4. Launch Valorant again and check if the error is resolved.

✅ Expected Result: The game should launch without the VAN 128 error. If the Valorant VAN 128 driver conflict Windows 11 24H2 persists, proceed to the next method.

2. Disable Windows Test Signing Mode

Windows Test Mode allows unverified drivers to run, which can conflict with Vanguard’s security protocols and trigger a Valorant VAN 128 driver conflict Windows 11 24H2 error.[reference:15]

  1. Press Windows + R, type cmd, press Enter.
  2. Right-click Command Prompt and select “Run as administrator”.
  3. Enter the following command and press Enter: bcdedit /set TESTSIGNING off[reference:16]
  4. Enter this command as well: bcdedit /set nointegritychecks OFF[reference:17]
  5. Restart your computer.
  6. Launch Valorant and test.

💡 Quick Tip: If you previously enabled Test Mode for other purposes, forgetting to disable it can cause Vanguard to fail initialization.

3. Disable Debug Memory Dump

Windows’ default debugging settings can sometimes interfere with Vanguard. Disabling the Debug Memory Dump has resolved this issue for many players.[reference:18]

  1. Press Windows + R, type sysdm.cpl, and press Enter.[reference:19]
  2. Go to the Advanced tab.
  3. Under Startup and Recovery, click Settings.
  4. Change the “Write debugging information” dropdown to (none).[reference:20]
  5. Click OK and restart your computer.

🔁 Alternative Solution: Some users have also resolved the VAN 128 error by setting the “Write debugging information” to “Small memory dump” instead of “(none)”.

4. Identify and Remove Unsigned Drivers

Unsigned drivers can fail Vanguard’s integrity checks, causing a Valorant VAN 128 driver conflict Windows 11 24H2 error.[reference:21] Identifying and removing them can resolve the issue.

  1. Press Windows + R, type sigverif, and press Enter.[reference:22]
  2. Click “Start” to scan for unsigned drivers.
  3. Review the list of unsigned drivers found.
  4. For each unsigned driver, try updating it through Device Manager or the manufacturer’s website.
  5. If updating is not possible, consider removing the associated software.
  6. Restart your PC and test Valorant.

❌ Common Mistake: Removing critical system drivers can cause system instability. Only remove or update drivers you can identify as non-essential or from third-party software.

5. Update or Roll Back GPU Drivers

Outdated or incompatible GPU drivers are a common cause of Valorant VAN 128 driver conflict Windows 11 24H2. Updating to the latest stable version—or rolling back to a version known to work—can resolve the issue.[reference:23]

  1. Update GPU Driver: Open GeForce Experience (NVIDIA) or Radeon Software (AMD) and check for updates. Do a clean installation if possible.[reference:24]
  2. If the error started after a recent driver update, roll back to a previous version. Some users have reported that rolling back to NVIDIA driver 566.36 fixed VAN 128 issues.[reference:25]
  3. Open Device Manager, expand Display adapters, right-click your GPU, and select Properties > Driver > Roll Back Driver (if enabled).
  4. Restart your PC and test Valorant.

💡 Quick Tip: If you’re using an NVIDIA RTX 50 series card, some driver versions are known to cause issues with Valorant. Try driver version 566.36 or newer stable releases.[reference:26]

6. Rename or Remove Conflicting Drivers (ene.sys)

One of the most common causes of Valorant VAN 128 driver conflict Windows 11 24H2 is the ene.sys driver, which is often installed by RGB lighting software from ASUS, MSI, or other manufacturers.[reference:27] Renaming or removing this driver can resolve the issue.

  1. Navigate to C:\Windows\System32\drivers\.[reference:28]
  2. Find the file ene.sys.[reference:29]
  3. Right-click it and select Rename.
  4. Change the name to ene.sys.old.[reference:30]
  5. Restart your computer.[reference:31]
  6. Launch Valorant—it should now run without issues.[reference:32]

⚠️ Warning: Renaming system drivers can affect the functionality of associated hardware (like RGB lighting). If you notice issues, rename the file back to its original name.

7. Uninstall Conflicting Software (Fasoo, CryptoPro, RGB Tools)

Certain software is known to conflict with Vanguard and trigger a Valorant VAN 128 driver conflict Windows 11 24H2 error.

  1. Fasoo: This security software can cause conflicts with Riot Vanguard. Uninstall it through Control Panel > Programs and Features.[reference:33]
  2. CryptoPro Cloud CSP: This software commonly shows as cpinit.exe in Task Manager. Uninstall or disable it through Control Panel.[reference:34]
  3. RGB/Lighting Software: ASUS Aura/Armoury Crate, MSI RGB, and similar tools often install incompatible drivers.[reference:35]
  4. After uninstalling, restart your PC and test Valorant.

🔁 Alternative Solution: Instead of uninstalling RGB software entirely, try updating it to the latest version, as newer versions may have fixed compatibility issues with Vanguard.[reference:36]

8. Enable Secure Boot and TPM 2.0

On Windows 11, Vanguard requires both Secure Boot and TPM 2.0 to be enabled.[reference:37] If either is turned off, Valorant may fail to launch with a VAN error.[reference:38]

  1. Check Secure Boot: Press Windows + R, type msinfo32, and press Enter. Confirm Secure Boot State is On and BIOS Mode is UEFI.[reference:39]
  2. Check TPM 2.0: Press Windows + R, type tpm.msc, and press Enter. It should say TPM 2.0, ready for use.[reference:40]
  3. If either is disabled, restart your PC and enter UEFI/BIOS (usually by pressing F2, F12, or Delete during boot).
  4. Navigate to the Security or Boot tab.
  5. Enable Secure Boot and TPM 2.0 (may be listed as “PTT” for Intel or “fTPM” for AMD).
  6. Save changes and exit BIOS.
  7. Restart your PC and test Valorant.

💡 Quick Tip: If you’re using a custom-built PC, your motherboard manual will have specific instructions for enabling Secure Boot and TPM.

9. Reinstall Vanguard

If none of the above methods resolve the Valorant VAN 128 driver conflict Windows 11 24H2 error, a clean reinstall of Vanguard is the next logical step. This removes deeply corrupted configuration files that may be causing the issue.[reference:41]

  1. Open Settings > Apps > Installed apps.
  2. Find Riot Vanguard and click Uninstall.[reference:42]
  3. Restart your PC—this is critical before reinstalling.[reference:43]
  4. Launch Valorant—the game will automatically reinstall Vanguard.[reference:44]
  5. If prompted, restart your PC again to complete the Vanguard installation.[reference:45]
  6. Launch Valorant and test.

✅ Expected Result: A clean reinstall of Vanguard should resolve the Valorant VAN 128 driver conflict Windows 11 24H2 error. If the error persists, proceed to advanced troubleshooting.

Advanced Troubleshooting for Valorant VAN 128 Driver Conflict Windows 11 24H2

If none of the standard methods resolve the Valorant VAN 128 driver conflict Windows 11 24H2 error, deeper system issues may be involved. Here are advanced solutions for persistent cases.

Run System File Checker (SFC):

  1. Open Command Prompt as Administrator.
  2. Type sfc /scannow and press Enter.
  3. Wait for the scan to complete and restart your PC.

Disable Overlays and Background Apps:

  1. Disable overlays from Discord, NVIDIA GeForce Experience, and other applications.
  2. Close MSI Afterburner, RivaTuner, and other monitoring tools while testing.[reference:46]

Reset the vgk Driver from Command Prompt:

  1. Open Command Prompt as Administrator.
  2. Run these commands one at a time:
    • sc stop vgc
    • sc stop vgk
    • sc start vgk
    • sc start vgc
  3. Launch Valorant and test.[reference:47]

Contact Riot Support:

  1. If all else fails, submit a ticket to Riot Games Support.
  2. Include details about your system configuration and the steps you have already tried.

For more gaming troubleshooting, explore our Gaming Errors Hub.

Conclusion

Encountering a Valorant VAN 128 driver conflict Windows 11 24H2 error is frustrating, especially when you’re eager to play. However, the vast majority of cases are resolved with the methods above. Start with the simplest fixes—restarting Vanguard and your PC—before progressing to more advanced solutions like disabling Test Mode, removing conflicting drivers like ene.sys, or reinstalling Vanguard.

If you have tried every fix and the Valorant VAN 128 driver conflict Windows 11 24H2 error still persists, consider that the problem may be related to Windows 11 24H2’s compatibility issues with certain drivers. Check for Windows updates or contact Riot Support for further assistance. For broader gaming troubleshooting, explore our Gaming Errors Hub.

For similar Vanguard and anti-cheat issues on other platforms, check out our guides on Riot Vanguard Not Initialized or Valorant VAN Error Codes.

Related Guides

FAQ

What is Valorant VAN 128 driver conflict Windows 11 24H2?

VAN 128 is a Vanguard error that occurs when the anti-cheat’s kernel-mode driver fails to load or detects an incompatible driver. Windows 11 24H2 has introduced compatibility issues with certain drivers, making this error more common.

How do I fix Valorant VAN 128 driver conflict?

Start by restarting your PC and Vanguard. Then disable Windows Test Mode and Debug Memory Dump. Update or roll back your GPU drivers, and rename or remove conflicting drivers like ene.sys from RGB software. If the error persists, uninstall conflicting software or reinstall Vanguard.

What is the ene.sys driver and why does it cause VAN 128?

ene.sys is a driver commonly installed by RGB lighting software from ASUS, MSI, and other motherboard manufacturers. Vanguard flags it as incompatible, causing VAN 128. Renaming the file to ene.sys.old and restarting your PC resolves the issue.

Can disabling Test Mode fix VAN 128?

Yes, Windows Test Mode allows unverified drivers to run, which can conflict with Vanguard. Disabling it with the command bcdedit /set TESTSIGNING off often resolves the VAN 128 error.

Does disabling Debug Memory Dump fix VAN 128?

Yes, Windows’ debugging default settings can interfere with Vanguard. Changing the “Write debugging information” dropdown to “(none)” in sysdm.cpl and restarting your PC has resolved VAN 128 for many users.

What software conflicts with Vanguard?

Fasoo security software, CryptoPro Cloud CSP, and RGB lighting software (ASUS Aura/Armoury Crate, MSI RGB) are known to conflict with Vanguard. Uninstalling or updating these programs often resolves VAN 128.

Does Windows 11 24H2 cause Valorant driver errors?

Yes, Windows 11 24H2 has introduced compatibility issues with some drivers, particularly RGB/lighting control software drivers and network adapters. Many users have reported VAN 128 errors after updating to 24H2.

Does reinstalling Vanguard fix VAN 128?

Yes, reinstalling Vanguard removes deeply corrupted configuration files that may be causing the error. Uninstall Vanguard, restart your PC, and launch Valorant to trigger a clean reinstall.

HowToFixPro Editorial Team

We’re a team of system administrators, technical writers, and platform specialists who genuinely enjoy solving the problems most users find frustrating. From persistent Windows errors and Android sync failures to browser crashes and network drops — we’ve seen it all, and we document every fix properly. Our guides are built on official documentation, direct testing, and real troubleshooting experience. No filler, no guesswork — just reliable, step-by-step solutions you can trust.

Scroll to Top