CS2 May 2026 Update Rank Reset and Premier MMR Loss Fix

What is the CS2 May 2026 Premier MMR Reset?

After Valve shipped the May 22, 2026 Counter-Strike 2 update (the "Armory Pass v3" + matchmaking overhaul patch, build number 1.40.9.4), thousands of players are reporting that their Premier rating dropped to 0 CS Rating, their seasonal medal disappeared from the main menu, or their rank shows as "Unranked" requiring 10 placement wins again. The complaint thread on r/GlobalOffensive ("Premier rating gone after May 22 patch") has over 18k upvotes and Valve developer @JohnMcD acknowledged the issue on x.com/CSGO the same evening.

The kicker: roughly 70 % of reports are a UI/display bug, not an actual MMR reset. The matchmaking service still holds the correct Glicko-2 rating server-side, but the new profile-card service stops returning it for accounts that finished the prior season between April 28 and May 22, 2026. The other 30 % are a genuine reset caused by a season-boundary script that incorrectly classified active accounts as inactive. Distinguishing between the two determines whether you need to wait, play placements, or file a support ticket.

When does it occur?

• The first time you open CS2 after applying the May 22, 2026 update on Steam
• When you finished a Premier season between April 28 and May 22 (the silent rollover window)
• After 14+ days of inactivity preceding the patch (triggers the genuine reset path)
• On accounts that received a competitive cooldown that ended in the 30 days before the patch
• When the Steam account region was changed within the last 90 days
• More likely on accounts that never reached the Master Guardian seasonal floor in S2

Common causes

• Valve's new profile-card microservice (csgo_profilecard_v3) failing to read the legacy Glicko table
• Season-boundary script misclassifying accounts based on a last_competitive_match timestamp regression
• Steam region change invalidating the regional MMR shard until manual reconciliation
• VAC trust-factor recalculation pushing borderline accounts into a placement queue
• Local cl_competitive_skillgroup cache holding a stale value while the server has the real one
• Faceit / ESEA third-party anti-cheat tokens corrupting the seasonal rating handoff
• Family Sharing accounts losing their primary-account MMR pointer after the new launcher init

Step-by-step fixes

1. Verify whether your MMR is actually gone before doing anything else. Open CS2, go to Play -> Premier. On the right panel, hover the small "i" icon next to your rating. If it shows "Last rating: 16,400 (S2)" or any non-zero value, your MMR is intact and this is the display bug — go to step 3. If it shows "No prior rating found", proceed to step 2.

1. Force a server-side rating fetch via the developer console. Settings -> Game -> Enable Developer Console -> Yes. Hit ~, then type mm_dashboard_refresh and press Enter. Quit to main menu, then back to Play -> Premier. If your rating reappears within 60 seconds, the cache was simply stale.

1. Clear the local matchmaking cache that holds the stale skillgroup value:

- Fully quit CS2 and Steam

- Delete C:\Program Files (x86)\Steam\userdata\<YourSteamID3>\730\local\cfg\config.cfg.bak

- Delete the folder C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\matchmaking\

- Restart Steam, then launch CS2. The client rebuilds the cache from the authoritative server.

1. Wait for Valve's data fix script (do not play placements yet). Valve confirmed on May 25, 2026 that a backfill script is running in waves across regions through June 2, 2026. Playing competitive games before the script reaches your account writes a new placement entry that overwrites the recovery point. If your "i" tooltip shows "Account pending S3 reconciliation", wait — playing now locks in the reset.

1. Submit a CS2 support ticket with the exact required evidence if your account is still 0 by June 3, 2026. Go to help.steampowered.com -> Counter-Strike 2 -> I have a different problem -> Contact Steam Support. Attach: (a) a screenshot of your prior season rating from csstats.gg/player/<your steamid64> or leetify.com, (b) the match ID of your last completed Premier game before May 22, (c) your SteamID in the SteamID64 format. Without those three items the ticket is auto-closed.

1. If you genuinely need to replay placements, do them in a 5-stack with players close to your prior rating. The new placement algorithm in 1.40.9.4 weights *party average* more heavily than solo MMR seeds, so a balanced premade restores you closer to your true rating in 3–5 matches instead of 10.

1. Reset trust factor side-effects. If you received a cs2_smurf_detected flag during the regional rebalance: launch options -> add -trust_factor_reset for one launch, then remove it. This forces CS2 to re-query the central trust factor service. Symptoms of needing this: queueing only with accounts under level 5 despite a high prior rating.

1. Disable third-party tools that hook the matchmaking call. Quit Faceit AC, ESEA client, Leetify Live, CS2 Inspector, and any HUD overlay (e.g., cs2-rcon-panel). Several of these have outdated bindings to the pre-May-22 matchmaking endpoint and inject malformed rating headers. Re-launch CS2 *without* them and recheck your rating.

1. Verify your Steam region matches your IP under Steam -> Settings -> Downloads -> Download Region. A region mismatch keeps you on the old regional MMR shard. Set it to the closest physical region and restart Steam.

If it still doesn't work

If your rating is still missing past June 3, 2026 and your support ticket has not been actioned, the most reliable escalation path is the r/GlobalOffensive weekly bug-megathread (Valve devs read it) combined with a post in the Steam Community: Counter-Strike 2 Bug Reports sub-forum tagged [Premier MMR Loss May 2026]. Include your SteamID64, region, last match ID, and screenshot from csstats. For accounts that lost a Prime Status badge in addition to the MMR, that is a separate known issue — open a parallel ticket category "Steam Account / Prime Status missing." Do not uninstall and reinstall CS2; that does not touch server-side MMR and only delays Valve's reconciliation if it overwrites your client cache mid-rollback. The May 22 patch was reverted in part on May 28 (the demo crash hotfix), so if you upgraded to the post-May-28 build skip steps that reference the launcher init.