XPLOITR
Report a bug or exploit
Call of Duty: Modern Warfare 4Call of Duty: Modern Warfare 4 · PC · version Launch (Oct 2026)

"LIVORNO NAVAJO" error after DMZ matches

UnconfirmedUnpatched

Updated

Several Steam players say an error named LIVORNO NAVAJO appears at the end of DMZ matches and they have to fully restart the game each time. Some say it started after early access. No acknowledgement from Infinity Ward or Activision found.

Lifecycle

Reported · stage 1 of 5

6days 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 6d
Workaround none yet
Game
Call of Duty: Modern Warfare 4
Platform
PC
Affected version
Launch (Oct 2026)
Kind
Bug
Confirmation
Unconfirmed
Patch status
Unpatched
First reported
Last updated
Latest fix or workaround
None on the record
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 5.5 out of 9.9, ElevatedOur estimate from how many players it reaches and what it costs them.

Updates · 6

Show fewer
  1. Report

    Oct 24: the error appears after every match and the game has to be restarted each time.

    Community report · Steam · Forum thread ·
    “?!! what is this, very annoying, I have to restart it every single match.”
    Community report · Steam · Forum thread · Open source
  1. Report

    Oct 24: another player has had it in their last two games.

    Community report · Steam · Forum reply ·
    “only started happening to me for the last 2 games :(”
    Community report · Steam · Forum reply · Open source
  2. Report

    Oct 24: it started on Friday for a player who had no problems during early access.

    Community report · Steam · Forum reply ·
    “Started happening to me on Friday. Played flawlessly during early access...”
    Community report · Steam · Forum reply · Open source
  3. Report

    Oct 24: another player says it has just started for them too.

    Community report · Steam · Forum reply ·
    “yeah just started for me aswell”
    Community report · Steam · Forum reply · Open source
  4. Report

    Oct 24: the game has to be fully restarted every time.

    Community report · Steam · Forum reply ·
    “Yeah, have to full restart the game every time...”
    Community report · Steam · Forum reply · Open source
  5. Report

    Oct 24: a player on the Xbox PC version gets the same error after every game and has to restart.

    Community report · Steam · Forum reply ·
    “same every single game its a restart. I am on Xbox PC version but same”
    Community report · Steam · Forum reply · Open source
Sources · 66 CommunityCommunity reportSteam · Forum thread+ 5 similar community reportsShow all →
Community reportSteam · Forum thread
“?!! what is this, very annoying, I have to restart it every single match.”
  • Community reportSteam · Forum replyOpen
    “only started happening to me for the last 2 games :(”
  • Community reportSteam · Forum replyOpen
    “Started happening to me on Friday. Played flawlessly during early access...”
Show all 6 sources