Launcher crashes on macOS - nativeUpdater quit unexpectedly

sigue el problema igual

AI_Burtle go to https://www.minecraft.net/en-us/download and download it there. However, do not let it update the second time or else it will be bugged again.

thanks

I followed instructions from Turbo, but I'm loosing all my config and existing worlds doing this. When I try to copy it back from older `minecraft` folder, then it's broken again. I would need some instructions about files which need to be copied back after this operation. But now I cannot play MineCraft at all. I have this issue on both my iMac and MacBook. Where only one of them uses mods and shaders. Second one is used only to play with original settings. But both are affected.

Hi again! You can get your worlds back by copying "saves" from the backup folder into the new minecraft folder.

How do I make the launcher not update on startup? Please help. It will be bugged again if it does. Is this update 2.4.4 stopped server side yet?

It is happening the same for me. launcher stops suddenly. I'm running minecraft in imac 24" with mac os Ventura 13.2.1

I tried to download again the launcher from the minecraft page but the problem keeps... I don't know what to do...

Same issue, I deleted the minecraft folder, uninstalled the launcher and then downloaded it again and when reloaded the same problem happens and I can't find the minecraft folder after the last install

Is there any update on this issue? Experiencing the same problem. Deleting Minecraft installation and app and reinstalling fixes temporarily but upon closing the game and relaunching the launcher update bug persists. It begins to download an update then crashes without error message.

@[Helper] turbo can you please mark it as confirmed? I really need this problem fixed because reinstalling the launcher isn't a permanent fix as when I open it the second time it is updating to the bugged version again. Also this problem happens on apple silicon.

I am having the same issues but in a PC with Windows 8.1. Vanilla Minecraft, without mods.

Action https://redstone-launcher.mojang.com/release/v2/objects/5cc0c762f4d271154ec17d8a3cd60f481e215ec5/libcef.dll failed in response handler. response code: 200 - error string: 'transfer closed with 137371192 bytes remaining to read
[Error: 2023-03-25 16:37:50.1572686: Updating.cpp(354)] Download of https://redstone-launcher.mojang.com/release/v2/objects/5cc0c762f4d271154ec17d8a3cd60f481e215ec5/libcef.dll failed.
[Error: 2023-03-25 16:37:50.1573479: Updating.cpp(354)] Download of https://redstone-launcher.mojang.com/release/v2/objects/2b8ccc04c8f204af7a12a59f663abf005c72346d/allaytwirl.zip failed.
[Error: 2023-03-25 16:37:50.1575114: Updating.cpp(365)] Some downloads failed, update will not proceed.

Unstalling MinecraftLauncher and deleting .minecraft folder works, but only once. The second time Launcher tries to update and fails again.

The workaround is editing the game/.version file and writing 2.4.4, so the launcher do not try to update anymore.

Hello, have you tried using the minecraft launcher using offline mode / without wifi? it worked for me, i had the same issue yesterday but when i did this trick it worked.

Reminder: use the vote button if you experienced this issue, not just writing comment. I have been told it is easier for the bug tracker moderators like that means you can get your Minecraft Java back faster.

Hi all,

We're actively investigating this issue on a few fronts to try and get a consistent repro. We believe we have a fix for the actual crash that's going through testing now, but we're still working on some investigation for what is causing it to get into the state to cause that crash. 

For those still hitting this issue, can you provide the following information?

1. An updated log (specifically nativeLauncherLog.txt and nativeLauncherLog-0.txt) after running the launcher and experiencing the issue.
2. When using the workaround to get into the launcher, are you seeing any other odd behaviors? Specific callouts would be issues downloading Java versions or news items not loading? If so, please provide launcher_log.txt and launcher_log0.txt when you hit those issues in addition to the above. 
3. If using a VPN, does toggling that on/off or using a different VPN region cause any different behavior? If toggling these settings changes anything, please let us know the VPN you're using and the region targeted that was having issues.

After reading SeaLocust's comment I downloaded Minecraft again from the "Minecraft Alternative Downloads" link and suddenly it works. 

