Troubleshooting · Save lock

Saving is currently locked

How to Fix “Saving Is Currently Locked” in The Blood of Dawnwalker

Hotfix 1.0.4 fixed one problem that blocked saving, but not every cause. Update first; if Manual Save and Quicksave are still locked during normal exploration, protect your last valid save and use the diagnosis below.

Quick answer

Saving is currently locked

Update to Hotfix 1.0.4 or later first. If “Saving is currently locked” remains after you leave combat, dialogue or another scripted state, stop risking new progress, check your last valid save and continue with the diagnosis below.

No universal fix exists for every case. The steps below narrow down which case you have.

Hotfix 1.0.4 status

Hotfix 1.0.4 changed the situation

Released 2026年9月9日. The patch fixed one issue that blocked players from saving.

Still locked on 1.0.4+? · Continue diagnosis

Current status

Official patch fix
Yes — one save-blocking issue fixed in 1.0.4
Every save-lock case fixed?
Not established
Universal cause
No single cause established
What to do first
Update → check last save → leave temporary states → retest

Hotfix 1.0.4 fixed one issue that could block saving. The patch notes do not state that every “Saving is currently locked” case has the same cause or is now resolved.

Read the official patch notes

On this page

Before Anything: Protect Your Progress

Don't keep playing for another hour assuming Autosave will recover your progress.

Before Trying Anything: Check Your Last Valid Save

Open Load Game and check:

  • Latest save type
  • Latest in-game day
  • Whether recent progress is present

A locked Manual Save or Quicksave does not guarantee that Autosave is still recording your progress.

Understand Autosave →

Diagnose My Save Lock

Answer in order. Each step narrows down which kind of save-lock case you have.

Step 1

Are you updated?

Are you updated?

Step 2

What exactly happens when you try to save?

What exactly happens when you try to save?

Step 3

First Check Whether the Lock Is Temporary

Saving may be unavailable while the game is handling combat, dialogue, cutscenes or scripted transitions. Finish the current state, return to normal exploration, then test both Manual Save and Quicksave again.

Are you currently…

If both remain locked during normal exploration, continue below.

Step 4

When did saving stop?

When did saving stop?

Step 5

Check your last valid save

Open Load Game before you reload or keep exploring.

Do you know when your last valid save was?

How save slots work →

Your diagnosis

Answer the steps above and this panel turns into the next action for your exact case.

What to Try, in Safe Order

  1. 1

    Check your current game version

    Update to Hotfix 1.0.4 or later.

  2. 2

    Open Load Game

    Confirm your latest valid save before risking more progress.

  3. 3

    Finish the current scripted state

    Leave combat, dialogue, a cutscene or a quest transition.

  4. 4

    Test both save methods

    Try Manual Save and Quicksave separately.

  5. 5

    Return to normal exploration

    If saving works again, the lock was temporary.

  6. 6

    If it began after Ambrus, check the reported progression pattern

    Treat this as diagnosis, not a universal fix.

  7. 7

    If the lock persists on the current patch, preserve your last valid save

    Do not overwrite older milestone saves while troubleshooting.

Reloading may discard everything after your latest valid save. Check its in-game day first. Do not reload as the first step.

Community-reported pattern

Still Locked After Defeating Ambrus?

If your problem did not begin after Ambrus, skip this section.

Some players have reported persistent save locking after the Ambrus encounter. A community-reported explanation links some cases to a pending Infamy-related event.

This is useful for diagnosis, but it has not been established as the cause of every save-lock case.

Possible related state: Infamy. This page does not explain the Infamy system.

Community reports on Steam

Community workaround

Community Workaround Reported for Some Post-Ambrus Cases

Hotfix 1.0.4 officially fixed one issue that blocked saving. Update before trying older community workarounds.

One player reported that triggering the pending Infamy event restored saving.

Deliberately changing Infamy can affect your playthrough, so do not use this as the first troubleshooting step.

Attacking a guard is not a first-line fix. It is a community-reported way to trigger a particular Infamy state and can change your playthrough.

Still Locked on Hotfix 1.0.4 or Later?

If Manual Save and Quicksave remain unavailable during normal exploration on the current version, do not assume an older community workaround applies. Protect your last valid save, note exactly where the lock began, and compare it with the relevant quest or progression state.

Issue Status Timeline

  1. 2026年9月3日

    Players report persistent save locking, including post-Ambrus cases

  2. 2026年9月4日

    Hotfix 1.0.2 does not specifically list the issue

  3. 2026年9月9日

    Hotfix 1.0.4 fixes one issue that blocked saving

  4. Current

    Persistent cases should be diagnosed separately; no claim that every cause is resolved

Read the official patch notes

Save Lock Questions

Why does Dawnwalker say “Saving is currently locked”?
The game is currently blocking a save. That can be a temporary state such as combat, dialogue or a scripted transition, or a persistent issue. Update first, then use the diagnosis above.
Was saving fixed in Hotfix 1.0.4?
Yes — one issue. The official patch notes list a fixed issue that blocked players from saving the game.
Does Hotfix 1.0.4 fix every save lock?
Not established. The patch notes fix one blocking issue without claiming that every “Saving is currently locked” case shares that cause.
Why can’t I quicksave?
Finish any temporary state, return to normal exploration and retest Quicksave and Manual Save separately. If both stay locked, continue with the diagnosis.
Does this happen after Ambrus?
Some community reports describe persistent save locking after the Ambrus encounter. That is a reported pattern, not a confirmed universal cause.
Is Infamy the cause?
A pending Infamy-related event is a possible community-reported pattern for some post-Ambrus cases. It is not established as the cause of every save lock.
Should I attack a guard?
Do not treat that as a universal fix. It is a community-reported method for triggering a particular Infamy state and can alter your playthrough.
Will Autosave protect my progress?
Do not assume that it will. Check the Load Game screen and confirm your most recent valid save before continuing.
Should I reload?
Only after checking how much progress your latest valid save contains, because reloading may discard unsaved progression.

Check your save lock

Continue diagnosis