Fix Minecraft Exit Code 100: 2026 Java Edition Troubleshooting Guide
Minecraft Exit Code 100 does not point to one documented cause or one universal fix. The number is an exit status shown after the Java Edition game process closes; by itself, it cannot tell you whether a mod, custom Java path, game file, graphics driver, or another problem caused the shutdown. “Century Crashes” is not an official Minecraft error category. Treat the code as a symptom, then use a clean test profile and the crash log to find the actual failure.
This guide covers Minecraft: Java Edition. Start with the low-risk checks below. Keep your worlds intact, avoid random JVM tweaks, and change one thing at a time so you can tell which test helped.
What Exit Code 100 tells you
The launcher may display an exit code when the game process ends abnormally, but Minecraft Help does not document Exit Code 100 as a diagnosis with a specific cause. The message is not proof of a Java version mismatch, a corrupted install, low memory, or an antivirus block. The useful evidence is the crash report or the lines in the log immediately before the process stopped.
Use the point where the crash happens to choose your first test:
| When it crashes | What to check first |
| Before the game window appears | Custom Java executable, launcher installation settings, and the first exception in the log. |
| While a world is loading | Mods, shaders, resource packs, and whether the same world works from a clean profile. Back up the world before testing. |
| Only with a modded profile | Whether each mod matches the exact Minecraft version and the installed loader version. |
| After a graphics or operating-system change | Graphics drivers, overlays, and the relevant OpenGL or graphics error in the log. |
Step 1: Record the crash details and protect your worlds
Write down the exact Minecraft version, whether you are using the official Launcher or a third-party launcher, the loader (if any), and what you were doing when the crash occurred. Copy the complete launcher message rather than searching only for “100.” Then check the game directory for logs/latest.log and, if one was created, the newest file in crash-reports. Some Java crashes also create a file named like hs_err_pid1234.log.
Read the first error or exception around the time of the crash. Search for terms such as Caused by, a mod name, or a graphics library error. The last line is not always the root cause, so include several lines before it when you ask for help. Avoid posting account tokens, full computer usernames, or other private data from logs publicly.
If a world matters to you, back it up before changing files or reinstalling anything. Minecraft Help explains how to create a Java Edition world backup in its official world backup instructions. Do not delete the entire game folder as a first fix.
Step 2: Test a fresh installation of the same version
A new installation gives you a useful comparison without destroying the profile that currently fails. In the Minecraft Launcher, select Minecraft: Java Edition, open Installations, and choose New installation. Name it something recognizable, select the same game version as the failing profile, and install it. Mojang’s launcher-crash instructions recommend this test; if the new profile launches, investigate downloaded mods or advanced settings in the old profile.
Start the test profile with its default settings. If it works, the basic launcher and that game version can run, which narrows the problem to something customized in the old installation. If it fails in exactly the same way, note that result and continue to the log-based checks below.
Step 3: Restore the default runtime and test without mods
If the failing installation has a custom Java executable, change it back to the launcher-managed runtime for the test. Minecraft releases can use different Java versions: Mojang’s 26.1 release notes state that the game moved to Java 25 and includes the Microsoft build of OpenJDK 25. That is why a blanket instruction to install Java 21 is unsafe for every version. Let the official Launcher select the runtime unless you have a specific reason to use a custom one; if you use a third-party launcher, check its documentation for the runtime required by your exact game version.
Also remove custom JVM arguments for the test or restore the profile’s original arguments. Do not paste a long “performance” command from a forum. Minecraft’s memory-allocation guidance notes that an unsuitable allocation can cause crashes, lag, or stuttering, and the 26.1 release notes set a 4 GB default allocation. Keep the default as a baseline, especially if you do not know how much memory is available to other programs. See the official memory-allocation troubleshooting guide before making a deliberate adjustment.
For a modded profile, move the mods folder out of that instance temporarily instead of deleting it. Also disable shaders and resource packs for the test. Launch vanilla, then restore items one at a time. A crash that returns immediately after restoring one mod or pack points to a compatibility issue; check that it supports the exact Minecraft release and loader you are running.
Step 4: Update the remaining software, then repair the launcher
If a clean vanilla profile still crashes, install operating-system updates and the current graphics driver from your computer or GPU manufacturer. Minecraft’s official video and graphics troubleshooting page recommends checking outdated software and graphics drivers for visual or performance problems. Close recording tools, overlays, and graphics utilities for one test so they are not adding another variable.
Use the Launcher’s Latest Release option for a separate test if the crash occurs on an older or snapshot version. Keep the original profile and world unchanged; a version change can affect mods and world data. If the launcher itself appears damaged, reinstall the Launcher from Minecraft’s official download page. Reinstalling the launcher is different from deleting the whole game directory, which can put saves and settings at risk.
If the problem remains, send Minecraft Support or the official bug tracker the exact game version, launcher type, steps that reproduce the crash, and relevant log or crash report. Include whether a clean same-version profile launched and whether vanilla works. Those details are more useful than the exit code alone.
Quick checks before you retry
- Confirm the article applies to Java Edition, not Bedrock Edition.
- Keep the world backed up and preserve the old profile.
- Try a new installation using the same game version.
- Use the launcher-managed Java runtime and default JVM arguments for the baseline test.
- Test without mods, shaders, and resource packs; restore them one at a time.
- Read the log around the first exception and share only the relevant, privacy-checked details.
Frequently asked questions
Does Minecraft Exit Code 100 always mean Java is outdated?
No. The code alone does not identify the cause. A custom Java path can be incompatible, but a mod, graphics issue, installation setting, or another failure can also stop the game. Use the crash report and the clean-profile test to narrow it down.
Should I install Java 21 to fix Exit Code 100?
Not as a universal fix. Java requirements vary by Minecraft version, and Mojang’s Java 26.1 notes document Java 25. First restore the launcher-managed runtime. Only set a custom Java executable after checking the requirement for the exact version and launcher you use.
Will deleting and reinstalling Minecraft fix the crash?
It may help when files are damaged, but deleting the full game folder is a risky early step. Test a new installation first and back up worlds before any manual cleanup. If you need to reinstall, use the official launcher instructions and preserve your saves.
Does this guide apply to Bedrock Edition?
No. This troubleshooting sequence is for Minecraft: Java Edition and its Java runtime, launcher installations, and mods. Bedrock Edition uses different support and error-code paths.
Sources