On this page
First: Protect Your Progress
Don't continue for another hour assuming Autosave will recover your progress.
Manual Save and Quicksave being locked does not guarantee that a fresh Autosave is being created.
Save Lock Diagnosis
Answer in order. This is a decision tree, not a probability score.
First: Is the Save Lock Temporary?
Check whether the game is still in a scripted state. These are checks, not confirmed Dawnwalker lock rules.
Check Your Last Save
Open Load Game before you reload or keep exploring.
- Latest save type
- Latest in-game day
- Approximate progress represented
Community-reported pattern
Save Lock After Ambrus
Not yet treated as a universal rule
Several players have reported losing access to Manual Save and Quicksave after the Ambrus encounter. One repeated community explanation is that Infamy crosses a progression threshold while a related event or cutscene is still pending.
This does not yet prove that every “Saving is currently locked” case has the same cause.
Possible related progression state: Infamy. This page does not explain the Infamy system.
What to Try, in Safe Order
- 1
Stop progressing
Don't continue for another hour assuming Autosave will recover your progress.
- 2
Check Load Game
Note the latest save type, in-game day, and whether recent progress is represented.
- 3
Finish the current scripted state
If you are still in combat, dialogue, a cutscene, or a quest transition, leave that state and test saving again. This is a check, not a verified lock table.
- 4
Test Manual Save and Quicksave
If either works, the lock has cleared. If both stay locked, continue.
- 5
Check the known progression pattern
Only if this started after Ambrus or an Infamy change: a pending Infamy-related event is a community-reported pattern, not a confirmed cause.
- 6
Check that the game is updated
Hotfix 1.0.2 notes do not list this save-lock issue. An update is not a confirmed fix.
- 7
Preserve the last valid save
Avoid overwriting older manual milestone saves while diagnosing.
Reloading may discard everything after your latest valid save. Check its in-game day first. Do not reload as the first step.
Community workaround
Community Workarounds
Some players report that triggering the pending Infamy-related event caused saving to become available again.
Do not intentionally change your Infamy state unless you're comfortable with the gameplay consequences. This is not a verified universal fix.
Issue Status
Sep 3, 2026
Multiple community reports
Sep 4, 2026
Not listed in Hotfix 1.0.2 notes
Sep 7, 2026
No universal cause confirmed
Still Locked?
Treat the case as unresolved. Keep the last valid save, and use the save-system page for ordinary save types.
What to Save Now
This site cannot save the game for you. If saving is available again, make a Manual Save before you continue.
FAQ
- Why does Dawnwalker say “Saving is currently locked”?
- The message indicates that the game is currently preventing a save. Multiple players have reported longer-than-expected lock states, but no single universal cause is confirmed yet.
- Is it caused by Infamy?
- There is a community-reported pattern linking some post-Ambrus cases to an Infamy-related event that had not yet triggered, but this should not be treated as the explanation for every save lock.
- Should I attack a guard to fix it?
- Do not treat that as a universal fix. It is a community-reported method for triggering a particular Infamy-related state and can alter your playthrough.
- Will the game still autosave while saving is locked?
- Do not assume that it will. Check the Load Game screen and confirm your most recent valid save before continuing.
- Was this fixed in Hotfix 1.0.2?
- The published Hotfix 1.0.2 notes do not list this save-lock issue among its fixes or known issues.
- Should I reload?
- Only after checking how much progress your latest valid save contains, because reloading may discard unsaved progression.