Minecraft Exit Code 1 — game crashes on launch
Exit Code 1 — crash on launch
Verified against Mojang Support — Minecraft Java Edition crash troubleshooting, Minecraft Wiki — Tutorials/How to get a crash report, Forge community documentation — Troubleshooting mod crashes · Updated June 2026
> quick_fix
Open your launcher, go to the crashing profile's settings, and make sure the correct Java version is selected. Minecraft 1.17+ requires Java 17 or newer. If you have mods installed, remove them all and add them back one at a time to find the broken one.
# Check which Java version Minecraft is using
java -version
# Minecraft 1.17-1.20.4 needs Java 17, 1.20.5+ needs Java 21
# If wrong version, install the correct one:
# Windows: winget install Oracle.JDK.21
# macOS: brew install openjdk@21
# Linux: sudo apt install openjdk-21-jdkWhat causes this error
Exit Code 1 is Java's generic 'unhandled exception' exit status. Minecraft terminated because the JVM hit a fatal error it couldn't recover from. The three most common triggers are: (1) a mod compiled against a different Minecraft or Forge/Fabric version, (2) the wrong Java version for the Minecraft version you're launching, and (3) a corrupted game installation where essential class files are missing or damaged. The actual cause is always in the crash log, but the launcher only surfaces 'Exit Code 1.'
How to fix it
- 01
step 1
Read the crash log
The crash log contains the actual error. Find it at .minecraft/crash-reports/ (latest file) or check the launcher's log output. Look for the first 'Caused by:' line — that's usually the real problem.
Crash log locations: Windows: %appdata%\.minecraft\crash-reports\ macOS: ~/Library/Application Support/minecraft/crash-reports/ Linux: ~/.minecraft/crash-reports/ - 02
step 2
Check your Java version
Minecraft 1.17 through 1.20.4 requires Java 17. Minecraft 1.20.5 and newer requires Java 21. Running the wrong version causes an immediate Exit Code 1. The official launcher bundles the correct Java, but third-party launchers (MultiMC, Prism, ATLauncher) often use your system Java.
# Verify Java version java -version # Should show 17.x.x for MC 1.17-1.20.4 # Should show 21.x.x for MC 1.20.5+ - 03
step 3
Remove all mods and test vanilla
Move your mods folder out of .minecraft temporarily. Launch the game. If vanilla works, add mods back one at a time to find the culprit. Pay attention to mod loader version — a Forge 1.20.1 mod will crash on Forge 1.20.4.
- 04
step 4
Delete and re-download the version
In the launcher, go to Installations, find the crashing version, delete it, and create a new installation for the same version. This re-downloads all game JARs and fixes corruption from interrupted updates.
Manual cleanup: 1. Close the launcher 2. Delete .minecraft/versions/<version-folder>/ 3. Open launcher → Installations → New → select same version 4. Launch - 05
step 5
Allocate enough RAM
If the crash log shows 'java.lang.OutOfMemoryError' before Exit Code 1, you need more RAM. In launcher settings, set JVM arguments to allocate at least 2GB for vanilla, 4-6GB for modded.
JVM Arguments (set in launcher profile): Vanilla: -Xmx2G -Xms1G Light modpack (50 mods): -Xmx4G -Xms2G Heavy modpack (200+ mods): -Xmx6G -Xms4G
How to verify the fix
- Minecraft launches past the Mojang splash screen and reaches the main menu
- Clicking Singleplayer and loading a world completes without crashing
- No new files appear in .minecraft/crash-reports/ after launching
Why EXIT1 happens at the runtime level
When the JVM exits with code 1, it means System.exit(1) was called or an uncaught exception propagated to the top-level thread. Minecraft's Bootstrap class catches Throwable in its main() method and calls System.exit(1) for any unrecoverable error. The launcher process monitors the JVM's exit code via Process.waitFor() and reports it. The actual fatal exception — whether it's a ClassNotFoundException from a missing mod dependency, an UnsupportedClassVersionError from wrong Java, or a NullPointerException in a broken mod's init — is written to the crash report before the exit call.
Common debug mistakes for EXIT1
- Allocating too much RAM (e.g., 16GB) which causes garbage collection pauses so long the watchdog thread kills the server with Exit Code 1.
- Installing a Forge mod into a Fabric instance or vice versa — they are completely incompatible and the mod loader crashes instantly.
- Using Java 8 for Minecraft 1.17+ because an old tutorial said to — Java 8 cannot load the game's class files compiled for Java 17+.
- Ignoring the crash log and reinstalling Minecraft, which doesn't remove mods or configs from .minecraft and the same crash repeats.
- Running 32-bit Java on a 64-bit OS, which caps available RAM at 1GB and crashes modded installations immediately.
When EXIT1 signals a deeper problem
Repeated Exit Code 1 across different Minecraft versions and without mods points to a system-level Java problem. Corrupted Java installations — especially when multiple JDK vendors coexist (Oracle, Adoptium, GraalVM, Azul) — cause class-loading conflicts that crash at startup. Aggressive antivirus software (especially Avast and McAfee) is known to quarantine Java class files inside the .minecraft directory mid-download, leaving corrupted JARs that pass the launcher's checksum but fail at class load. The most insidious case is Windows users with a GROUP_POLICY that redirects %appdata% to a network drive — Java's file locking doesn't work reliably over SMB, causing random class file corruption on every update.
Editor's take
Exit Code 1 is the most searched Minecraft error for a reason: it tells you absolutely nothing. The JVM exited with status 1. That's it. Every Java program that crashes for any reason exits with code 1. Minecraft's launcher treats this as a specific error and shows it in a dialog box as if it means something diagnostic, but it's the equivalent of a doctor saying 'something's wrong.'
The real information is always in the crash report, and the single most useful skill for any Minecraft player is learning to read one. Open the latest file in .minecraft/crash-reports/, scroll past the system information block, and find the first 'Caused by:' line. That's your error. If it says ClassNotFoundException, a mod is missing a dependency. If it says UnsupportedClassVersionError, your Java version is wrong. If it says OutOfMemoryError, you need more RAM allocated.
The mod ecosystem makes Exit Code 1 dramatically more common. A typical modpack has 200+ mods, each compiled against a specific Forge or Fabric version. Update one mod without updating its dependencies and you get Exit Code 1. Downgrade Forge to match a mod and three other mods break. This is why modpack launchers like CurseForge and Modrinth exist — they version-lock everything together.
The Java version problem deserves special attention. Minecraft's Java requirements changed three times in recent versions: Java 8 for 1.16 and below, Java 17 for 1.17-1.20.4, and Java 21 for 1.20.5 onward. The official launcher handles this automatically by bundling its own JRE, but every third-party launcher (MultiMC, Prism Launcher, ATLauncher, GDLauncher) defaults to your system Java. If your system Java is wrong, every launch crashes. The fix is a one-time configuration in the launcher's Java settings to point at the correct JDK path.
By Bikram Nath · Curator · Updated June 2026
Frequently asked questions
Exit Code 1 only happens with one specific modpack — what do I do?
Check the modpack's required Forge/Fabric/NeoForge version and Java version. Modpacks are version-locked — running ATM9 on Forge 47.2.0 when it needs 47.1.3 will crash with Exit Code 1. Install the exact loader version the modpack specifies.
I'm using the official launcher and haven't installed any mods. Why Exit Code 1?
Most likely a corrupted download. Delete the version folder inside .minecraft/versions/, then re-launch. If that doesn't work, fully uninstall the launcher (including .minecraft) and reinstall from minecraft.net. Back up your worlds folder first.
Does Exit Code 1 mean my computer can't run Minecraft?
No. Exit Code 1 is a software error, not a hardware limitation. Even very old computers can run Minecraft if the Java version and mods are compatible. Hardware issues show different errors like Exit Code -1 (GPU driver crash) or complete freezes.