Baldur’s Gate 3 Failed To Load Main Menu | Quick Fixes

What The Baldur’s Gate 3 Failed To Load Main Menu Error Means

The baldur’s gate 3 failed to load main menu message usually pops up before you even see your saves, which makes the whole game feel locked away. The launcher runs, the splash screens play, then a warning appears or the loading spinner hangs forever.

This problem shows up in a few slightly different ways. Some players see a warning about the current game mod. Others sit on a black screen with a spinner after pressing any button. On Steam Deck or console the game may crash straight back to the dashboard.

Next, it helps to know what is going wrong behind the scenes. Baldur’s Gate 3 loads profile data, mods, graphics settings, and cache files before it shows the main menu. When any of those files are corrupted, mismatched with the current patch, or blocked by a third party program, the game stalls on the menu step instead of finishing the startup process.

That sounds scary, but in most cases your saves are still fine. The fix usually involves clearing configuration folders, repairing game files, or disabling mods so the game can build a fresh profile and reach the menu again.

Why Baldur’s Gate 3 Menu Load Errors Happen

Most reports from Larian help pages, player guides, and forum threads point to the same root causes. Once you match your own setup to one of these patterns, you can jump to the most likely fix instead of trying random tweaks that waste time.

• Corrupt player profile — The PlayerProfiles or profile.lsx files can break during a crash, power cut, or patch, which stops the game at the menu stage.
• Leftover or broken mods — Old mod files or a damaged modsettings.lsx file often trigger a failed to load message even when you think all mods are gone.
• Mismatched game version — Steam, GOG, or console builds that only updated partly can leave you with out of date resources that no longer match your current patch.
• Overlays and background tools — Tools such as GPU overlays, recording software, RGB controllers, and chat overlays sometimes hook into the game at startup and cause crashes or infinite loading.
• Damaged install files — Missing or corrupted game files after a bad download or storage issue can prevent the menu map and assets from loading.

On PC, the strongest link is between mods and the baldur’s gate 3 failed to load main menu error. Guides and forum posts often confirm that deleting or repairing modsettings.lsx and clearing the right profile folders clears the warning and brings back the title screen.​

Quick Checks Before You Start Deleting Files

Quick check: Before you dig through folders, run through a short round of simple checks that sometimes clear the error on their own and save you a deeper cleanup run.

• Restart the PC or console — A fresh reboot clears leftover processes and lets Baldur’s Gate 3 start in a clean state.
• Disable overlays — Turn off Discord overlay, GeForce Experience overlay, Steam FPS counters, and similar tools, then try to launch again.
• Unplug extra controllers — Remove spare gamepads and USB devices that might confuse input detection during startup.
• Check for pending updates — Make sure the game, launcher, and graphics drivers are fully patched before you chase deeper fixes.
• Try a different startup path — On Steam, launch directly from the library instead of a shortcut, or skip the Larian launcher if that option is available.

If the main menu still refuses to appear after these quick steps, it is time for targeted fixes based on your platform and whether you use mods.

Core Fixes For PC Players Using Mods

Most PC players who run into the error use mods from Nexus Mods, mod.io, or similar sites. Patch changes sometimes break those files, and even a single outdated tweak can block the menu. The steps below line up closely with player fixes and guides from sites that track this bug.​

1. Back up saves and profiles — Copy your save folder and the entire Larian Studios directory in your Documents and AppData folders to a safe place so you can restore progress if something goes wrong.
2. Clear mod manager deployment — In Vortex, BG3 Mod Manager, or your chosen tool, disable all mods and run any clean or purge option so loose files leave the game directory.
3. Delete modsettings.lsx — In many cases this single file is the culprit. Delete modsettings.lsx in both the global Baldur’s Gate 3 folder and the PlayerProfiles\\Public folder so the game can rebuild it from scratch.​
4. Remove leftover Mods folders — Open the Larian Studios directory under AppData and Documents and delete any Mods folders that still hold files from past setups.
5. Verify game files — Use Steam or GOG Galaxy to run a file verification pass so the launcher replaces missing or damaged assets linked to the menu.

