Why can't I save in Blood of Dawnwalker after the update?

Hotfix 1.0.4 fixes one issue that blocked players from saving, but saving can still be temporarily unavailable during particular story or combat states. Check the active mission and exact on-screen message before treating the save as damaged.

How do I fix “Saving is currently locked” in Dawnwalker?

First preserve the current details: platform, patch version, active quest, in-game day and last autosave. A Steam discussion reports that progressing an overdue Infamy event restored saving for some players, but it is not an official universal fix and may not match your run.

Should I keep playing when Dawnwalker will not save?

No. Avoid committing a long unsaved session or overwriting a good earlier save. If a normal story transition does not restore saving, stop and report the reproducible state rather than layering mods, configuration edits or unrelated fixes.

SAVE-LOCK TROUBLESHOOTING · COMMUNITY REPORTS, NOT AN OFFICIAL FIX

Blood of Dawnwalker can't save: what “Saving is currently locked” can mean

If The Blood of Dawnwalker will not quicksave or manual save, first identify whether saving is temporarily locked during a mission or whether a progression event has failed to trigger. Protect the current run before testing anything.

Last checked: September 10, 2026 · Facts and sources are updated when they change.

DO NOT OVERWRITE YOUR ONLY RUN

Update to Hotfix 1.0.4, then retest before changing anything. The official update fixes one issue that blocked players from saving, but a remaining “Saving is currently locked” message can still be a mission state or another reproducible bug.

First: tell a temporary save lock from a persistent bug

Temporary lockSome games disable saving during an active sequence, combat or a transition. Wait for the sequence to finish and check for the exact in-game notice.

Persistent lockIf the same message remains after a normal transition, note the active quest, location, in-game day and last autosave before taking another action.

One official fix, not a universal claimHotfix 1.0.4 lists a fix for an issue that blocked players from saving. It does not say that every locked-save report shares that cause.

Do not guess from the label“Can't save,” a missing autosave and a story consequence that cannot be reversed are different problems.

What should you do when Dawnwalker says saving is locked?

Capture the state: screenshot the message and write down platform, game version, active quest, location, in-game day and the time of the last autosave.
Finish or leave the current safe transition: if you are visibly in a combat, cutscene or scripted mission step, let it resolve before checking the save menu again.
Check for a pending progression event: one Steam discussion links a stuck save lock to an overdue Infamy cutscene. If your run has a pending Infamy threshold, test the normal in-game event that triggers it; do not assume this applies to another quest or platform.
Verify the result immediately: make one manual save or quicksave as soon as the option returns, then confirm it appears in Load Game before continuing.
Stop if it persists: do not spend hours hoping for an autosave. Keep the evidence and report the exact state for a patch or support investigation.

What not to do with a save-lock bug

Do not install a mod, edit an .ini file, delete local save data or overwrite the last usable slot while diagnosing a locked save. Those changes can turn a reproducible game-state report into a lost run. If you also have a crash or display problem, use the dedicated crash and stutter guide or flickering guide; neither is a save-lock remedy.

What to include in a useful bug report

Include the exact save-lock text, platform and storefront, patch version, current quest, in-game day, Infamy state if visible, last successful save type, and a short video of the normal transition that did not restore saving. This is more useful than “can't save” alone, and it lets other players tell a mission lock from the same reproducible bug.