Launcher Crashes when I try to run the game. I am running Windows 10, Java 8, AMD Radeon R9 300 Series. Screenshot of the crash included. Never had any trouble running MC until the new launcher. I was able to get on February 4th, after the launcher crashed several times. Since then, I have been unsuccessful. Please help!
Related issues
is duplicated by
Attachments
Comments



You cant confirm your own issues 😛, you have a nvidia gpu?
@unknown, it's a different person.
Please attach the launcher log (which should be located inside of your .minecraft folder) here.

It launched once fine and crashed second time

This is what happened when I tried again this morning:

Is this the right one?

And again:

I also have had this problem, it tries to download the version, then says "Minecraft Launcher has stopped working" then proceeds to crashing

Horrible problem, please fix it ASAP. It's literally impossible to play the game due to this bug existing.

You can use the steps described in this reddit post to get the old launcher and be able to play while this bug is not fixed.

Having the same problem here on version 1.8.9. Uninstalled minecraft and reinstalled. Ensured up to date Java is installed. Did try checking on the compatibility file for javaw.exe which I saw as a possible way to fix but the compatibility does not include windows 10 as an option. I don't understand how some users are not having this problem on windows 10 but I still do. Any help would be greatly appreciated in resolving this issue.

I have the same problem on Windows 7. No NVIDIA devices, and an up-to-date Java. My Anti-Virus is not interfering, either.
I would hope this gets fixed soon, because it's a right pain.

This bug has been incredibly aggravating. I'm running a completely fresh install of Windows due to a mess VS2017 caused. Only things installed are drivers, Notepad++, VS2008, Firefox, Java and Minecraft. Haven't even done any of my usual configuration and tweaking of Windows like I normally do after a fresh install so it's a bog standard Windows 7 Professional install updated without any of the optional hot fixes.
Haven't noticed anything too odd in the logs other than it reporting Java 1.8.0_25 installed, stating it's outdated and that I should install Java 1.8.0_25 before running. I have noticed that when I start the launcher there are 2 or 3 processes called "MinecraftLauncher" running but I wrote that off as not grouping up processes under the same parent process like that horrendous mess called Chrome. While bad practice (as I've been taught) it wont exactly break anything so it's more a style choice.
The thing about when that launcher crashes is that it seems to randomly take out Minecraft with it. Sometimes it crashes out and Minecraft launches just fine. Others it crashes and causes Minecraft to go unresponsive either during loading or world loading. Now I found you can avoid the world loading crash simply by force killing the launcher process before loading a world.
One thought I have is to add a security policy for Minecraft's specific copy of Java, one to escalate it out of UAC. This is a fix that I know works for some software but considering it disables safeguard that protect your computer not just from malicious attacks but also programmer accidents. I am weary of doing that for software I didn't compile on this machine personally since anywhere in transit that executable could have been tampered with.
I know that's one thing that could potentially cause this with Windows Vista on up. If the application doesn't declare what permissions it needs, Windows may not grant them. Ran into that myself with .NET software I wrote and I know there are similar mechanisms (if not the same mechanism) in place for all software.

I am having the same problem on the newest launcher

So what is the solution for this issue?

Same problem confirmed on launcher version 2.0.847.

One thing I found is that if I change launcher language to "English US" and create a profile with Minecraft 1.9.4 the launcher doesn't crash, but that is all I found.

this makes me so mad when my issue is a duplicate of an issue that still aint fixed mojang needs to get to fucking work and fix their fucking game

ikkrrrr

Confirmed to be still an issue. It's been several weeks I have been waiting now..... can I get my money back if this bug is not fixed?????????

Do not swear in your bug reports.