Player posts and guides report that deleting the correct modsettings.lsx file is often enough to stop the failed to load message and bring back a clean main menu. Steam threads also point out that there are two similar folders, so you need to remove the file from both the global and PlayerProfiles paths for a full reset.​

Steps To Rebuild A Corrupt Player Profile

If your game never used mods, or the previous sequence did not help, the next suspect is a broken profile. Larian help pages and fix guides often describe a full profile reset as the reliable next move.​

1. Close the game and launcher — Make sure Baldur’s Gate 3 and its launcher are fully closed in Task Manager.
2. Open the Larian Studios folder — On Windows this usually lives under %AppData%\\Local\\Larian Studios\\Baldur's Gate 3.
3. Delete the PlayerProfiles folder — Remove the entire PlayerProfiles folder so the game cannot reuse damaged profile data at startup. Your saves live in a different folder and stay intact.
4. Start the game — Launch Baldur’s Gate 3 again so it can build a fresh default profile and reach the menu.

Many recent guides confirm that a corrupt profile is the leading cause of this menu error since full release, and that deleting PlayerProfiles clears the bad data and allows the game to start clean.​

Fixes For Players Without Mods Or On Console

Plenty of players hit a failed to load main menu message even when they never touched a mod manager. On console you do not have a Mods folder at all, yet the game can still stall on the first loading screen.

In those cases the problem usually sits in broken game files, graphics settings that push too hard during the opening scene, or background tools that fight with the game at startup. Larian’s own crash troubleshooting page points to these areas when Baldur’s Gate 3 fails before the main menu.​

On Xbox and PlayStation, cache files can also get stuck after an update. A full power cycle helps in many cases: shut the console down, wait a minute, unplug it, then plug it back in and start Baldur’s Gate 3 from your game library again.

• Lower graphics settings — On PC, drop settings such as texture quality and anti aliasing in your GPU software, then start the game again.
• Turn off third party overlays — Disable hardware monitoring, RGB tools, recorders, and chat overlays before launch, then re enable them one by one later.
• Repair or reinstall the game — On Steam or GOG, run a file verification first. On console, use the built in repair or reinstall option if the menu still refuses to load.
• Free storage space — Make sure the drive that holds the game and your system drive both have comfortable free space so the game can write cache files.
• Check for system updates — Install any pending OS and driver updates tied to graphics, storage, or platform firmware.

On Steam Deck, recent patches included layout and performance updates that change how the game loads on that hardware. If your deck started showing menu errors after a hotfix, double check that you completed any required migration steps and that you are on the intended build, not an older Proton layer.

Handy Reference Table For Folder Paths

When you troubleshoot the failed to load main menu problem on PC, you spend a lot of time jumping between folders. This quick table helps you confirm that you are working with the right paths for the usual fixes.

How To Prevent The Error From Coming Back

Once your menu finally loads again, the last thing you want is a repeat the next time a big patch lands. A few simple habits will keep your setup cleaner and make it less likely that this menu warning returns.

• Update mods in step with patches — When a new hotfix lands, wait for your core mods to update and read the change notes before you launch a save that relies on them.
• Keep a backup of clean profiles — After you reach the main menu with a setup that feels stable, copy the entire Larian Studios folder to another drive as a fallback.
• Avoid manual edits in modsettings.lsx — Let your mod manager handle that file so you do not introduce stray tags or broken links.
• Limit concurrent overlays — Pick one monitoring or overlay tool during play instead of stacking several at once.
• Watch storage health — Run periodic checks on the drive that holds the game so slow or failing sectors do not corrupt large files.

If you play on both PC and Steam Deck, pick one platform as your main home for campaigns. Fewer cross platform saves means fewer chances for conflicts that can break profile data later.

If you run into fresh menu errors even with clean profiles and no mods, gather your crash logs and send them through Larian’s help form. Include your platform, a short description of the steps you tried, and your system specs. That extra detail saves back and forth messages and gives the team a better chance to spot a pattern tied to your hardware or a new patch.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback