What if Valorant keeps saying Vanguard not initialized? If you are running into the error code 57 or 128 when playing this game in Windows 11/10, don’t panic and you come to the right place. MiniTool will show you some useful ways to fix Vanguard Anti-Cheat not initialized.
Vanguard Not Initialized Windows 11/10
Although Valorant is a famous and popular first-person shooter multiplayer game developed and published by Riot Games, it inevitably has some problems like other excellent games. Some common issues have been introduced in our previous post, for example, Valorant error code VAN 9001, your game requires a system restart to play, error code VAN 1067, Valorant FPS drops, etc.
Today, we will talk about another common issue – Valorant Vanguard not initialized error. Sometimes, you see the error code 128/57 on the screen. This error happens if the system or any other program is conflicting with the Vanguard Anti-Cheat system (VGC). If Vanguard is not installed properly, you may sometimes get the same error.
What if Valorant keeps saying Vanguard not initialized in Windows 11/10? Take it easy and you can find some useful solutions from the following part.
What should you do if you encounter the error code VAN 135 when playing Valorant? Try multiple ways to fix this connection error.
Riot Vanguard Not Initialized Fix
Exit and Re-Open Valorant Vanguard
Most times, a simple restart can fix some issues. When getting the Vanguard not initialized error in Windows 11/10, you can also try to exit Valorant Vanguard and re-launch it. Then, launch your game to see if the issue is fixed.
Reinstall Riot Vanguard
Step 1: Type Add or remove programs to the search box in Windows 10/11 and click the result.
Step 2: Locate Riot Vanguard and click Uninstall.
Step 3: Launch Valorant and Vanguard will reinstall.
Disable Windows Testing Mode
Windows testing mode allows you to run drivers that are not unverified, which may be clashing with Vanguard. As a result, Valorant Vanguard not initialized error code 57 or 128 appears. Follow the steps below to disable the mode.
Step 1: Launch Command Prompt in Windows 11/10 with admin rights.
Step 2: Type in the following commands in turn and press Enter after each one:
bcdedit -set TESTSIGNING OFF
bcdedit -set NOINTEGRITYCHECKS OFF
Step 3: Open Valorant, click Reboot Computer and wait for the PC to reboot. The game should run without any issue.
Set VGC Service to Automatic
Vanguard Anti-Cheat not initialized may appear due to the issue of the VGC service and you can set it to automatic.
Step 1: Press Win + R to open Run, type services.msc and click OK.
Step 2: Locate VGC, double-click it and change its Startup type to Automatic. Do the same thing for the Virtual Disk service.
Step 3: Click Apply > OK to save the changes.
Your current Windows version may conflict with Valorant Vanguard, leading to the not initialized error. To fix it, you can try to install Windows updates. Just go to Windows settings in Windows 10/11, locate the Windows Update section and check for updates. If some are available, download and install them on your PC.
It is useful to fix your issue by verifying and repairing Valorant’s corrupted game data and here is how to do the work:
Step 1: Click the link to download and install the installer of Valorant.
Step 2: Open this tool and click Advanced Options.
Step 3: Choose the path where Valorant is installed and click the Install button.
Step 4: The installer says repairing instead of installing. After the operation, restart the PC.
There is a tool in Windows to help you know which drivers are unsigned. After verification, you can remove or update the driver to fix your issue.
Step 1: Type sigverif in the Run window and press Enter.
Step 2: Click Start to begin file signature verification.
Step 3: If this tool detects any unsigned driver, it will tell you. Search for the driver in Google to check its origin. If it is an outdated driver, update it.
These are common fixes for Valorant Vanguard not initialized error code 128/57 in Windows 10/11. Try these solutions if you are running into the issue on your PC.