{"id":339832,"date":"2026-01-22T19:46:55","date_gmt":"2026-01-22T19:46:55","guid":{"rendered":"https:\/\/community.skin.club\/?p=339832"},"modified":"2026-01-22T19:46:55","modified_gmt":"2026-01-22T19:46:55","slug":"valve-remove-false-vac-bans-cs2-update","status":"publish","type":"post","link":"https:\/\/community.stage.jamson-sc.dev\/en\/news\/valve-remove-false-vac-bans-cs2-update","title":{"rendered":"Valve begin mass removal of false VAC bans in CS2 after update, players urged to avoid queueing"},"content":{"rendered":"

Following a recent update to Counter-Strike 2, the community has been hit by a wave of false VAC bans, issued without any apparent violations from players. Within hours of the first reports, initial confirmations began to surface that these sanctions were being automatically reversed, pointing to a malfunction within the Valve Anti-Cheat system.<\/p>\n

Early signals and insider response<\/h3>\n

One of the first to highlight the issue was well-known insider and analyst Thour<\/a>, who stated that Valve were already working on rolling back the false bans and urged players to avoid ranked modes until an official confirmation is made.<\/p>\n

It looks like Counter-Strike is now working on removing false VAC bans after the recent CS2 update. I would advise waiting for an official announcement before queueing, Thour wrote.<\/p><\/div><\/blockquote>\n

His post triggered a wave of replies from users confirming similar experiences on their own accounts.<\/p>\n\n

\n

read more<\/p>\n

\n
\n
<\/div>\n
\n
\n
\n \n \"s1mple\n <\/a>\n <\/figure>\n <\/div>\n \n
\n
\n
\n

\n \n s1mple couldn\u2019t save them: BC.Game botch their debut in the IEM Rio qualifier <\/a>\n <\/h3>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n
<\/div>\n<\/article> <\/div>\n<\/div>\n

Widespread confirmation: bans removed without contacting support<\/h3>\n

\"Image\"<\/p>\n

The most notable detail is that many VAC bans were lifted automatically<\/a>, without players needing to contact Steam Support. Users reported receiving ban removal notifications 10 to 30 minutes after the sanction was applied. The Steam message contained a clear statement:<\/p>\n

We apologize, it looks like we made a mistake and have removed this false ban.<\/p><\/div><\/blockquote>\n

Valve also confirmed that access to VAC-secured servers had been fully restored, emphasizing that the ban was the result of a system error rather than a rule violation.<\/p>\n

Historical context: this has happened before<\/h3>\n

As discussion intensified, the community quickly recalled a similar incident in December 2023, when a CS2 update mistakenly triggered VAC bans. At the time, Valve publicly acknowledged the issue and announced that ban rollbacks were underway. Thour referenced that case as well, noting Valve\u2019s tendency to fix such issues quietly:<\/p>\n

Historically, they don\u2019t always make announcements \u2014 they just roll the bans back. They\u2019ve done it before.<\/p><\/div><\/blockquote>\n

This reinforced the belief that the current situation is a systemic post-update error, not a new or stricter anti-cheat wave.<\/p>\n

Parallel concerns: FPS and optimization debate<\/h3>\n

Alongside the VAC incident, another discussion erupted within the community \u2014 a potential FPS drop following the update. Some players claimed performance losses of up to 30\u201335%, raising further alarm. However, Thour publicly disputed these claims after running his own benchmarks:<\/p>\n

I ran a benchmark and saw zero difference. Claiming a 30% FPS drop without evidence isn\u2019t reasonable.<\/p><\/div><\/blockquote>\n

The conflicting feedback highlighted the overall instability of the update and the chaotic nature of its initial rollout.<\/p>\n

Community reaction: relief mixed with distrust<\/h3>\n

Social media quickly filled with reactions from players confirming that their bans had been removed:<\/p>\n