Baldur's Gate 3 Mod Manager Not Loading Profile

When the Baldur’s Gate 3 Mod Manager profile freezes on loading, a broken modsettings.lsx file or old manager version usually causes the problem.

Quick context: You sit down to launch a modded run, open the tool, and the progress bar just hangs on “Loading profiles.” No error pop-up, no clue what went wrong, and your whole load order feels locked away. This guide walks through clear, safe steps that many players use to get back in game without wiping everything by accident.

Goal of this guide: Help you fix the stuck profile screen, keep as much of your load order as possible, and prevent the same Baldur’s Gate 3 Mod Manager not loading profile bug from returning after the next big patch.

Baldur’s Gate 3 Mod Manager Not Loading Profile Fix Overview

Start with the basics: The tool reads profile data from a few key files under your Baldur’s Gate 3 folders. When one of those files corrupts during a patch or a mod install, the manager stalls on the loading step and never reaches the main window. That is why so many fixes revolve around deleting or rebuilding a single file called modsettings.lsx.

Most players who report the stuck profile screen share the same pattern: the game updated to a new patch, the manager still pointed at old data, and the load order file no longer matched the current build. The manager keeps trying to parse that file, loops on “Loading profiles,” and never exposes your profile dropdown.

To fix this, you will work in three layers:

Quick checks — Make sure the manager points at the right game folder and profile.
File repairs — Reset or rebuild the modsettings.lsx file that drives the profile list.
Clean reinstall steps — Refresh the manager and mod files when the bug keeps coming back.

What The Stuck Profile Bug Looks And Feels Like

Spot the common symptoms: Before changing anything, match what you see with the usual behavior players report when the profile fails to load. This helps you avoid chasing the wrong issue, such as a general game launch problem instead of a profile-only one.

Endless “Loading profiles” bar — The progress bar gets about halfway and never finishes.
Blank profile dropdown — The profile field at the top left is empty or greyed out.
Missing “Public” profile — You only see a blank entry, or no playable profile at all.
Manager runs, game will not — Mods appear in the list, but the game launch button does nothing or fails silently.

These issues usually trace back to three roots: a corrupt profile file, a wrong game path in settings, or a mismatch between installed mods and the current patch of Baldur’s Gate 3. The next sections walk through easy checks before you remove anything.

Quick Checks Before You Change Files

Easy checks first: These steps take a minute each and often fix the Baldur’s Gate 3 Mod Manager not loading profile issue without touching the game folders.

Restart everything — Close the manager, Steam or GOG, and the game launcher, then restart your PC and open the manager again.
Run as administrator — Right-click the manager shortcut and choose Run as administrator so it can read and write profile files freely.
Check the game path — Open the manager settings and confirm the game directory points at your live Baldur’s Gate 3 install, not an old folder or moved drive.
Start the game once without mods — Launch BG3 directly from Steam or GOG, reach the main menu, then close it and reopen the manager. Starting the game refreshes some internal files that the manager reads.
Update the manager build — Compare your version with the latest release on the GitHub page or the site where you downloaded it. Install the new build if yours is behind.

Quick check: If the profile still sticks after these steps, the modsettings.lsx file is the next place to work. Many reports from Patch 7 onward point straight at that file as the trigger for infinite loading.

Step-By-Step Fixes For A Stuck Profile Screen

Work carefully: The steps in this section touch game data under your user profile. Read each item fully before you act, and keep a backup of anything you delete so you can roll back if needed.

Delete A Corrupt modsettings.lsx File

Main fix: Many players fix the profile hang by deleting the current modsettings.lsx file and letting the game rebuild it. This removes your current load order but frees the manager from the loop.

Close BG3 and the manager — Make sure both the game and the mod tool are fully closed in Task Manager.
Open the profile folder — In Windows Explorer, paste this path in the address bar:
%LocalAppData%\Larian Studios\Baldur's Gate 3\PlayerProfiles\Public
Back up modsettings.lsx — Right-click modsettings.lsx, choose Copy, and paste it somewhere safe such as your desktop.
Delete the original file — Remove modsettings.lsx from the Public folder.
Start BG3 once — Launch the game normally, reach the main menu, then close it so BG3 writes a clean profile file.
Reopen the manager — Start the tool and check whether the profile now loads and the dropdown shows your Public profile again.

Deeper fix: If the manager still locks up, repeat the same process but also clear any extra player profiles you do not use, leaving only Public. Keep the backups somewhere safe until you confirm that the bug is gone.

