: Corrupted local user initialization ( .ini ) configuration files.
Follow these troubleshooting steps in order to resolve the issue. 1. Clear Local App Data/Configuration Files
Most users encounter this issue due to a handful of megabytes failing to properly download during a fresh install or a title update. Launch and navigate to your Library . null coreerrorsopen failed mortal kombat new
If you’ve just installed a new Mortal Kombat game — whether it’s MK1 (2023), MK11 , or an older title with a fresh update — and you’re greeted by a cryptic error message saying you’re not alone. This error has been popping up for PC players, especially after patches, driver updates, or using unofficial game versions.
: Old graphics or network drivers can prevent the engine's "Kore" (Core) system from initializing correctly. Recommended Troubleshooting Steps : Corrupted local user initialization (
A damaged engine.ini or user settings file can lead to null pointer references when the game tries to log errors.
null coreerrorsopen failed in the context of a new Mortal Kombat game (likely Mortal Kombat 1 or a recent update to Mortal Kombat 11 ). This error has been popping up for PC
It looks like you’re trying to interpret an error message or log related to Mortal Kombat (possibly a new version, mod, or emulated release).
: Go to the Installed Files (or Local Files) tab.
If you want, tell me your platform (Windows/PlayStation/Xbox/switch/emulator) and whether the game is modded or from Steam — I’ll give a tailored next step.
Find the game in your sidebar, right-click it, and select Manage . Go to the Extensions or Subscription Content tab and verify the "Story Content" box is checked. Click Apply Changes to queue the download. 3. Clear Local AppData Configuration Folders
