Minecraft exit code 1: a crash with a paper trail

Exit code 1 is Minecraft's generic 'the game died' signal, shown by the launcher when Java exits abnormally during startup. By itself it says nothing about the cause, which is usually a broken or mismatched mod, a corrupted config file, a damaged installation, or the wrong Java version for the build. The actual reason is always written in the game log; the method below finds it.

Fix it, in order

  1. Read the log first. In the launcher, enable the output log (Settings, 'Open output log when games start'), or open latest.log in the game's logs folder. The lines just before the crash name the mod or file involved far more often than not.
  2. Remove mods in halves. Exit code 1 on a modded install is a mod problem until proven otherwise. Take out half the mods; if it launches, the culprit is in the removed half. Repeat until one mod remains.
  3. Check versions match: the mod loader (Forge, Fabric, NeoForge), each mod, and the Minecraft version must all agree. A mod built for another version is the single most common cause.
  4. Rename the config folder (or the specific mod's config named in the log) and relaunch; a corrupted config regenerates with defaults.
  5. For vanilla installs, repair the installation: in the launcher, find the installation, and let it re-download, or delete the version's folder inside versions and relaunch to fetch a clean copy.
  6. Check the Java runtime: modded setups pointing at a custom Java executable should use the version the loader expects (Java 17 for 1.17-1.20.4 era builds, Java 21 for 1.20.5 and newer). A mismatched runtime crashes instantly with this code.

Exit code 1 on a totally vanilla game

With no mods involved, the suspects narrow to a corrupted game file (fixed by re-downloading the version), a broken launcher profile (create a fresh installation in the launcher and test), graphics drivers (update them, especially after an OS upgrade), or an overlay/antivirus interfering at launch. Testing a fresh installation profile is the cleanest experiment, it changes nothing about your worlds, which live in the saves folder, not the installation.

Back up worlds before surgery Worlds live in the saves folder of your Minecraft directory. Copy them somewhere safe before deleting or reinstalling anything beyond the version folders. Exit code fixes never need to touch saves, and a backup makes every step reversible.

Common questions

Is exit code 1 a Java problem? Sometimes, but not by default. A wrong Java version produces it, yet on modded installs a mismatched mod is more common. The log distinguishes them in seconds: Java faults mention the runtime, mod faults name the mod.

It worked yesterday and nothing changed. What gives? Something did change, usually quietly: a mod auto-updated, a config was edited by a crash mid-write, or a driver or Windows update landed. The log plus 'what updated last' is nearly always the answer.

Related

Minecraft exit code 0 · Minecraft exit code 255 · Minecraft GLFW error 65542 · Could not create the Java Virtual Machine