I may have to, however I did reinstall the game yesterday. There is something else going on here for this to continually be an issue, and for many many users of the software. The native launcher should not continually fire like this. It should download save and be available, only needing to check for updates, not continually download. Has anyone opened a ticket with Mojang on this issue?
Day 1: launcher would fire every time I would open the program, game would start
Day 2: launcher would fire and receive the same error as OP
Day 2: uninstalled Minecraft, updated java, reinstalled minecraft, launcher would fire, but game would start
Day 3: launcher is still firing, but back to seeing the error code 5 as before.
Day 3: deleted the .tmp file as recommended, however I am still getting the launcher issue AND the error code, and I have repeated this step multiple times, without it fixing for me.
Honestly, going in and uninstalling or deleting files is not a fix, it's a sloppy work-around. Anyone know if Mojang is looking into this issue?
1
https://bugs.mojang.com/browse/MCL-5291
0
I may have to, however I did reinstall the game yesterday. There is something else going on here for this to continually be an issue, and for many many users of the software. The native launcher should not continually fire like this. It should download save and be available, only needing to check for updates, not continually download. Has anyone opened a ticket with Mojang on this issue?
0
Manual launch steps?
0
I too am having this same error.
Day 1: launcher would fire every time I would open the program, game would start
Day 2: launcher would fire and receive the same error as OP
Day 2: uninstalled Minecraft, updated java, reinstalled minecraft, launcher would fire, but game would start
Day 3: launcher is still firing, but back to seeing the error code 5 as before.
Day 3: deleted the .tmp file as recommended, however I am still getting the launcher issue AND the error code, and I have repeated this step multiple times, without it fixing for me.
Honestly, going in and uninstalling or deleting files is not a fix, it's a sloppy work-around. Anyone know if Mojang is looking into this issue?