Quick answer
If your existing save hangs forever while loading or the game freezes when you sleep, do not delete the save or overwrite your only copy with a new game. Check your platform and installed patch first:
PC: 1.008 (October 2) fixed an infinite loading issue tied to a conveyor exception; 1.009 (October 6) fixed another crash while loading a save.
PlayStation / Xbox: official 1.009.1 (October 9) contains fixes for freezing and says that certain already-stuck saves are repaired on load.
Nintendo Switch / Switch 2: do not assume those PC and PlayStation fixes have arrived. Players were still reporting old saves that could not load on October 11–12, and no universal recovery procedure is confirmed for every affected Switch save.
On PC, back up your related .dat and .info files before changing anything. On consoles, preserve the available local/cloud save before trying risky recovery steps.
These reports describe several different bugs
Players say “save broken” to mean different things:
- 1
Continue is missing:
the game may not be finding the slot.
- 2
Continue exists but loading never ends:
a slot is found, but the scene fails to open.
- 3
Sleeping freezes:
new progress may not be written.
- 4
The game crashes shortly after loading:
a runtime/session issue rather than necessarily a missing save file.
- 5
A quest is stuck in a loaded game:
story state is broken while the world still opens.
Treating all five as “reinstall the game” is not useful. Reinstallation does not automatically repair a damaged game-state record.
Check your exact patch first
Graveyard Keeper 2 received several distinct rounds of post-launch fixes.
PC 1.007
Included saving-performance improvements and some quest/workstation softlock corrections.
PC 1.008 — October 2
The official notes specifically list a fix for infinite loading caused by a conveyor-related exception. They also mention a sleep-related crash that could leave the Keeper out of bounds.
PC 1.009 — October 6
A separate crash while loading a save was fixed. The same release addressed freezes when replacing an invalid previous zombie worker and several gardener-related issues.
PlayStation / Xbox 1.009.1 — October 9
Official notes describe fixes for freezing during sleep, assigning workers, some calendar transitions and several other conditions. They also state that already-stuck saves are repaired on load for the relevant affected cases.
That note belongs to this console update, not automatically to Nintendo Switch.
Why the Switch situation is different
Patches have different release schedules across platforms. tinyBuild's support pages distinguish problems already fixed on some systems from issues still awaiting delivery on Switch and Switch 2.
Reddit users on October 11–12 were still describing Nintendo saves that never finished loading even while new games could start. That is serious evidence of a remaining platform-specific problem, but not proof that every affected save is permanently lost.
Do not start over solely because a commenter said that was their only option.
What is safe to do first?
Step 1: record what happens
Write down:
platform and device;
installed game version;
whether a new game opens;
whether the existing slot reaches gameplay;
whether the freeze happens immediately, during sleep or on entering a location;
whether you just changed the Factory, conveyors or zombie assignments.
That helps distinguish a known fixed issue from one still being investigated.
Step 2: protect your save
On Windows, copy the full folder:
%USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2
A slot includes related .dat and .info files; copying the whole folder is safer than separating them.
On consoles, inspect the platform's official backup or cloud-save features first without choosing anything that deletes or overwrites the only existing version.
Step 3: update the game
Confirm the installed build, not just whether the launcher says “no update available.” PC and console numbers and release dates can differ.
If the patch notes explicitly name your symptom and that patch is available on your platform, loading again after installing it is the logical first test.
Step 4: fully restart the session
Close the game, restart the device if needed and try the save again. This may clear a temporary session problem, but it is not a guaranteed fix for the file itself.
Step 5: compare with another existing slot
If another save loads normally, the problem may be localized to one slot. Do not make a new test save by overwriting the only copy of your important progression.
What if the game freezes while sleeping?
Sleeping is the normal way to save in GK2. A freeze here is more concerning than a temporary graphics glitch: the latest game state might never have been written.
Look for a pattern:
does it happen after a specific Factory modification?
did you just assign a zombie worker?
is a quest cutscene about to trigger?
does midnight or a new weekday cause the failure?
The 1.008/1.009 PC fixes and 1.009.1 console release address multiple such cases. That does not guarantee the Switch issue is gone.
Official changelogs contain fixes for repeating exception popups, gardener zombies, caretakers and invalid workstation states.
But the word exception alone is not a diagnosis. Record the first complete error message and the interaction immediately before it appeared.
Do not demolish every workstation, disable cloud backup or delete directories just because a message mentions a conveyor.
Can a corrupted PC save be repaired?
Sometimes a newer patch or an older backup can restore progress. Community PC patches also repair certain specific broken states.
However, there is no verified universal method that restores every corrupted GK2 save. Not every infinite loading screen is caused by the same error.
Before testing mods, moving files or changing game versions, preserve the original save separately.
For the directory and backup procedure, see Save File Location and Backups.
What not to do
Do not delete cloud data assuming Steam or your console will reconstruct a better copy.
Do not make reinstalling the only plan: it does not guarantee a save-state repair.
Do not edit .dat with a normal text editor.
Do not stack untested mods onto your only working backup.
Do not say “Switch is fixed because PC is on 1.009.” The platforms do not share a simultaneous patch schedule.
If an irreplaceable save is still inaccessible, protecting it for an official future fix can be wiser than risking the only copy.
How to file a useful bug report
Include:
- 1
exact platform (PC, PS5, Xbox, Switch, Switch 2);
- 2
- 3
where the failure occurs (Continue, sleep, combat, area loading);
- 4
whether it happens every time;
- 5
the action immediately before the first failure;
- 6
whether a previous backup exists.
Steam PC has an in-game bug-report path. Other users should use tinyBuild's official support workflow for their platform.
FAQ
Does PC 1.009 fix every infinite loading screen?
No. It fixes named causes; different failures can remain.
A new game works on Switch 2. Is my old save deleted?
Not necessarily. It means the game can start, but that particular slot cannot load successfully. The cause needs more evidence.
Do I still need backups after patches?
Yes. Backups are especially valuable during frequent early updates.
Will reinstalling fix the save?
Not reliably. Some player reports say reinstalling did not help their inaccessible older slot.
Should I restart from zero immediately?
Not if you want to preserve the old progression. Check the official status and backup options first.
