Minecraft launcher works fine for second before showing ''Whoops! an error occurred'' message.

Please see if community support can help resolve the issue.

Quick Links:
📓 Bug Tracker Guidelines -- 💬 Community Support -- 📧 Mojang Support (Technical Issues) -- 📧 Microsoft Support (Account Issues) -- ✍️ Feedback and Suggestions -- 📖 Game Wiki

Same issue with windows 11.24h2 - the legacy launcher fix worked for me.

Hi
Could you check your computer for updates and see if the issue still occurs?
Could you also let us know if the issue occurs with newly installed Launcher or one you had for some time?

This ticket will automatically reopen when you reply.

For me: System is freshly updated, Launcher is one that I used for months and it stopped working a couple of weeks ago just like that. Is there any way I can submit some debug info?

Looks like that did the trick for me:

rm -rf ~/.minecraft/

rm -rf ~/.minecraft/

Well, I reported the previous message a bit too early. Launcher starts once when I delete the configs as per my previous post and I can start/play java edition of Minecraft. However whenever I quit the game and the launcher and restart it, I face the issue again:

Issue still there. Any updates? Really annoying to loose login info and game settings upon each game start…

Hi!
Could you upload a video of this issue happening?
Could you also let us know if this issue still occurs in the newest Launcher version?

This ticket will automatically reopen when you reply.

Issue still there. Video here: https://streamable.com/032ry0

Alternative video link (if the one above is expired): https://murena.io/s/tP8mQKEtin4gYya

Hi there!  

Could you answer few questions regarding this issue, it will help with the investigation:  

• Are you logged in in both Xbox app, MS store, and Launcher with the same MS account?  

• Have you tried signing out of all your Windows Apps, and the signing in again? 

• Is your Windows and associated apps (Xbox app, MS store) up-to-date (check for updates regardless)?  

• Do you have enough free space on your disc drive? 

• Have you tried installing the Launcher on a different drive? 

• Please also uninstall the Launcher, delete .minecraft folder (copy its content elsewhere before deletion) and then reinstall, restart your computer. Then please try to boot the Launcher. 

• Do you use VPN or any of the incompatible software on machine you try to log-in?   

• Could you provide us with more in-depth repro steps?  

This ticket will automatically reopen when you reply. 

#1 I only have/use Minecraft launcher

#2 I have no such apps

#3 I have no Windows OS in use and thus also no such apps

#4 Free disk space is roughly 850 GiB

#5 No, however the laptop device has only on physical drive, I could try to use a USB-pendrive?

#6 will do so and report back later

#7 No VPN used, no software from the referenceed “incompatible software” list is in place/use

#8 see video above, install launcher on Linux, log in, all works, restart launcher → error

Tried as suggested in #6 to no avail

Hi there!

We do not have enough information to find the cause of this issue.

Please attach the full launcher log found in minecraft/launcher_log.txt.

_{This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

requested log rom a failed start attenpt + close after error message is shown: https://pastebin.com/raw/75Nc77rK

I’m facing the same issue now…

Any news? Issue persists, workaround is a very lengthy procedure...

this issue still persist… since mar/12 til sept/09 and beyond

Can anyone still running into this please upload your launcher_log.txt file? This is a standard need for any triage requests.

Please find the launcher_log.txt file from this location on your PC: %appdata%\.minecraft

@Donuts1000 I posted the Log here already on “24/Jul/25 12:16 PM”

Try this:

• Clear Launcher Cache Delete the .minecraft/webcache2 folder to reset the Chromium UI cache.

• Also consider removing .minecraft/launcher_prefs.json and .minecraft/launcher_profiles.json to force regeneration.

@Donuts1000 Thanks a million!

Actually a simple rm -rf ~/.minecraft/webcache2/does the trick and in contrast to deleting the whole ~/.minecraft folder (which was my current workaround) that is much better because there is no need to re-login and re-download the full 500-600MB each time!

Still the problem exists, a second start in row while keeping the ẁebchache2 folder fails each time.

Same here on KDE neon 22.04 6.2

Hello. I encountered the same bug. The login attempt ends with a "whoops" error. I get an Xbox window where I select my account, and it gets stuck for almost a minute before the error.

Moreover, cleaning the specified folders isn't enough; I literally have to perform a clean install every time to log in. Killing the processes with PKILL -9 isn't enough either; I have to reboot the system.

After a successful login, when I restart the launcher, the launcher forgets about the login. I suspect the launcher is malfunctioning on KDE with the wallet disabled. I haven't encountered such problems on another Arch but DE "Cinnamon" installation.

I have been having the exact same issue on Linux: MCL-26160

@[MCQA] Zgajak i know that webcache2 to is what is causing the issue on Linux at the least

Is that enough info to fix it?

P.S, shouldn’t my bug report be added to the duplicate list?

@[MCQA] Zgajak?

@Zgajak

I have uploaded a launcher log

@KuKar you asked for a launcher log

There it is

@[MCQA] Blawik

MCL-24881 And here is yet ANOTHER report mentioning the same issue

@[MOD] Greymagic27 You might want to add it to the list of duplicates, if you haven’t already, or contact somebody who can

Those 2 issues are being tracked in different reports as they describe different things

oh

…. Wait, How are those two different issues? I tried opening the launcher on Linux, and it went “'Whoops! An unexpected issue occurred; we are sorry for the inconvenience. Please try restarting your Launcher. If that does not resolve the issue, please log a bug report here!” which is the exact same issue that these two reports detail, more or less. Sure i might have paraphrased a little, but the reports both ultimately say the same thing (that the launcher won’t open properly on Linux. And this bug report, lists Linux as one of the affected versions. And the comments of the reports that have them, tend to point out that Webcache2 seems to be causing the issue) So how exactly do they describe different things? from what i can tell they seem to be describing the same issue.

And then there is this report! MCL-26170

@[MCQA] Blawik If it is not too much of an hassle, I would like you to read my comments, i have some info that you might find useful.

Also, just looked, it seems that even more people are having the “'Whoops! An unexpected issue occurred; we are sorry for the inconvenience. Please try restarting your Launcher. If that does not resolve the issue, please log a bug report here!” problem

@[MCQA] Blawik ?

You asked for info, right?

@[MCQA] Blawik

@Mojira Modification Automation Can somebody PLEASE take a look at my comments? i have info that you will probably find info!

@[MCQA] Blawik

@ multiple times, and still no response.

@[MOD] Greymagic27 I believe I have made my rebuttal quite clear. So tell me, how are the other two reports describing two different things?

Hi. This report is describing an issue with the launcher showing the ‘oops an error occured’ message whilst MCL-24881 is about this error:

[13136:13170:0228/145918.196528:ERROR:cast_crl.cc(443)] CRL - Verification failed. terminate called after throwing an instance of 'std::bad_function_call' what(): bad_function_call

Both of these reports are logged internally so if it turns out it’s the same course, then they may be merged at that point, but currently they seem like two different issues

…..

Where is that info recorded?

I have uploaded a launcher log (not sure if it has the info that you are looking for) in one of my previous comments on this very report (and also on my own)

I would really appreciate if the launcher log I uploaded at least gets looked at (if it’s not the one that contains the data you would need to determine the verdict, then you might need to tell me what file to look for) @[MOD] Greymagic27

Here’s another log, if you need a different one, just tell me which one you actually need (Assuming the one first uploaded was the wrong one, of course.)

@[MOD] Greymagic27 You might want to see this