BG3 Mod Manager Troubleshooting: Every Common Error & Fix (2026)

The fastest way to route a BG3MM symptom to the correct fix is to ask which stage of the workflow has failed. Users can walk this short decision tree in under thirty seconds and arrive at the matching spoke article. The branches are mutually exclusive in most cases: a symptom that fits one branch usually rules out the others.

• The application will not run at all. Either the EXE is double-clicked and nothing visible happens, or a dialog mentions “.NET 8 Desktop Runtime”. This is a runtime-or-permissions problem. See the spoke on launching failures or the dedicated .NET 8 article below.
• The application opens but stays on “Loading Profiles” forever. A specific Patch 7 regression around campaign discovery is the typical cause. Skip to the “Loading Profiles” section.
• The application opens but the mod list is empty. Detection is broken: a misconfigured Game Data Path, an invalid Mods folder, or files placed in the wrong directory. The “Mods or .pak Files Not Detected” section covers each cause.
• Mods are listed but a yellow or red dependency warning appears. The load order references mods that are not installed or not active. The “Missing Mod Dependencies” section maps the warning to its source.
• Dragging a .pak into BG3MM produces “Mod Was Not Imported”. The file is corrupted, archived, or lacks valid metadata. The dedicated import-error section describes the three sub-causes.
• BG3MM works but the in-game launcher does nothing. The Game Executable Path is unset, or Steam interception is blocking the launch. See the “Can’t Launch the Game” section.
• BG3 launches but crashes during character creation or load. Almost always a Patch 8 mod-binary mismatch. Skip to the Patch 8 crash section.
• Load order changes silently between sessions. Either a “Reset Externally” dialog appears, or the user notices that order has changed without warning. Two distinct failure modes; both are explained in the consolidated “Load Order Reset” section.
• Override-style mods stopped working after Patch 7. Patch 7 changed how Larian loads override .pak files. The Patch 7 override section covers the workaround.

Issues that resist this triage are usually misdiagnoses of one of the nine branches above. When in doubt, the LaughingLeader/BG3ModManager GitHub issue tracker (linked under each section) holds the canonical reproduction reports.

Symptom: BG3 Mod Manager opens, displays the splash, and reaches the “Loading Profiles” step in the status bar. The progress never advances; the campaign dropdown stays empty; closing and reopening reproduces the same state. The hang is most often reported on Patch 7 and on first-run installs that were upgraded across versions.

Root cause: The profiles directory under %LOCALAPPDATA%\Larian Studios\Baldur's Gate 3\PlayerProfiles contains a malformed profile.lsb or a stale modsettings.lsx from a previous Patch 7 boot. BG3MM’s profile parser will block on the malformed XML rather than skipping it, which presents as an indefinite “Loading Profiles” wait. GitHub issue #355 captures the path-config edge case that triggers this in OneDrive-redirected Documents folders.

Fix: Close BG3MM, back up the PlayerProfiles folder, launch Baldur’s Gate 3 once to regenerate a clean profile, then reopen BG3MM. If the hang persists, delete modsettings.lsx inside the active profile so the game writes a fresh copy on next boot. Read the full guide on the Loading Profiles hang.

Symptom: A user drags a .pak file (or several) from a download folder into the BG3 Mod Manager window. A dialog appears with the message “Mod Was Not Imported” and the file count of failed imports. The mods do not appear in the Inactive list.

Root cause: The dropped file is one of three things: a still-archived bundle (.zip, .rar, .7z) rather than a loose .pak; a .pak that lacks a valid meta.lsx inside (often the case with override-only mods or partially built test packages); or a corrupted file from an interrupted download.

Fix: Extract any archive to expose the inner .pak before dropping. For mods that ship without meta.lsx (typically Patch 7 override-style packages), place the .pak directly into %LOCALAPPDATA%\Larian Studios\Baldur's Gate 3\Mods and skip BG3MM’s import flow entirely. For corrupted files, redownload from the original source. Read the full guide on the Mod Was Not Imported error.

Two distinct failure modes both show up as “the load order changed without permission”. They share a symptom but have different root causes and different fixes, so distinguishing them matters.

Sub-case A: “Load Order Has Been Reset Externally” dialog. A modal dialog appears on launch saying that BG3MM detected an external change to the active load order. This means another tool, the in-game manager, or the user opened modsettings.lsx outside BG3MM, and the on-disk file no longer matches BG3MM’s last known state. The dialog offers to keep BG3MM’s order or accept the on-disk version. The fix is to choose deliberately and disable Larian’s in-game manager when working from BG3MM, since the two write to the same file. GitHub issue #353 documents how Patch 7 added the in-game manager that overwrites modsettings.lsx silently. Read the full guide on the Reset Externally dialog.

Sub-case B: modsettings.lsx keeps resetting at file level. No dialog appears, but the on-disk modsettings.lsx reverts to a default or pre-mod state every time the game launches. The active mod list is wiped from inside BG3 itself. Root cause is Patch 7 launcher behavior plus interaction with the in-game manager, OneDrive sync rewriting the file mid-launch, or an antivirus tool restoring a previous version. The fix involves marking modsettings.lsx as read-only after exporting from BG3MM, disabling Larian’s in-game manager, and excluding the Larian profile path from antivirus monitoring. Read the full guide on modsettings.lsx resets.

The video below shows the standard BG3 Mod Manager workflow end-to-end: opening the application, configuring the Game Data Path, refreshing the mod list, building a load order, and exporting it to the game. Most troubleshooting symptoms become obvious once the working workflow is visible side by side with the broken state.