Reinstall The Mod Manager Cleanly

When to do this: If you updated through several builds or swapped between tools such as Vortex and the standalone manager, some leftover files can confuse profile loading. A clean reinstall resets that layer.

Export your load order if possible — If the manager sometimes opens, use its “Save” or “Export” function to keep a copy of your mod list.
Uninstall the manager — Remove it through Apps & Features or by deleting the folder where you extracted it.
Delete leftover config folders — Remove any old manager folders under your user AppData or the folder where you unpacked it.
Download the latest build — Grab the current version from the official project page or trusted source.
Install and set the game path — Point the new install at your Baldur’s Gate 3 directory and restart it once.

After this reset, try loading the manager again. If the profile now appears, you can rebuild your load order by dragging mods back in or by re-importing your saved order file.

Repair Game Files And Remove Conflicting Tools

Check the game side: Broken game files or an extra loader such as an old script extender can keep the manager from reading the new patch layout correctly.

Verify game files in Steam or GOG — Use the built-in “verify integrity” option to repair damaged files.
Remove old DWrite.dll hooks — If you see a DWrite.dll in the Bin folder or a “Native Mod Loader” folder, move or delete it and test the manager again.
Turn off alternate mod tools — Close Vortex or any other mod tool while you test the standalone manager so they are not both trying to control the same files.

Once the game files are clean and only one tool manages mods, the profile screen often starts working again, since the manager no longer collides with old loaders or half-applied patches.

Cleaning Up Mod Files And Load Order

Why cleanups matter: Even if modsettings.lsx rebuilds without errors, a tangled mod folder can pull the manager back into a bad state later. Spending a few minutes tidying your mod structure now saves time when the next patch lands.

Sort mods by source — Group files from Nexus, Steam Workshop (if used), and direct downloads into clearly named subfolders outside the game directory.
Remove duplicate versions — Keep only the newest build of each mod in your active mods folder.
Check mod pages for patch notes — Many authors post updated instructions after each major BG3 patch; match your settings with those notes.
Watch for script extender requirements — If a mod needs BG3 Script Extender, follow the author’s steps so the manager sees it correctly.

Load order tuning: After the manager opens again, take a moment to rebuild a clean load order before you start a long new run. Put core libraries and framework mods near the top, content and gear mods in the middle, and small tweaks or visual mods near the bottom. Keep a backup of this order in a text file or inside the manager’s own export feature.

Fix	What It Targets	When To Try It
Delete modsettings.lsx	Corrupt profile and stuck loading bar	Profile never loads after a new patch
Clean reinstall manager	Old config files and mixed tools	Manager updated through many builds
Verify game files	Damaged BG3 install or loaders	Game or manager misbehaves in other ways

Keeping The Mod Manager Stable After New Patches

Stay ahead of the bug: Big content patches tend to change how mod data is stored. That is why the same loading profile issue spiked around Patch 7 and later updates, then eased off as players cleaned and rebuilt their profiles.

Wait for updates before modding a new patch — When BG3 patches, let the manager and your most complex mods update before you enable them again.
Keep a “clean” backup profile — After you reach the main menu on a new patch with no mods, back up that fresh modsettings.lsx under a name such as modsettings_clean_patch7.lsx.
Change only a few mods at once — Add or remove a small batch, test the game, then move on. That way, if the manager hangs again, you roughly know which change triggered it.
Store your load order outside the manager — Keep a simple text file that lists your mods in order. If you ever need to delete modsettings.lsx again, you can rebuild quickly.

Last check: Once everything works, open the manager, confirm your profile appears, launch the game through it, and load a save. If you can enter a zone, use a few modded features, and exit to the main menu without errors, you are in a stable state again.

When The Bug Keeps Coming Back

Time to step back: If the Baldur’s Gate 3 Mod Manager not loading profile problem returns every time you change mods, you may be dealing with a specific mod or tool that does not play well with the current patch.

Test with zero mods — Move every mod out of the active folder, delete modsettings.lsx, let BG3 rebuild it, and see whether the manager loads a plain profile.
Add only must-have mods — Bring back a small core set, one group at a time, testing the manager after each group.
Watch bug reports for your manager version — Check the GitHub issues page or main guide sites to see whether others hit the same pattern with a specific build.

Practical rule: If a certain mod or bundle always leads back to the loading profile loop, keep it disabled until the author ships an update that calls out Baldur’s Gate 3 patch compatibility in the description.