How to Fix Minecraft Crash Exit Code 1 (PC & Server)

Your world loads for a second, the screen drops away, and Minecraft closes with nothing but “Exit Code: 1” to explain itself. It is one of the most common launch crashes in the game, and it points at a Java version mismatch, a broken mod, or an outdated graphics driver rather than any one thing. In this Nitrado guide, we’ll show you how to fix Exit Code 1 on your PC, and what to check when the same crash hits your hosted Minecraft server.

Quick Answer: Exit Code 1 usually traces back to one of four things: your installed Java version doesn’t match your Minecraft version, a mod or loader build is broken or mismatched, your graphics driver is out of date, or your launcher files are corrupted. Start with the Java version table below, then work through mods, drivers, and the launcher itself if the crash continues.

What Causes Minecraft Exit Code 1?

Exit Code 1 is a generic Java crash signal, not a description of one specific problem. Minecraft’s Java runtime reports it whenever the game fails to start correctly, and several unrelated issues can trigger it.

The usual suspects are a Java version that doesn’t match your Minecraft release, a corrupted or incompatible mod, an outdated graphics driver, or damaged launcher files. Modded servers add a fifth: a Forge, NeoForge, or Fabric build paired with the wrong Minecraft version. Because the error rarely names the actual cause, working through each possibility in order is the fastest way to narrow it down.

How to Fix Exit Code 1 on Your PC

Work through these fixes in order, starting with the simplest. Most Exit Code 1 crashes clear within the first three steps.

Restart the Launcher

Restarting the Minecraft launcher is worth trying first. It costs nothing, and it clears a stalled process often enough to be the first thing you reach for. If a restart doesn’t help, reboot your computer, or end the launcher’s process manually through Task Manager on Windows or Activity Monitor on macOS, then start it fresh.

Check and Update Your Mods

Mods are one of the most common causes of Exit Code 1, whether you run Forge, Fabric, or NeoForge. If you added or updated a mod recently, look there first. Revert your most recent change, then relaunch to see if the crash clears.

If reverting a single mod doesn’t help, remove your mods one at a time, or clear them all and reintroduce them in small batches. When Minecraft launches cleanly with no mods installed, you’ve confirmed the problem is mod related and you can work forward from there.

Update Your Graphics Driver

An outdated graphics driver can trigger Exit Code 1 alongside a range of other rendering problems. Open the Nvidia or AMD control panel, or their respective update tools, and install the latest driver for your card. Beyond clearing the crash, a current driver often improves your frame rates too.

Match Java to Your Minecraft Version

Minecraft’s Java requirement changes with the version you run, and installing the wrong one is a common cause of Exit Code 1. Mojang also renumbered the game in March 2026, moving from the old 1.21.x scheme to year-based versions starting at 26.1, so the number you’re comparing against may look unfamiliar if you haven’t updated in a while.

Check your Minecraft version in the launcher’s Installations tab, match it against the table, then visit the official Java download page, select your operating system, and install the matching version. If you already have a different Java version installed, add the correct one alongside it rather than removing the old one. The next section covers pointing Minecraft at it.

Set the Correct Java Executable Path

If Minecraft still won’t launch after installing the correct Java version, point the launcher at it directly. Open the Installations tab, hover over your profile, click the three-dot menu, and select Edit. Click More Options to expand the advanced settings, then browse to the javaw.exe or java file on your computer and enter it in the Java Executable field.

Two common paths to check:

Windows
C:\Program Files\Java\[version]\bin\
C:\Program Files\Eclipse Adoptium\[version]\bin\

macOS (Cmd + Shift + G)
/Library/Java/JavaVirtualMachines/[jdk_version_folder]/Contents/Home/bin/

Important: Select the executable that matches the Java version from the table above, then save your changes.

Repair or Reinstall the Launcher

If none of the fixes above resolve the crash, the launcher’s own files may be damaged. Repair the Minecraft launcher via the Windows repair tool. If that doesn’t help, back up your saves folder, delete the .minecraft directory, and reinstall the launcher from Minecraft’s official site.

If you use a third-party launcher like CurseForge and it was involved in the crash, reinstall that too. A corrupted install on either the official or a third-party launcher produces the same Exit Code 1 symptom, so ruling out both closes off this path completely.

Fixing Exit Code 1 on a Hosted Minecraft Server

A Minecraft server throws the same Exit Code 1 crash as your PC, usually for one of three reasons: a Java mismatch, a loader conflict, or something visible only in the crash log.

Match Your Server’s Java Version to Its Minecraft Version

Your hosted server follows the same branch as the PC table above: Java 17 for 1.20.4 and older, Java 21 for 1.20.5 through 1.21.11, and Java 25 for 26.1 and newer. A server running the wrong Java version hits the same startup failure as a PC with a mismatched install.

If you recently updated your server, or moved to a modpack built on the newer 26.x numbering, confirm the Java version moved with it. A server that ran cleanly before an update and throws Exit Code 1 after it points straight at this.

Resolve Mod and Loader Conflicts

If your server’s crash started right after you switched or updated a modpack, suspect a mismatch between your installed Forge or NeoForge build and the Minecraft version you’re running. Check that the build number matches your target version. A loader built for a different Minecraft release fails on every startup attempt, not just the first, which is what separates this from a one-off crash.

This catches people out most often after a modpack update, when the pack’s required Minecraft version moves but the server’s loader build stays where it was.

Read the Server Crash Log

Before you change any settings, check what the server actually reported. In your Nitrado Web Interface, open File Browser under Tools, then open your Minecraft server folder and look inside the crash-reports folder for the most recent dated report. For a live session, latest.log carries the same information.

The first line marked ERROR or FATAL usually names the mod, file, or version conflict responsible. That one line tells you whether you’re chasing a Java mismatch or a loader conflict, and it can save you from working through every PC fix above on a problem that was server-side all along.

Exit Code 1 Quick Answers

Why Did Exit Code 1 Start After I Updated Minecraft?

Because updating the game can change the Java version it needs. Minecraft moved to Java 21 at version 1.20.5 and to Java 25 at 26.1, so an update across either of those lines leaves you on a runtime the game no longer accepts. Check your version against the table above before assuming a mod is at fault.

Why Does My Minecraft Server Need a Different Java Version Than My PC?

It doesn’t. It needs to match the same Minecraft version your PC does. Exit Code 1 on a hosted server often comes down to the server sitting on an older Java version after your PC has already moved to a newer Minecraft release. Match both against the same table and the mismatch resolves.

Is Exit Code 1 Always Caused by Mods?

No. Mods are a common cause, but a mismatched Java version, an outdated graphics driver, or a corrupted launcher install all produce the same Exit Code 1 message on an unmodded setup.

Keep Your Minecraft Server Crash-Free

With your Java version matched, your mods checked, and your launcher running clean, Exit Code 1 stops being the thing standing between you and your world. Most crashes trace back to one of the causes above, and working through them in order is faster than guessing. If your server keeps crashing after all of this, back up your world before you change anything else, then head back into the Web Interface and confirm your loader build and Minecraft version still agree.