Unofficial player utility / checked 28 Sep 2026

Graveyard Keeper 2 Known Issues and Patch Status

Check Graveyard Keeper 2 known issues by symptom, platform, and version. Keeper Ledger maps official 1.005 and 1.006 changelog entries, then keeps recent player reports in a separate evidence lane. A community report is never presented as a confirmed cause or fix.

  • Current tracked build: 1.006
  • Official records: 13
  • Community signals: 5 categories
25,636players online at capture
5,146all-language reviews at capture
400,000copies claimed by the publisher
1.006latest official patch reviewed

Working tool

Check Graveyard Keeper 2 known issues by symptom

Select the closest problem, platform, and game version. The result uses only the records shown on this page. It will not edit saves, recommend mods, or convert a player complaint into an official fix.

Nothing is uploaded. Your selection stays in this browser.

Versioned evidence

Graveyard Keeper 2 issue status board

“Fixed” means the developer included the item in a published changelog. It does not guarantee the same symptom has the same cause in every save. “Community report only” means recent Steam reviews describe the symptom, but the reviewed patch notes do not confirm its cause or resolution.

Official changelogFixed in 1.006

Ultrawide or non-standard resolution crash

Update 1.006 says intermittent crashes on ultrawide and non-standard resolutions were fixed.

Verified action: update to 1.006, then report a reproducible recurrence with the in-game Steam PC reporter.

Official changelogFixed in 1.006

Keeper wedged between workstations

The 1.006 notes cover the kitchen chest and firewood gap plus cases where a zombie pushed the Keeper between workstations, chests, or extensions.

Verified action: update to 1.006. The notes do not publish a recovery step for saves still affected.

Official changelogFixed in 1.006

Kitchen zombie consumes ingredients without output

Kitchen zombies should no longer consume or burn ingredients without producing the selected dish.

Verified action: update to 1.006 before reproducing. No compensation policy is stated.

Official changelogFixed in 1.006

Defender's Emblems can block squad unlocks

Players can no longer destroy Defender's Emblems and soft-lock zombie squad unlocks, according to update 1.006.

Verified action: install 1.006. The changelog does not say how an already soft-locked save is repaired.

Official changelogFixed in 1.006

Crop bed permanently stuck before harvest

Patch 1.006 fixed crop beds that could become impossible to inspect, harvest, or remove just before harvest.

Verified action: update to 1.006. Recheck the existing bed before dismantling anything.

Official changelogFixed in 1.006

Extra bag slots ignored for pickups or purchases

Extra bag slots now work for pickups and vendor purchases when the main backpack is full.

Verified action: update to 1.006 and retest with space in an extra bag.

Official changelogFixed in 1.006

Static-price goods double on first purchase

Static-price trade goods should now retain their fixed price instead of doubling on the first buy.

Verified action: update to 1.006; capture the vendor and item name if the mismatch remains.

Official changelogFixed in 1.005

Study Table locks after adding an item

Update 1.005 fixed the Study Table becoming unusable after an item was inserted for Science.

Verified action: use 1.005 or later. If it recurs in 1.006, file a new report rather than assuming the old cause.

Official changelogFixed in 1.005

Crematorium stuck with a corpse

The 1.005 changelog says the Crematorium should no longer lock with a corpse on the table and become unusable.

Verified action: update to at least 1.005. No official manual reset is listed.

Official changelogFixed in 1.005

Zombies cannot be resurrected despite requirements

Update 1.005 fixed cases where resurrection failed even after quest and item requirements were met.

Verified action: update to 1.005 or later and confirm the zombie limit before reporting a recurrence.

Official changelogFixed in 1.005

Resurrection Table preparation resets

The prepared body and strap state should no longer reset after leaving and re-entering the morgue.

Verified action: update to 1.005 or later and record whether the reset affects the body, strap, or both if it returns.

Official changelogImproved in 1.005

Heavy FPS drops at the alchemy tower

The 1.005 notes state that performance at the top of the alchemy tower was improved.

Verified action: compare on 1.005 or later and report hardware, resolution, and exact location if the drop persists.

Official changelogErrors cleared in 1.005

Errors before first sleep or save

Update 1.005 says a batch of errors before the first sleep and save was cleared. The note does not promise manual saving or recovery of a missing save.

Verified action: update before starting again; do not interpret this entry as proof that every save-loss report is resolved.

