Last updated: 19 October 2026

Enshrouded Save File Location & Crash Fixes 1.0 Migration, Hotfixes & Known Issues

On Windows, Enshrouded stores your local saves at C:\Users\<you>\Saved Games\keen games\Enshrouded\default, and since 1.0 you can also keep them in Steam Cloud instead of (or alongside) that local folder. If you're crashing after the 1.0 update, the short version is: Keen Games already fixed several specific crash causes in Hotfix 1.0.0.1 and 1.0.0.2, your Early Access save should still load, and there is one known migration bug — corrupted pre-1.0 character saves get skipped rather than fixed — that Keen Games has acknowledged but not yet solved as of this writing.

01Enshrouded Save File Location (Windows)

The local save folder on PC is:

• C:\Users\WINDOWSUSER\Saved Games\keen games\Enshrouded\default — replace WINDOWSUSER with your actual Windows account name.

That's the path Keen Games documents in the official 1.0 changelog's "Save data" section. Since 1.0, the in-game menu also lets you choose between a local-folder save tab and a Steam Cloud save tab, so your world and character data can live in either place (or be checked in both, if you want to compare which one is current before loading).

02Back Up Your Saves Before You Do Anything Else

Before you update, reinstall, verify game files, or report a crash to support, copy your save folder somewhere safe. This is ordinary PC hygiene, not an Enshrouded-specific trick, but it's the single most useful thing you can do if a crash or a bad migration damages a save:

1. Close Enshrouded completely.
2. Open C:\Users\<you>\Saved Games\keen games\Enshrouded\default in File Explorer.
3. Copy the whole default folder to a second location (an external drive, a cloud folder, anywhere outside that path).
4. If you also use Steam Cloud saves, leave Steam Cloud syncing on — it's a second copy, not a replacement for a manual backup, since a cloud sync can push a corrupted save over a good one just as easily as a local overwrite can.

03What Happens to Your Save When You Update to 1.0

Keen Games built a new, more efficient save format for 1.0. If your existing save is from version 0.8 or earlier, the game automatically backs it up and migrates it to the new format the first time you load it after updating — you don't have to do anything manually, and the full 1.0 changelog's "Save data" section is explicit that this backup-then-migrate step happens automatically.

Keen Games' official Launch FAQ also confirms your Early Access save keeps working: "You can absolutely use Early Access saves once the game releases in 1.0... saves will be converted to a new, more efficient format." In the same post, though, Keen Games adds a recommendation worth taking seriously: "we have made many improvements to the world and first few hours of the game, so if you're up for it, we strongly encourage you to start over!" Carrying your save over works; starting fresh is Keen Games' own suggestion, not a requirement.

The same Launch FAQ also confirms you don't need to buy the game again: "You do not need to buy Enshrouded PC again if you own the Early Access version." That matters for this guide specifically, because it means there's no "fresh install, fresh purchase" step that would otherwise reset your save location — the Saved Games path above is the same one your Early Access install was already using.

One change that affects every carried-over character, new start or not: your skill tree was reset in 1.0. Keen Games' combat-changes post says it plainly — "with the new skills and changes to existing skill placement in the tree, your skill tree has been reset, hopefully for the last time." That's expected behavior after migration, not a sign your save is broken. For the skill tree itself, see the dedicated skill tree guide; for everything else that changed in the update, see what's new in 1.0.

04The One Confirmed Migration Bug: Corrupted Character Saves Get Skipped

Hotfix 1.0.0.2 (Oct 16, 2026) fixed a rare crash that happened specifically during save-game migration. As part of that fix, Keen Games changed how a corrupted pre-1.0 character save is handled: instead of attempting to migrate it (and risking the crash), the game now skips that character.

Keen Games' own hotfix notes say a future update will migrate and repair those skipped characters, and that if a character is missing from your list after updating, "help is on the way." As of Hotfix 1.0.0.2 — the latest patch covered by this guide — that repair has not shipped yet. If a character vanished after you updated:

• Don't delete anything. The skipped character's old data should still exist in your pre-migration backup (see the next section) and, per Keen Games, is expected to be recoverable once the repair fix lands.
• Check Keen Games' official channels (Steam news hub, linked below) for the fix before assuming the character is gone for good.
• If you need help now rather than waiting, use the official support form linked at the end of this guide.

