Launcher problems

HMCL Launcher Error: java.io.IOException: Read end dead

What it looks like in the log

java.io.IOException: Read end dead

How to fix it

  1. Update Hello Minecraft! Launcher (HMCL) from legacy version 2.x to HMCL 3.x or newer, where the faulty piped log reader was completely rewritten.
  2. If you must use an older HMCL 2.x build, turn off the launcher's live log viewer window in the profile/launcher settings so LaunchingUIDaemon does not pipe console output.
  3. If Minecraft also closed unexpectedly, open the .minecraft/logs/latest.log file or the .minecraft/crash-reports/ folder directly to find the real crash cause hidden by the 'Read end dead' spam.
  4. Check your antivirus history (such as Kaspersky) and add an exclusion for your Java executable and .minecraft folder if security software is forcibly terminating the game process.
LoadersForge, Vanilla
SeverityBreaks something
CategoryLauncher problems

Check your own log

Related errors

Launcher problemsATLauncher AccessDeniedException When Deleting temp/natives FolderDo not troubleshoot this AccessDeniedException directly; scroll up in the ATLauncher console above the 'Oh no.Launcher problemsFabric Crash: Could Not Create Directory (Windows Path on Linux)Open your Minecraft launcher, delete the existing Iris profile migrated from Windows, and delete the old versiLauncher problemsHMCL ChecksumMismatchException: Incorrect Checksum (SHA-1) During Forge/NeoForge InstallUpdate HMCL to the latest stable or development version, which includes fixes for Forge installer processor chLauncher problemsHMCL Crash: Not on FX Application ThreadClose the error window and reopen HMCL; because this is a timing race condition during startup, simply restartLauncher problemsHMCL Launcher Error: SAXParseException in Log4jHandlerUpdate Hello Minecraft! Launcher (HMCL) to version 3.x (or at least 2.7.8.45+) from the official HMCL website Launcher problemsMultiMC Fails to Launch: Not Enough Arguments (org.multimc.NotFoundException)Connect to the internet and launch the instance using standard 'Launch' (not 'Launch Offline') at least once s