Baldur’s Gate Game Load Error 117 | Save Fix Steps

What Baldur’s Gate Game Load Error 117 Means

When you hit a load screen in Baldur’s Gate 3 and see error 117, the game cannot build the story data linked to that save. The launcher often pairs this code with text such as We couldn’t create a story that worked or warnings about damaged add ons.

This message usually appears when you load a save that depends on scripts, mods, or data that no longer match the current build. It can show up after a hotfix, a large patch, or a change in your mod list. In some cases it points to a corrupt save file.

Players face this problem both on modded setups and clean installs, though reports lean strongly toward mod heavy profiles. Steam threads and help pages link error 117 with story scripts that fail to run or saves that come from a different version of the game.

Baldur’s Gate 3 Load Error 117 Causes And Triggers

To clear baldur’s gate game load error 117 in a stable way, you need to know what usually sits behind it. Several common patterns show up often across Steam forums, Larian notes, and guide sites.

• Broken or missing mods — A mod update, removal, or install order change can break the story scripts linked to your save, which blocks the load process.
• Old saves with a new patch — A large patch or hotfix can change internal data. Saves made on an older build may fail when the new build expects different story files.
• Leftover mod data in folders — Even after you disable mods in a manager, mod files can linger in AppData or the Documents\\Larian Studios\\Baldur's Gate 3 folder and still affect loads.
• Cloud and local saves out of sync — If Steam Cloud or GOG Galaxy holds a different version of a save than your local files, the game can trip over mixed data.
• Corrupted save file — Sudden crashes, forced shutdowns, or storage issues can leave a single save broken while older ones still work.

Cause	Typical Symptom	Fast Test
Missing or broken mods	Error 117 on modded saves only	Turn off mods and try a new save
Patch and save mismatch	Error 117 after a hotfix or large update	Load older saves from the same run
Leftover mod data	Error 117 even on a clean profile	Clear Mods folders in AppData and Documents
Corrupted save file	Only one or two saves fail	Test the same profile on older saves

Most official advice from Larian for broken saves starts with clearing mods and cache folders and then testing clean profiles with new saves.

Quick Checks Before You Tackle Error 117 Loads

Run through these quick checks first; they often restore loads and reveal whether one save or your whole setup is broken.

• Restart the game and launcher — Close Baldur’s Gate 3 and its launcher, end any stray bg3.exe tasks, then start fresh.
• Reboot the PC or console — A clean boot clears stuck processes that can lock save files or story data.
• Test a new game — Start a new campaign and save once. If that loads fine, the core install works and the issue likely sits with a specific profile or mod list.
• Try an older save — Load a save from earlier in the same run. If older saves load while the newest one fails, the latest file may be damaged.
• Check cloud sync — Temporarily turn off Steam Cloud or GOG sync for Baldur’s Gate 3, then test with local saves only.

If every save fails, even new ones, you are dealing with a wider setup issue. That kind of pattern usually points toward mods, stray data in folders, or a damaged install.

Step-By-Step Fixes For Error 117 Load Problems

Work through the fixes in this section in order and test your saves after each block.

Clean Up Mods And Test A Vanilla Profile

1. Disable every mod in your manager — In BG3 Mod Manager, Vortex, or your tool of choice, turn off all mods for the profile that throws error 117.
2. Switch the game to a new profile — In the launcher, create a fresh profile with no linked mods, then start a new save.
3. Load the fresh save — Quit to menu and reload that new save. If it works, the base game can create a working story with no mods.
4. Test an old save without mods — With mods still off, try loading one of the saves that showed error 117. If it now works, your issue came from a mod conflict or load order.

Remove Leftover Mod Files From Game Folders

1. Reveal hidden folders in your file manager — Turn on the option that shows hidden items so you can reach the AppData path.
2. Open the local Larian folder — Go to AppData\\Local\\Larian Studios\\Baldur's Gate 3 and look for a Mods folder or script extender files.
3. Delete or move the Mods folder — Move the folder to a backup location or delete it to clear stray mod data.
4. Check the Documents folder — Open Documents\\Larian Studios\\Baldur's Gate 3 and remove any leftover mod files there as well.
5. Start the game again — Launch Baldur’s Gate 3 so it can rebuild fresh config and mod lists, then try your saves.

