ϟGAMECRASHFIX.com
Counter-Strike 2 / Online & account

Counter-Strike 2: disconnected by VAC or session cannot be verified

When CS2 shows “Disconnected by VAC: You cannot play on secure servers” or fails to verify your session, Valve says the cause is almost always third-party software interfering with the game or a broken Steam service – not a ban. The order below follows Valve's help article: known conflicts first, then the Steam service, Windows boot settings and system files. Test on an official server after each step.

Updated: ·3 min read·Windows / PC
YOUR FEEDBACK MATTERS

Did this fix help?

— helpful
Initial count + votes from the last 90 days

Voting stores an identifier for 24 hours to prevent repeat votes. Privacy policy

STRAIGHT TO THE SOLUTION

Start here

01Classify the error↓02Step 1: close known conflicts and verify files↓03Step 2: repair the Steam service↓
01

Classify the error

  1. Note the exact text and whether it appears on every server or only on one community server. Valve describes the message as the result of software interfering with the game or Steam.
  2. Check: if your Steam profile shows no VAC ban, this is a session or conflict problem. A real ban is shown separately on the profile and in the library.
02

Step 1: close known conflicts and verify files

  1. Valve lists CCleaner, PowerShell, Cheat Engine, IObit Start Menu 8, DLL injectors, hypervisors and Steam idlers as typical triggers. Exit them completely, including from the system tray. Also remove custom textures, skin changers or anything else that modifies game files.
  2. Restart the PC, then verify the game files (Properties → Installed Files → Verify integrity of game files).
  3. Check: if CS2 now works on official servers, re-enable the tools you need one at a time to find the trigger.
03

Step 2: repair the Steam service

  1. Exit Steam, press Windows key + R and run the repair command below. It needs administrator rights and may take a few minutes. If Steam lives in another folder, adjust the path.
  2. Check: start Steam and CS2 again. If the error is gone, the Steam service was the cause.
"C:\Program Files (x86)\Steam\bin\SteamService.exe" /repair
04

Step 3: restore Windows boot settings to default

  1. VAC-secured servers require kernel integrity checks, kernel debugging and Data Execution Prevention (DEP) to be at their defaults. Open Command Prompt as administrator, run the four bcdedit commands from the code block one after another and restart.
  2. If Windows says the value is protected by Secure Boot policy, Valve explains that it is already at the default – that is not an error.
bcdedit /deletevalue nointegritychecks
bcdedit /deletevalue loadoptions
bcdedit /debug off
bcdedit /deletevalue nx
05

Step 4: repair system files

  1. Run sfc /scannow in an administrator Command Prompt, restart when it finishes and test again. It replaces damaged Windows files that can break the check.
sfc /scannow
06

If it keeps happening

  1. If you deliberately use virtualisation software or a hypervisor (for development, for example), test one launch with that feature off. If the error persists after every step, contact Steam Support with your results.

Related guide

Sources and current status

Frequently asked questions

Does this message mean a VAC ban?

No. Valve describes it as the result of interfering software or a Steam service failure. A ban is shown explicitly on your profile.

Is running the bcdedit commands risky?

They return boot options to Windows defaults. If you changed these values on purpose for development or driver testing, note them first; VAC needs them at default.

Why does it only happen on one community server?

Then the server or its settings are the more likely cause. Valve's restart advice refers to errors that occur on all servers.

← All fixes for Counter-Strike 2