Dawnwalker Update 1.1 Save Crash Fix: Mods & Load Errors
Cannot load a Dawnwalker save after Update 1.1? Use the safe PC recovery order for outdated PAK, executable and UE4SS mods, then identify unresolved vanilla crashes.
This page synthesizes the attributed sources below. It does not present another outlet's test as our own; unresolved player reports stay provisional.
If Dawnwalker crashes while loading a save after Update 1.1, do not delete the save or immediately downgrade the game. First preserve the save files, remove every pre-1.1 mod component—not just the visible mod folder—and verify the game files. A first-hand Steam Deck case recovered after removing an outdated executable and PAK replacement, and several PC reports recovered after cleaning mod files. Other current players report the same load failure with no active mods, so this is not a guaranteed universal fix and Rebel Wolves has not yet listed post-1.1 save loading as an official known issue.
Can't load a save after Update 1.1: direct answer
Update 1.1 officially fixes several save, loading and crash paths, but current Steam and Reddit reports describe a separate post-update failure where Continue or Load Game crashes before a campaign opens. The reports include different GPUs and error signatures, so there is not enough evidence to call every affected save corrupted.
The strongest reproducible cause is an outdated mod or modified game file left behind by an older installation. Clean that layer first. If a fully verified, never-modded install still fails on several saves, preserve the files and stop short of risky rollback or deletion while waiting for an official response.
| Observed state | Evidence status | Best next action |
|---|---|---|
| Save loads after all old mod files are removed | Repeated first-hand recovery | Keep a clean 1.1 baseline; update mods one at a time |
| Save still crashes after disabling the visible mod | Plausible leftover file | Check PAK, executable, loader and config replacements; then verify files |
| Never-modded install crashes on several saves | Repeated report, cause unconfirmed | Preserve saves and error text; report the clean reproduction |
| RX 9070 XT crashes when enabling Frame Generation | Official known issue | Leave Frame Generation Off |
| One save fails but an older manual save loads | Save-specific symptom | Keep both files and continue only from a copied backup |
Safe recovery order before touching your saves
Work from reversible steps to destructive ones. Copy the save folder or use the platform's supported backup method before changing game files. Do not test by overwriting the only recent manual save.
A normal reinstall may not remove third-party files that the storefront did not install. That is why a clean mod audit followed by Verify integrity is more useful than repeatedly reinstalling over the same folder.
- Close the game and Steam completely
- Back up the affected manual saves and keep the originals unchanged
- Move all third-party loaders, PAK files, executable replacements and injected DLLs outside the game directory
- Restore the original executable if a mod replaced or renamed it
- Use Steam Properties → Installed Files → Verify integrity of game files
- Launch Update 1.1 with no mods and Frame Generation Off for the first test
- Use Load Game and test a copied recent manual save, then one older manual or autosave
- Record the exact error and whether a new game reaches gameplay
Remove every kind of pre-1.1 mod
Dawnwalker mods do not all live in one folder. UE4SS loaders, PAK content, executable replacements and INI edits use different paths. Deleting only a Mods folder can leave the component that actually crashes during save loading.
One documented Steam Deck recovery removed an outdated replacement executable and a performance-mod PAK, then verified the installation. Treat those filenames as specific to that mod, not a universal deletion list. If you are unsure which files were added, compare against the mod author's installation instructions and let the storefront restore official files.
| Mod type | What may remain | Clean test |
|---|---|---|
| UE4SS or injected loader | Proxy DLL and ue4ss folder beside Dawnwalker.exe | Move both outside the game folder and verify |
| PAK or Logic Mods | Added .pak files under Content\Paks or a mod subfolder | Move only third-party files, then verify |
| Executable replacement | Renamed original plus a modified Dawnwalker.exe | Restore the original or delete the replacement and verify |
| INI/config tweak | Changed renderer, FrameGen or engine values | Back up, then restore the clean generated configuration |
| Steam Deck performance package | Executable and PAK changes may be combined | Follow that package's removal steps before verification |
What current reports do and do not prove
A Steam thread active on October 27 reports a Bad name index serialization error and multiple saves failing after 1.1. Separate Reddit threads include modded systems that recovered after a clean removal and players who say verification or reinstalling did not help. This establishes a real troubleshooting cluster, not one confirmed root cause.
Rebel Wolves' official Update 1.1 known-issues section currently names only the RX 9070 XT Frame Generation toggle crash. It does not acknowledge a general save-conversion failure, publish a hotfix ETA or instruct players to downgrade. Keep all non-official recovery claims labelled as player-verified or provisional.
| Claim | Current status | Why |
|---|---|---|
| Update 1.1 can expose incompatible mod files | Player-verified | Multiple clean-removal recoveries |
| Every failing save is corrupted | Not established | Different errors and recoveries are reported |
| Reinstalling always fixes it | Not established | Some clean reinstalls still fail |
| Deleting the newest save fixes it | Unsafe and unverified | Can destroy the best recovery copy |
| A hotfix is confirmed | No | No official announcement checked on October 27 |
If a clean vanilla install still crashes
Keep the clean configuration and test whether a new campaign reaches gameplay. Then test Load Game rather than Continue, starting with a copied older manual save. If every existing save fails but a new game works, report the exact game version, storefront, hardware, error text and whether the installation was ever modded.
Do not keep cycling through BIOS, drivers, Proton versions and save deletion at the same time. The official BIOS guidance applies to the separate Oodle or DecompressShader compilation crash on affected Intel systems; the RX 9070 XT warning applies specifically to switching Frame Generation from Off to On.
- Confirm Update 1.1 and a successful file verification
- Leave Frame Generation Off during diagnosis
- Test a new campaign without overwriting existing slots
- Test copied manual saves from newest to older
- Capture the full crash message and timestamp
- State whether any mod, loader or executable replacement was ever installed
- Submit the clean reproduction through the official support route
Why downgrading is the last resort
Community posts describe downloading an older Steam depot, but Rebel Wolves has not published that as a supported recovery. A version rollback can introduce mismatched files, lose 1.1 fixes and create new compatibility uncertainty if a save was written by the newer build.
Preserve the saves before considering any rollback and do not publish the older-version test back over the only current save. Waiting for an official hotfix is safer when the clean 1.1 installation still fails and no earlier manual save opens.
| Action | Risk | Recommendation |
|---|---|---|
| Delete the save or cloud copy | Permanent data loss | Do not use as diagnosis |
| Copy saves before testing | Low | Do this first |
| Steam depot downgrade | Version and save mismatch | Unsupported last resort only |
| Wait on a preserved clean reproduction | Lost play time, but protects evidence | Safest when vanilla 1.1 still fails |
Install mods again only after a clean load
Do not reinstall a loader merely because its pre-1.1 version worked before the patch. Wait for the author to name Update 1.1 or the current build explicitly, then add one component and test the same copied save.
Keep the working vanilla state as the baseline. If the crash returns after one mod, remove that exact component and retain its log rather than adding more changes.
- Confirm the save opens on clean Update 1.1
- Use only a mod release that explicitly supports 1.1
- Add one mod at a time
- Close the game between tests
- Keep an unmodified manual save and game-file baseline
Compatibility warning before installing any mod
Mods are community software, not an official Rebel Wolves feature. Update 1.1 invalidated at least some older executable, PAK and loader modifications. A package that worked on Hotfix 1.0.5 is not automatically compatible with 1.1.
Use a mod only when its current page explicitly names Update 1.1 or the matching current build and recent users confirm the same platform. Windows, Steam Deck/Proton, GOG and Xbox PC can require different files.
| Check | Safe requirement | Do not assume |
|---|---|---|
| Game version | The mod explicitly supports Update 1.1 | A 1.0.5 loader still works |
| Platform | The author names your storefront and operating system | Windows and Proton use the same package |
| Loader location | Follow the current package instructions beside the real executable | Every mod belongs in one Mods folder |
| Save safety | Keep an untouched pre-mod manual save | Removing files reverses every saved change |
Install UE4SS in the correct folder
Use UE4SS only when the individual mod lists it as a requirement. Download the complete Dawnwalker-compatible package from its maintained page and read its file notes before extracting; upstream UE4SS documentation explains the loader structure, but the game-specific package supplies the settings and signatures tested against Dawnwalker.
For a standard Steam installation, open the game folder from Steam, then continue into Dawnwalker\Binaries\Win64. The correct directory contains Dawnwalker.exe. Close the game before changing files.
| Step | Action | Verification |
|---|---|---|
| 1 | Back up the save you will test and copy any existing dwmapi.dll plus the entire ue4ss folder outside the game directory | The backup is separate from Win64 |
| 2 | Remove the old loader files; do not merge two UE4SS packages | No old ue4ss folder remains in Win64 |
| 3 | Extract the complete compatible archive beside Dawnwalker.exe | dwmapi.dll and the supplied ue4ss folder sit next to the executable |
| 4 | Launch through Steam with only the package's supplied helpers | The main menu loads and a fresh UE4SS.log is created |
| 5 | Close the game, add one required mod, then test again | A failure can be tied to the last change |
Do not mix INI, PAK and UE4SS instructions
Dawnwalker mods use different installation methods. An INI tweak edits configuration, a packaged content mod replaces or adds game content, and a UE4SS mod runs through a loader. Follow the file author's current instructions for that exact download instead of dropping every archive into the UE4SS Mods folder.
Install one variant when a mod offers mutually exclusive timer, segment or balance versions. Combining alternatives that edit the same value can create an ambiguous result even when the game does not crash.
| Mod family | Typical clue | Safe rule |
|---|---|---|
| INI/config | Archive contains an .ini file or replacement values | Back up the original and recheck it after every game update |
| Packaged content | Author names a PAK or Logic Mods location | Use only the path on that mod's current page |
| UE4SS/Lua | UE4SS is listed as a requirement | Verify the loader build first, then add the mod alone |
| Save file | Download replaces or adds campaign saves | Keep it separate from your own saves and scan the archive before use |
Fix a crash, stutter or missing mod after installation
Start from the verified vanilla Update 1.1 baseline. Add only the current loader if a mod requires it, launch once, then add one mod and retest. This makes the last changed component identifiable.
If a failure returns, remove the last component and preserve its log. Do not diagnose a save-load crash by stacking a loader update, GPU driver change and several new PAK files in the same test.
| Symptom | First safe check | Next action |
|---|---|---|
| Game fails before the menu | Remove the loader and all added files | Verify the base game before retrying |
| Save crashes only with one mod | Remove that mod and retest the same copied save | Wait for an explicit 1.1-compatible release |
| Mod does not appear | Read its current loader and install-method notes | Check a fresh log from the current launch |
| Stutter began after adding mods | Restore the clean 1.1 baseline | Return one component at a time |
| Clean game also crashes | Keep the clean state and exact error | Use the shader guide only for matching Oodle or DecompressShader errors |
Clean rollback to the unmodded game
Close the game and move the proxy DLL plus the complete ue4ss folder out of Win64. Restore only files from the backup made before installation. Then verify game files through the storefront if the unmodded launch still fails.
Do not overwrite the only post-mod save while diagnosing. Some gameplay mods can write changed inventory, timing or progression values into a save, so removing the files does not guarantee that every saved change reverses.
- Keep a pre-mod manual save
- Remove loader and mod files while the game is closed
- Restore the original configuration backup
- Verify storefront files only after preserving edited files for comparison
- Retest with the unmodified save first
Which popular mods are safe to recommend?
No community mod is universally safe to recommend across every build. Popular timer, torch, inventory and UI changes demonstrate real demand, but popularity does not establish patch compatibility, save safety or achievement behavior.
Choose a mod only when its page names the current game build or has recent confirmations for that build. Read requirements, recent posts and known bugs before downloading. Avoid stacking several mods that change time, progression or the same loot tables on the first test.
Frequently asked questions
Where do you install UE4SS for The Blood of Dawnwalker?
Install the compatible Dawnwalker package beside the actual Dawnwalker.exe in Dawnwalker\Binaries\Win64. Do not use Engine\Binaries\Win64.
Which UE4SS version works with Update 1.1?
Use only a Dawnwalker-specific package whose current author notes explicitly name Update 1.1 or the matching build. A package documented for Hotfix 1.0.5 is not proof of 1.1 compatibility.
Why did Dawnwalker start crashing after installing mods?
Remove added mods and test the matching UE4SS package with only its supplied helpers. If that works, restore one mod at a time and inspect UE4SS.log after each launch.
Do Dawnwalker mods disable achievements?
There is no universal confirmed answer. Different mods use different methods, so rely only on the current statement and reports for the exact mod you install.
How do you uninstall Dawnwalker mods?
Close the game, move added mod files, dwmapi.dll and the ue4ss folder out of Win64, restore backed-up configuration files and verify storefront files if the vanilla game still fails.
Official sources establish releases and documented features. Independent walkthroughs corroborate routes; community posts only show reported behavior. The article above combines these sources into an original answer, table or decision route and marks uncertainty where the evidence does not agree.
- Rebel Wolves — official Update 1.1 fixes and known-issue boundary ↗
- Steam Discussions — active Update 1.1 save-load serialization report ↗
- Dawnwalker community — mod-removal recovery after Update 1.1 ↗
- Dawnwalker community — mixed load-failure reports after Update 1.1 ↗
- Nexus Mods — maintained Dawnwalker UE4SS package and build-specific instructions ↗
- UE4SS project — upstream installation and verification documentation ↗
- Steam — official Hotfix 1.0.5 release note ↗
- CurseForge — active Dawnwalker mod catalogue ↗
- Space4Games — independent mod types and post-update behavior cross-check ↗