when I try to start my Minecraft 1.14.4, it starts up but when it's finished loading it crashes and sends me back to the launcher. Back at the launcher it says unexpected issue has occured. When I try to view the crash details it won't let me. However when I try to play Minecraft on 1.8.9 I can start up my launcher. Can someone help me please?
Launcher version: 2.1.5964
ย
Linked issues
Attachments
Comments 12
it started for me yesterday but i had played previously, i had closed the game and 30 mins to one hour later i relaunched it and it crashed. i thought it was a one time thing so i tried again and it still didn't work. the thing is it works for my friends but not me. I tried again today and it still doesn't work. i really want to get back to playing Minecraft so it would be very much appreciated if myself and the others who are experiencing this bug was given a possible way to fix this, or have this patched as soon as possible.
itย been happening to me for the last few weeks, it would let me play for couple days and then it say error game crashed as unexpected issus occurred and game has crashed. were sorry for the inconvenience, try to look at the crashed report it dont show me anything i end up deleting it from my pc all the files and reinstall the game... it getting really annoying it do it everyday, i see im not the only one have this problem few others have the same problem as me they need to fix this, i just got back into playing minecraft few months back i do really enjoy the game i fear they gonna lose lot of players who love this game if this dont get fix, i had this problem since the latest update
ย
ย
Thank you for your report!
We're actually already tracking this issue in MC-32606, so I resolved and linked this ticket as a duplicate.
However, that ticket has already been resolved. Depending on the resolution, that can mean that it either will be fixed in the next version, or that it is not considered a bug and won't be fixed.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Same here