Larian advice for broken saves often includes this folder cleanup step, since the game can read mod data from both the local and documents paths even when a manager reports that no mods are active.

Verify Game Files Through Your Platform

1. Open your game library — On Steam, right click Baldur’s Gate 3 and open the Properties panel.
2. Run a file integrity check — Use the option to verify or repair the install so the client scans for missing or damaged files.
3. Repeat on other launchers if needed — On GOG or other platforms, run their repair or verify tool on the game.
4. Retest problem saves — Once the scan completes, launch the game and try to load the saves that gave error 117.

This process replaces broken core files but leaves your save data and mods in place. If the error came from a bad patch download, loads may start working as soon as the client fixes those files.

Handle Incompatible Or Old Saves

Large patches can change the way story data works. In those cases, saves from a much older patch may no longer load on the latest build, even when you clean mods and repair files.

• Try saves from different dates — Work backward through your save list and see where loads start to succeed again.
• Check patch notes and hotfix posts — Larian often flags builds that break older saves or require new campaigns.
• Start a new run on the current build — If only new campaigns work, your older run may not be recoverable on this version.

Use A Mod Fixer Or Clean Load Order

Many players clear error 117 by installing a small mod fixer package or by rebuilding their load order from scratch. Both routes try to give the game a clean script list so story creation works again.

• Install a trusted mod fixer — On Nexus Mods, search for a BG3 Mod Fixer that you trust, follow the setup guide, and then test your problem saves.
• Rebuild your mod list slowly — Add mods back one at a time, testing loads in between, so you can spot the exact plugin that breaks your saves.
• Watch script extender versions — Make sure your script extender matches the current game build, since mismatched hooks can block story loading.

If a single mod or small cluster of mods triggers error 117 every time, drop those entries from your load order for this run and keep them for later campaigns only.

Mod Management Tips To Avoid Repeat Error 117

Once you get back into your save, a few habits can reduce the chance that baldur’s gate game load error 117 returns on the next patch or mod swap. None of these steps take long, yet they save hours of progress over the life of a campaign.

• Keep a plain vanilla profile — Maintain at least one profile with no mods that you use to test new patches and hotfixes.
• Snapshot your load order — Before large changes, export or screenshot your mod list so you can rebuild it if a manager profile breaks.
• Avoid heavy mod changes mid run — Try not to remove, add, or reorder large mods in the middle of a campaign, especially ones that touch story or classes.
• Store manual backups of core saves — Copy your most valued saves to a safe folder with date labels, so you can roll back if the main set breaks.
• Watch patch notes before loading — After a patch, skim the notes and check whether Larian mentions save changes or mod impact, then decide which run to risk first.

Careful mod and save habits help keep long campaigns safe, especially on platforms with frequent hotfixes and active mod scenes.

When To Back Up, Restore, Or Contact Larian

In a few edge cases, error 117 does not clear even after full mod removal, folder cleanup, file repair, and new campaigns on the same system. That pattern points to damaged save files, storage trouble, or a rare bug that sits beyond normal player fixes.

• Back up your saves before more tests — Copy the entire Baldur’s Gate 3 save folder to an external drive so you have a safety net.
• Test on another device if possible — Move a problem save to a second PC with a clean install and see whether it loads there.
• Scan your drive for errors — Use system tools to check the disk that holds the game and saves, since file system issues can corrupt data.
• Gather logs and crash dumps — Larian help tools can bundle saves, logs, and crash data into a report zip.
• Send a ticket to Larian help desk — Attach the report zip, a description of your steps so far, and links to specific saves that show error 117.

With that information, their help staff can review your saves and advise whether recovery is possible or whether you need to start a fresh run on the current build. Take notes on each step so you can report them easily later. That protects progress.