Launcher problemsMissing Log4j Library on Launch (LogManager ClassNotFoundException)
What it looks like in the log
java.lang.ClassNotFoundException: org.apache.logging.log4j.LogManager
How to fix it
- Launch a clean Vanilla profile of the exact same Minecraft version once before starting your modded profile so the launcher downloads all required base libraries.
- Use your launcher's Repair or Verify option—or manually delete the libraries/org/apache/logging/log4j folder inside your launcher data directory—to force a fresh download of Log4j.
- Update your third-party launcher (such as HMCL or GDLauncher) to its latest release to fix bugs where base game libraries are omitted from the launch command.
- If every instance in your launcher fails with this error, back up your worlds and mods, then completely reinstall the launcher to rebuild its corrupted shared files.
| Loaders | Fabric, Forge, Vanilla |
|---|
| Severity | Stops the game |
|---|
| Category | Launcher problems |
|---|
Check your own log