05Hotfix 1.0.0.1 — What It Fixed, and Two Known Issues Left Open

Hotfix 1.0.0.1 shipped the same day as 1.0 (Oct 15, 2026). Per Keen Games' own changelog:

• Fixed several causes of random crashes.
• Fixed an indoor dynamic-lighting brightness bug.
• Fixed a "Fire Wisp" scroll exploit where its damage scaled with player level instead of being fixed at level 27.
• Updated the Deluxe Upgrade Pack's digital artbook and world map.
• Fixed crashes tied to specific peripherals.

Alongside those fixes, Keen Games documented two known issues in the same patch notes — one it says the hotfix itself caused, one it was simply still tracking:

• Reverb/sound misbehaving in large rooms when the master volume slider is below 100%. Keen Games' notes don't say this hotfix caused it, only that the team was still observing it at the time of writing. Documented workaround: leave the in-game master volume at 100% and adjust your actual volume through Windows' own sound settings instead.
• The world "Edit" button could stop working — this one Keen Games explicitly flagged as a regression that "cropped up with this hotfix." Documented workaround: subscribe to anything in Adventure Sharing first, then retry editing.

06Hotfix 1.0.0.2 — Fixes on Top of Fixes

Hotfix 1.0.0.2 landed the next day (Oct 16, 2026) and, per Keen Games' changelog, cleaned up both new issues and some that had been present since launch:

• Fixed the world-settings-configuration bug that 1.0.0.1 itself had introduced.
• Fixed the rare save-migration crash described above (with the skip-corrupted-characters tradeoff noted above).
• Fixed an Nvidia-specific dense grey-fog rendering bug, called out as especially noticeable in Hollow Halls.
• Fixed factory-placement crashes and menu bugs.
• Fixed localization bugs in several wand-related skill names.
• Fixed a fast-travel/glider crash that happened in entity-dense worlds.
• Fixed multiple Adventure-Sharing-related crashes, a water-simulation crash, a Twitch-link-server crash, a full-backpack crash, and an exit-game crash.

As of Hotfix 1.0.0.2 — the latest patch this guide covers — Keen Games had not yet reported the reverb-at-low-volume issue from 1.0.0.1 as resolved, so if you're still hearing it, the 100%-master-volume workaround above is still the documented fix.

07Before You Report a Crash

None of this is Enshrouded-specific — Keen Games hasn't published a list of error codes or crash-code meanings, so this is ordinary PC troubleshooting hygiene, worth doing before you file a support ticket:

1. Back up your save folder (see above) before you touch anything else — verifying files or reinstalling shouldn't touch your saves, but you want a copy regardless.
2. Confirm your patch version. Make sure you're actually on Hotfix 1.0.0.2 or later — in Steam, right-click Enshrouded > Properties > Installed Files > Verify integrity of game files will also re-download anything missing or corrupted.
3. Update your GPU drivers through NVIDIA, AMD, or Intel's own driver tool, especially if you're on Nvidia and seeing fog or lighting artifacts — 1.0.0.2 fixed one specific Nvidia rendering bug, but driver updates catch issues outside that fix too.
4. Note exactly when the crash happens (on launch, loading a specific world, during save migration, in a specific area) and whether it matches one of the known issues above — that's the detail official support will ask for first.

If none of that resolves it, or your issue isn't one of the ones Keen Games has documented, the official route is Keen Games' Zendesk support form, listed directly in the Hotfix 1.0.0.2 patch notes as the contact point for unresolved issues.

08Where to Check for the Next Hotfix

Enshrouded is still being patched actively right after launch, so an issue in this guide can be superseded quickly. Keen Games posts every changelog to its official Steam news hub first:

• Official Steam news hub: store.steampowered.com/news/app/1203620 — every patch note, including hotfixes, is posted here.
• Official support form: enshrouded.zendesk.com, for issues the patch notes don't already cover.

For the full list of what changed in the 1.0 update itself (new region, level cap, combat rework and more), see Enshrouded 1.0: What's New. If you're specifically troubleshooting crossplay or a PS5 question, that's covered separately in the crossplay & PS5 guide, since PS5 doesn't use this Windows save path at all and Keen Games hasn't published a PS5 save-file location in any source we checked.