The Meaning of Life, the Universe, and Everything.
Location:
Eureka, CA
Join Date:
1/2/2013
Posts:
60
Location:
Eureka, CA
Minecraft:
MrPapaveraceae
Member Details
Pardon me? It was working fine before.
It was doing this for all the jars. So my latest attempt was to try launching the latest jar version.
I'm not even sure how to describe my problem, cause the error is not very descriptive with no error code.
I made two attempts to fix, the first was downloading the latest installer. First try to repair files. Same problem. Then I removed and reinstalled the game and still the same problem.
You can see the only warning that pops up on the log in the background. I've posted links to the logs below.
That error seems fairly descriptive to me. Simply put, the Minecraft json file contains a hash that is used to verify a jar of the same name; IE, the hash generated from the jar did not match the hash stored in the json file. Either the Jar is corrupted, or the Json is corrupted. Either way, I'd advise you to delete the folder "1.12.2" at "C:/Users\Preston Jones\AppData\Roaming\.minecraft\versions\1.12.2\"
The Meaning of Life, the Universe, and Everything.
Location:
Eureka, CA
Join Date:
1/2/2013
Posts:
60
Location:
Eureka, CA
Minecraft:
MrPapaveraceae
Member Details
I won't be able to do that right away. I'll look into it after a few hours. I'm hoping all it is - is a bug. I may also try some other things first, run some maintenance tools and restart.
The Meaning of Life, the Universe, and Everything.
Location:
Eureka, CA
Join Date:
1/2/2013
Posts:
60
Location:
Eureka, CA
Minecraft:
MrPapaveraceae
Member Details
Okay. I did some extra things. Cleaning, scanning and updating, I reinstalled the game again and still same thing. I also noticed that my thread is in the wrong forum. It's in modded MC. I don't know how I managed that. I'm playing vanilla and my client is unmodded. If there's a moderator that can move my thread, that would be awesome.
I'm having an interesting problem with the download to old launcher linked above. I gave it a try, I ran it as a containment with Comodo (no offense, I just had to play it safe) and it ran. It wouldn't allow me to log in to my Minecraft account, so I was able to only play as a demo. The game could at least run okay.
I closed it and I ran it again without the containment and it won't even start the application when double clicking it.
After this, I decided to do some more experimenting and I tried to contain the new launcher and I was able to play again, in the demo mode. I played for a while in 1.12.2 and the game plays fine. After the demo expired, I closed and reopened the new launcher as normal, without the containment with the firewall and when I tried to start a new game, it crashed again.
I don't know if that would help give someone a clue on what's going on.
I figured it out. It took more frowning at the computer screen and fidgeting and tinkering. Getting the old copy of the Minecraft launcher helped. So, thanks, Echofall.
Using the copy older launcher version made me think to turn on some extra protection around the application when executing it and I found out the game can at least start and generate a new world and I could play it fine, despite not being able to log in.
Turning the shield off, the game wouldn't work at all. So trying the new launcher and testing it out with the containment off and on, it was doing the same thing, with it being able to play and not being able to at all.
I figured it seemed like it was my firewall, but I went ahead and not only disable my firewall, but closed the program entirely. I took the extra step and disabled my AV. Then it worked! A little more tinkering, I found it wasn't my firewall, but my AV that was causing it to crash. So I added the whole folders of "...\Program Files (x86)\Minecraft\*" and "...\AppData\Roaming\.minecraft\*" in the AV exclusions and it works now. I can only assume it wan a recent update that changed the AVs behavior.
Now I can get back to working on my server and deal with server side issues that keep breaking.
I don't see where the option is to change the thread, but this can be marked as solved.
Pardon me? It was working fine before.
It was doing this for all the jars. So my latest attempt was to try launching the latest jar version.
I'm not even sure how to describe my problem, cause the error is not very descriptive with no error code.
I made two attempts to fix, the first was downloading the latest installer. First try to repair files. Same problem. Then I removed and reinstalled the game and still the same problem.
You can see the only warning that pops up on the log in the background. I've posted links to the logs below.
Crash log: https://paste.ubuntu.com/p/4tT9YH3Qz2/
DxDiag log: https://pastebin.com/9iGFVyBu
Est. 2011 (1.7.3 Beta)
That error seems fairly descriptive to me. Simply put, the Minecraft json file contains a hash that is used to verify a jar of the same name; IE, the hash generated from the jar did not match the hash stored in the json file. Either the Jar is corrupted, or the Json is corrupted. Either way, I'd advise you to delete the folder "1.12.2" at "C:/Users\Preston Jones\AppData\Roaming\.minecraft\versions\1.12.2\"
I do this for fun
I tried that for 1.12.2, deleting the file and letting the launcher upload it again and the same thing happened.
Est. 2011 (1.7.3 Beta)
Let's try setting the launcher's compatibility settings to Windows 7.
EDIT: Also update your Graphics Driver if possible.
I do this for fun
Still same problem.
Est. 2011 (1.7.3 Beta)
It may be a bug in the new launcher. Here's a link to the old Minecraft Launcher:
https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.exe
You will need Java installed to run it.
I do this for fun
I won't be able to do that right away. I'll look into it after a few hours. I'm hoping all it is - is a bug. I may also try some other things first, run some maintenance tools and restart.
Est. 2011 (1.7.3 Beta)
Okay. I did some extra things. Cleaning, scanning and updating, I reinstalled the game again and still same thing. I also noticed that my thread is in the wrong forum. It's in modded MC. I don't know how I managed that. I'm playing vanilla and my client is unmodded. If there's a moderator that can move my thread, that would be awesome.
I'm having an interesting problem with the download to old launcher linked above. I gave it a try, I ran it as a containment with Comodo (no offense, I just had to play it safe) and it ran. It wouldn't allow me to log in to my Minecraft account, so I was able to only play as a demo. The game could at least run okay.
I closed it and I ran it again without the containment and it won't even start the application when double clicking it.
After this, I decided to do some more experimenting and I tried to contain the new launcher and I was able to play again, in the demo mode. I played for a while in 1.12.2 and the game plays fine. After the demo expired, I closed and reopened the new launcher as normal, without the containment with the firewall and when I tried to start a new game, it crashed again.
I don't know if that would help give someone a clue on what's going on.
I figured it out. It took more frowning at the computer screen and fidgeting and tinkering. Getting the old copy of the Minecraft launcher helped. So, thanks, Echofall.
Using the copy older launcher version made me think to turn on some extra protection around the application when executing it and I found out the game can at least start and generate a new world and I could play it fine, despite not being able to log in.
Turning the shield off, the game wouldn't work at all. So trying the new launcher and testing it out with the containment off and on, it was doing the same thing, with it being able to play and not being able to at all.
I figured it seemed like it was my firewall, but I went ahead and not only disable my firewall, but closed the program entirely. I took the extra step and disabled my AV. Then it worked! A little more tinkering, I found it wasn't my firewall, but my AV that was causing it to crash. So I added the whole folders of "...\Program Files (x86)\Minecraft\*" and "...\AppData\Roaming\.minecraft\*" in the AV exclusions and it works now. I can only assume it wan a recent update that changed the AVs behavior.
Now I can get back to working on my server and deal with server side issues that keep breaking.
I don't see where the option is to change the thread, but this can be marked as solved.
Est. 2011 (1.7.3 Beta)