XPLOITR
Report a bug or exploit
Battlefield 6Battlefield 6 · PC · version 2026 updates

Error 0:85009S drops players from matches

UnconfirmedUnpatched

Updated

Players are thrown back to the menu mid-match with error 0:85009S, sometimes within a few minutes. The same thread also names 0:85008S and 0:85011S. It was reported through the spring and summer, and players said it had returned on Oct 25.

Lifecycle

Reported · stage 1 of 5

160days open

Since first report

  1. Reported (reached) · now
  2. Confirmed (not yet)next
  3. Acknowledged (not yet)—
  4. Partial (not yet)—
  5. Patched (not yet)—
In current stage 160d
Workaround available
Game
Battlefield 6
Platform
PC
Affected version
2026 updates
Kind
Bug
Confirmation
Unconfirmed
Patch status
Unpatched
First reported
Last updated
Latest fix or workaround
Workaround, : Oct 25: a player says the error stopped after deleting the game's Documents folder and turning FSR off. Source
How we label issues

Kind

  • Exploit: Repeatable and clearly advantageous to the player using it; essentially cheating.
  • Bug: Everything else: crashes, launch errors, broken features, visual or audio faults.

Confirmation

  • Confirmed: A developer or official account acknowledged it, an official known-issues board lists it, it appears in official patch notes, or 100+ corroborating posts on X were actually counted.
  • Unconfirmed: None of the above yet. Press articles are reports and never confirm an issue on their own.

Patch status

  • Unpatched: Known and open; no fix has been claimed.
  • Reported as unpatched: Players credibly report it persisting, including after a fix claim that never appeared in patch notes.
  • Partially patched: Official patch notes list a fix, but credible later reports say it still happens, or the notes only cover part of it.
  • Reported as patched: A developer, official account or player says it is fixed, but no official patch notes list it.
  • Patched: Official patch notes (a Steam news post or the publisher's patch notes page) list the fix, and nothing credible says it still happens.

Active means still affecting players: Unpatched, Reported as unpatched or Partially patched. Patched and Reported as patched issues are closed.

Estimated impact runs from 0.1 to 9.9 with one decimal. xploitr sets it from the rubric below. Factors: advantage to other players, reach, play blocked or progress lost, frequency, and whether a reliable workaround exists. Patched issues keep their historical impact.

Signed-in community members can report new issues and suggest status changes, such as Fixed or Still unpatched, with their platform, version and a source. Every report and suggestion is reviewed by an editor before anything on the record changes. A new issue is published only when the report has at least three independent sources (distinct accounts, or distinct sites for web pages, after blocked sources are removed), unless the owner approved that issue by hand. Approved input appears as a dated Update from the xploitr community source on the issue's timeline, credited to the member's username (reports can opt out and stay anonymous); nothing is counted or published automatically.

Impact bands

  • 0.1–2.9 Low: Cosmetic, audio, text and UI glitches with no effect on play.
  • 3.0–4.9 Moderate: Narrow gameplay bugs or small exploits, rare or with a workaround.
  • 5.0–6.9 Elevated: Bugs most players in a mode notice: hit registration, desync, balance-breaking damage.
  • 7.0–8.4 High: Widely abused competitive or economy exploits; crashes many players hit.
  • 8.5–9.9 Severe: Launch blockers, widespread progress or item loss, exploits that break the game for everyone.

Each issue has a dated timeline of updates (report, acknowledgement, announcement, fix, workaround). Update summaries are our own words; quotes and excerpts are the source's words, or our English translation when marked.

Estimated impactEstimated impact 6.0 out of 9.9, ElevatedOur estimate from how many players it reaches and what it costs them.

Updates · 11

Show all 11 updates
  1. Workaround

    Oct 25: a player says the error stopped after deleting the game's Documents folder and turning FSR off.

    Community report · Steam · Forum reply ·
    “Then realizing that when I turn on FSR, I get this error.”
    Community report · Steam · Forum reply · Open source
  2. Report

    Oct 26: translated from Russian: a player asks whether the developers are going to fix this error at all.

    Community report · Steam · Forum reply ·
    Community report · Steam · Forum reply · Open source
  3. Report

    Translated from Chinese: Oct 26, a player says that since an update a few days ago the error kicks them from every match about five minutes in, even after reinstalling the game and EA's anti-cheat several times.

    Community report · Steam · Forum thread ·
    Community report · Steam · Forum thread · Open source
  4. Report

    Oct 26: another player got the error and is giving up on the game.

    Community report · Steam · Forum reply ·
    “Got the error aswell”
    Community report · Steam · Forum reply · Open source
  5. Report

    Oct 27: translated from Russian: a player tried every suggested fix, reinstalled Windows and switched to a neighbour's Wi-Fi on another provider, and still got the error after 9 minutes.

    Community report · Steam · Forum reply ·
    Community report · Steam · Forum reply · Open source
Sources · 1111 CommunityCommunity reportSteam · Forum reply+ 10 similar community reportsShow all →
Community reportSteam · Forum reply
“its again, i played 1 month without problem. but after update again”
  • Community reportSteam · Forum replyOpen
    “I'm kicked out of a match every two minutes with this error: UNKNOWN ERROR CODE 0:85009S.”
  • Community reportSteam · Forum replyOpen
    “It also throws me out in the middle of a match with Error Code 0:85009S or 0:85011S. It started today.”
Show all 11 sources