At some recent version, I don't recall when it started exactly, the Minecraft client started to take forever to start up and would hang for a while at the end of the progress bar. My best guess is that this is due to the client calling home or waiting for some kind of network handshake that has a hard delay on it. It could also be reading form disk or building some kind of cache, but I don't know for sure.

Does anyone know WHY the client hangs at this point at startup?

enter image description here

  • Google "LazyDFU" and see if that mod helps. Commented Sep 9, 2022 at 13:18
  • I'm not sure this can be answered, only Mojang knows
    – pinckerman
    Commented Sep 9, 2022 at 14:04
  • @pinckerman why can't someone else find out using the obfuscation maps? Commented Sep 9, 2022 at 15:33

2 Answers 2


To know what happens in the loading sequence at that point, you could enable the game output logs.

In the launcher, go to Settings, and then check the "Open output log when the game starts" checkbox, and then launch Minecraft. Along with the game, it should also open an extra window with the logs.

That could probably answer what's going on with the game when it hangs.

In the older (v1.X) launcher, there was the Output log and the Development Console, where the Console outputs were a lot more detailed than the ones found in the Output log. But after the major v2 overhaul, the Development console was removed.


Not really the answer as to why, but I had the same issue and it stopped occurring when I supplied a custom log configuration to Minecraft client that did not include console output.

E.g. I removed this section of the logging config:

<Console name="SysOut" target="SYSTEM_OUT">
  <LegacyXMLLayout />

and the corresponding AppenderRef below it.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .