The Last Caretaker / GAME HISTORY
The Last Caretaker Backup Menu Lock: Wait Before Opening Save Again
Dorastrix reported locking the slot menu by opening Backup again before the first save finished. Waiting is the reported avoidance step. Another player suggested a Steam-overlay workaround; neither account establishes a final official repair version.
Short answer
Dorastrix reported locking the slot menu by opening Backup again before the first save finished. Waiting is the reported avoidance step. Another player suggested a Steam-overlay workaround; neither account establishes a final official repair version.
Scope: PC Steam reports, March–August 2026. Exact build and underlying code cause were not verified.

The second menu opened during the first save
The March report describes the Backup/Close prompt becoming available before saving finished. Opening Backup then left a slot window that stopped responding when the first operation ended.
The player could move somewhat but could not access menus, including Escape. That is a specific interface state, not evidence every backup station or file is broken.
The reported trigger order
Avoid repeating this sequence merely to test the only copy of a valuable run.
- Choose Backup at a station.
- Choose a slot and confirm saving or overwriting.
- Before it finishes, choose Backup again.
- Let the first save finish while the second slot window remains open.
The July replies offered different actions
Xanman64 advised doing nothing after pressing Save until it completed. YunggGravy reported opening the Steam overlay with Shift+Tab, closing it quickly and finishing the save interaction.
The overlay method is one player’s account, not an official recovery guarantee. It concerns an already trapped menu; the other advice avoids opening it a second time.
Forced exit has a narrower evidential basis
Dorastrix used Alt+F4 and said the situation occurred just after saving. That does not prove every background write has finished whenever a similar lock appears. Preserve existing backups before replacing files.
An August reply discussed the issue again. Continued reports alone do not show every later build remained unpatched. No race-condition diagnosis or final official fix version was verified.
Join the conversation
Have a question, correction or a different take? Share it below. Comments appear immediately after submission.
Reader comments
Loading comments…