Community report onlyUnconfirmed after 1.006

Crash while entering or leaving an area

Recent English Steam reviews describe crashes when entering a house or leaving the morgue. The reviewed 1.006 notes confirm a different resolution-related crash fix, not this transition cause.

Safe next step: record the area transition, build number, resolution, and lost play time; submit through the in-game reporter.

Community report onlyNeeds official confirmation

Battle door, flag, or green-fog progression block

Multiple recent reviews describe a locked door to a flag, spawning inside green fog, or a battle that cannot be completed. The 1.006 Defender's Emblem fix is not evidence that these reports share the same cause.

Safe next step: use the in-game reporter with the battle name, objective, platform, and save state. No verified workaround is published here.

Community report onlySystem design plus reports

Progress lost after a crash

Reviews repeatedly connect crash recovery with the sleep-based save flow and report losing recent progress. The official 1.005 note about pre-save errors does not establish a universal recovery method.

Safe next step: verify that a sleep completed before exiting. Keeper Ledger does not recommend editing or replacing save files without an official procedure.

Community report onlyNeeds reproduction

Bioreactor or factory appears not to work

Recent reviews say the bioreactor and factory flow are poorly explained, with one player unable to tell whether the bioreactor was broken. The 1.006 kitchen-zombie fix does not cover this report.

Safe next step: capture the machine, recipe, inputs, connected belts, assigned zombies, and version before reporting. No recipe data is invented here.

Community report onlyBroad symptom, cause unknown

General hitching, lag, or periodic slowdown

Thirteen of the sampled 100 recent English negative reviews mentioned performance, lag, slowdown, hitching, or stutter. This count is a demand signal, not a diagnosis.

Safe next step: report hardware, platform, resolution, area, zombie count, and whether the issue persists after 1.006.

Sample boundary: the community lane summarizes the latest 100 English negative Steam reviews returned on 28 September 2026. It over-represents dissatisfied players and is not a prevalence estimate. Terms overlapped: 36 mentioned save or progress, 24 bug/broken/soft-lock language, 13 performance symptoms, and 11 stuck or wedged states.

How to read the ledger

Fixed record, new recurrence, or unconfirmed report?

Official fixed record

The symptom appears in a versioned developer changelog. Install that build first, but treat a recurrence as new evidence instead of assuming the old cause.

Community-only signal

Players repeatedly describe a problem, but the reviewed official notes do not confirm its cause, affected platforms, or recovery steps.

Unlisted problem

No exact match is still useful: record the version, platform, location, trigger, and expected result, then use the in-game Steam PC bug report function added in 1.006.

Primary sources

Where the Graveyard Keeper 2 status comes from

Patch facts come from developer announcements. Player pain points come from a separately labeled Steam review sample. Point-in-time player and review counts can change after this page is published.

  1. Update 1.006 is live - official fixes for crashes, stuck states, crops, progression, inventory, trading, UI, and zombie work.
  2. Update 1.005 is live - official station, resurrection, performance, save-error, movement, and balance changes.
  3. 400,000 copies announcement - publisher-reported sales milestone, treated as a vendor claim.
  4. Graveyard Keeper 2 on Steam - release date, platforms, reviews, and store information.
  5. Recent English negative review feed - community demand evidence only, never an official issue list.

Boundaries

Frequently checked issue questions

Does “fixed in 1.006” guarantee my save is repaired?

No. It means the developer listed a fix in that changelog. Some notes prevent a trigger but do not describe recovery for a save that was already affected. Report a recurrence with the current build and exact save state.

Why are recent Steam reviews not labeled known issues?

A review can establish that a player experienced a symptom and that demand exists for clearer status information. It cannot establish the root cause, affected population, or official fix state. Those records stay in the community-only lane.

Where is the bug report option?

Update 1.006 says an in-game bug report function was added to the Steam PC build. The announcement does not say that the same function is available on every console, so this page does not claim it is.

Why does the checker avoid save edits and unofficial mods?

They may create a different failure or make a report harder to reproduce. This first version limits itself to published changelogs, safe evidence collection, and an official reporting route.

Is Keeper Ledger a full Graveyard Keeper 2 guide or wiki?

No. Recipe databases, quest walkthroughs, factory layouts, and tier lists require hands-on, versioned verification. Existing guide sites already compete for those broad searches. Keeper Ledger stays focused on patch status and issue triage.