The error message “Sorry, something went wrong” that appears when launching LEGO Batman: Legacy of the Dark Knight on PC is almost never a server issue. It is a local conflict — a permissions failure, a corrupted cache, an overlay injection, or a driver mismatch. The launcher itself (Steam or Epic Games Store) is the gatekeeper, and this error signals that the gatekeeper cannot verify or initialize the game executable. The fixes are systematic, not random, and understanding why each step works saves time.
Reinitializing the Launcher Stack
The most common cause is a residual process from a previous session. Restart the PC completely — not a shutdown-and-restart from the menu, but a full power cycle. Many launcher background services (Steam Client Service, Epic Games Launcher Helper) do not terminate cleanly, and a cold boot resets the entire authentication pipeline. After restart, launch Steam or Epic Games as administrator. Right-click the shortcut, select Run as administrator. The launcher requires write access to %ProgramData% and user-specific appdata directories for DRM tokens; without elevated permissions, the token retrieval may fail silently and produce the generic error.
Beyond Cache: Verifying File Integrity
If a restart does not clear the error, the next layer is file integrity. The “Sorry, something went wrong” error often masks a missing or corrupted game asset — typically a DLL used by the Unity engine’s asset bundle loader. On Steam, navigate to Library > right-click LEGO Batman: Legacy of the Dark Knight > Properties > Installed Files > Verify integrity of game files. On Epic Games, go to Library, click the three dots under the game, select Manage, then Verify. This scan compares every file against the manifest and redownloads only the damaged ones. A full verification takes 2–5 minutes; do not interrupt it.
Overlay Conflicts as a Common Culprit
Overlay software from Discord, NVIDIA GeForce Experience, MSI Afterburner/RivaTuner, Xbox Game Bar, and even the Steam overlay itself inject a hook into the game process before the main executable is fully loaded. When the hook conflicts with Unity’s initialization sequence — especially the splash screen or the DRM handshake — the launcher returns the error. Disable all overlays globally before launching the game. For Steam, uncheck Enable the Steam Overlay while in-game in the game’s Properties. For Discord, turn off In-game Overlay in User Settings. For NVIDIA, open GeForce Experience, go to Settings and toggle In-Game Overlay off. For MSI Afterburner, close the application entirely; RivaTuner Statistics Server does not need to be uninstalled, but it must not be running. Restart the PC after disabling all overlays to ensure no residual hooks remain in memory.
Cache Corruption at the Launcher Level
The launcher itself stores temporary files — update manifests, login tokens, cached thumbnails — that can become stale or corrupt. Clear the launcher cache independently of the game cache. For Steam, close it completely (check Task Manager for any steam.exe or steamwebhelper.exe processes). Press Windows+R, type steam://flushconfig, press Enter, and confirm the prompt. This wipes Steam’s local cache without affecting game installations. For Epic Games, press Windows+R, type %localappdata%, locate the Epic Games Launcher folder, and delete the Saved subfolder. Restart the launcher; it will regenerate these files. Corrupted cache is one of the most underdiagnosed causes because the error message does not distinguish between game file issues and launcher state issues.
DNS and Network Layer Adjustments
A less obvious trigger is the launcher’s inability to reach authentication servers due to outdated or misconfigured DNS. LEGO Batman: Legacy of the Dark Knight uses an online entitlement check even for single-player mode. If the DNS resolution fails or returns a cached bad IP, the launcher times out and presents the error. Change the DNS to Google Public DNS: open Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Right-click your active connection (Wi-Fi or Ethernet), select Properties, then double-click Internet Protocol Version 4 (TCP/IPv4). Select Use the following DNS server addresses, set Preferred DNS to 8.8.8.8 and Alternate DNS to 8.8.4.4. Click OK, then restart the PC. This bypasses ISP-level DNS filters and reduces latency to Steam/Epic authentication endpoints. For users on strict corporate or school networks, also consider adding the launcher executable to the Windows Firewall exception list: open Windows Security > Firewall & network protection > Allow an app through firewall > Change settings > Allow another app, then browse to steam.exe (or EpicGamesLauncher.exe) and to the game’s .exe (typically LEGOBatman.exe in the install folder).
When the Environment Itself Intervenes
Background applications that inject into every process — such as MSI Afterburner, RivaTuner Statistics Server, OBS Studio with game capture, Wallpaper Engine, ReShade, and RGB lighting software (Corsair iCUE, Razer Synapse, Logitech G Hub) — can all interfere with Unity’s startup. These tools are not inherently malicious, but they hook into DirectX or the Windows graphics pipeline to provide overlays, performance metrics, or custom shaders. When they load before the game completes its initialization, they can cause the “Sorry, something went wrong” error. Close all non-essential background applications using Task Manager before launching the game. A clean boot (msconfig > selective startup) can isolate the conflict, but for most users, manually exiting suspicious software is sufficient. Pay special attention to any software that uses a global keyboard hook or a notification tray icon.
The Last Resort: Clean Reinstallation
If all of the above fails — and only after trying every step in sequence — reinstall both the launcher and the game. Do not simply uninstall via the launcher. First, uninstall the game from Control Panel > Programs and Features, then delete the remaining game folder in SteamLibrarysteamappscommon or Epic Games…. Next, uninstall the launcher itself. For Steam, also delete the Steam folder in Program Files (x86) (after backing up any custom configurations). For Epic, delete the Epic Games folder in Program Files and the Epic Games Launcher folder in %localappdata%. Reboot, reinstall the launcher, then reinstall the game. This resolves registry corruption, broken symbolic links, and permissions stuck from an earlier version. It is time-consuming but definitive.
The “Sorry, something went wrong” error has persisted across multiple LEGO titles published by Warner Bros. Interactive, suggesting a systemic fragility in how the launcher handles Unity-based initialization with third-party DRM. Future patches may harden the startup sequence, but until then, the fix is not magical — it is a deliberate, layered process of isolating each point of failure. Users who methodically work through these steps will almost always recover the game without needing to wait for an update.