I can log into Minecraft without problems.  (tested, singleplayer, multiplayer  and apparently it works correctly)

I still can't locate the "minecraft" folder that I deleted following the instructions in the email if I look for it in the library (or hidden folders), but the game works. I think it must be something that happens in the installation

My last error log is from the 24th, if you need it I will upload it

Hello, I am using an Intel i5-4440 with 8 GB of RAM and Windows 8.1. Vanilla Minecraft without mods and Legacy Launcher. No VPN or anything uncommon.

When i run MinecraftLauncher it begins updating and then it gives the error "Error al actualizar el lanzador nativo de Minecraft", that I think is the same as "Unable to update the Minecraft Launcher".

I ran it twice an got the same error. Here are the logs:

I can not find the nativeUpdaterLog.txt

If I change the game/,version to 2.4.4 then it does not try to update and I can play without problems.

[Info: 2023-03-31 17:59:13.2439280: NativeUpdaterWin32.cpp(277)] 31-03-2023 19:59:13 - going to update minecraft.exe using minecraft.exe.tmp
[Info: 2023-03-31 17:59:13.2448284: NativeUpdaterWin32.cpp(279)] Launcher is definitely closed.
[Info: 2023-03-31 17:59:13.2448557: NativeUpdaterWin32.cpp(123)] Backing up previous version of the launcher...
[Info: 2023-03-31 17:59:13.2451787: NativeUpdaterWin32.cpp(144)] Previous version has been backed up as minecraft.exe.backup.
[Info: 2023-03-31 17:59:13.2452046: NativeUpdaterWin32.cpp(151)] Installing new version of the launcher...
[Info: 2023-03-31 17:59:13.2455470: NativeUpdaterWin32.cpp(159)] Moved minecraft.exe.tmp to minecraft.exe successfully.
[Info: 2023-03-31 17:59:13.2456430: NativeUpdaterWin32.cpp(161)] Removing backup file minecraft.exe.backup
[Error: 2023-03-31 17:59:13.2457187: NativeUpdaterWin32.cpp(164)] 5, going for attempt 2...
[Info: 2023-03-31 17:59:14.2566789: NativeUpdaterWin32.cpp(168)] Removed backup minecraft.exe.backup successfully.
[Info: 2023-03-31 17:59:14.2567259: NativeUpdaterWin32.cpp(306)] Update succeeded!

[Info: 2023-03-31 17:59:13.2147834: LaunchApplicationWin32.cpp(37)] Started application tools\NativeUpdater.exe minecraft.exe minecraft.exe.tmp --workDir C:\Users\FuryNocturn\curseforge\minecraft\Install
[Info: 2023-03-31 17:59:13.2148140: NetQueue.cpp(212)] NetQueue: Initiating shutdown.
[Info: 2023-03-31 17:59:13.2148340: NetQueue.cpp(226)] NetQueue: Waiting for worker thread to finish...
[Info: 2023-03-31 17:59:13.2148657: NetQueue.cpp(742)] NetQueue: Worker thread shutting down.
[Info: 2023-03-31 17:59:13.2156865: NetQueue.cpp(229)] NetQueue: Done.

I have to use the translator because I'm not good at the language.
I wanted to add that I've been trying to delete and reload all afternoon. and every time the same error. but when i delete the folders versions and webcache2.
I have closed the game and opened it 10 times and no error was generated.
I have been repaired.
If those folders are the ones with the error, you can look around.

I think that this issue has been fixed. I can play again.

It is an issue for both myself and my son, on 2 different MacBooks. We even tried my wife's and it doesn't work there either, so 3 different computers where it had worked and now doesn't.

@unknown :  Please reach out to Mojang Support (https://aka.ms/Minecraft-Support) so we can look into your issue more deeply. 

Hi!

Does this issue still occur to anybody after the last update?

I am still having the issue on MacOS

Hi!

Have you contacted Mojang Support (https://aka.ms/Minecraft-Support) ?

As per this comment by @unknown, this issue should be resolved now. Is this still occurring for anyone?

This is still an issue for me.
I had to switch to Lunar Client.

macOS Monterey v12.7.3