mojira.dev
MCPE-236811

26.3 Crashes During Startup - Game Unplayable

After updating to v26.3 the game is unplayable due to a crash that happens during the startup/launch sequence.
DO NOT MARK THIS AS AN INVALID ISSUE. THE GAME IN ITS ENTIRETY IS UNPLAYABLE.

Linked issues

Attachments

Comments 11

Hi!
Thank you for your report! 

Could you answer some questions regarding this issue?

  • Can you record a video of the issue and upload it?

  • Are you using any modifications or texture packs?

  • Have you tried reinstalling the launcher and the Minecraft game? (Remember to create backup files before doing so.)

  • Could you please include details about your device and system specifications (RAM, CPU, GPU)?

  • Are there any background processes or applications running that might interfere with the game's performance?

Thanks!

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

This is what happens.
Even when I opened the game on 26.2 and the 26.3 update automatically installed, the same crash sequence happened.

CPU: Intel Core i7 10th Generation
GPU: Nvidia G-Force RTX

Also, I’m using the standalone version of Bedrock which doesn’t require the MC Launcher.
Forgot to put that in the original report so I’m adding it here.

I have the same probleme and it is not fixed i tried to create a backup file but nothing worked so now i cant reinstall it

Same issue exactly. Mine seems to fail a bit quicker, but it’s the same result.

All drivers, etc. are up to date. Tried a Minecraft for Windows “reset”. Reset the Microsoft Store. Rebooted PC. Nothing has helped.

The game is completely unplayable because it will not even open.

I just wanted to note that I am trying to open the Bedrock version from the Minecraft Launcher.

1 more comments

For me, 26.1 caused a “can launch but cannot open a world” issue → unplayable. 26.2 fixed the “cannot open a world” issue → playable. 26.3 caused a “cannot even launch” issue → unplayable. Frustrating is right. I am close to giving up on Bedrock entirely.

@UpTheDubsGuy I have had the same exact problem. Might as well wait for 26.4…

Yeah at this point I’m just waiting for 26.4 too..

Just like you said @UpTheDubsGuy, my game doesn’t even launch anymore.

Day 8 without Minecraft 😟

What do you need?

Errorlog:

Fehlerhafter Anwendungsname: Minecraft.Windows.exe, Version: 1.26.3.1, Zeitstempel: 0x69a0e1aa

Fehlerhafter Modulname: Minecraft.Windows.exe, Version: 1.26.3.1, Zeitstempel: 0x69a0e1aa

Ausnahmecode: 0xc0000005

Fehleroffset: 0x0000000000006823

Fehlerhafte Prozess-ID: 0x638C

Fehlerhafte Anwendungsstartzeit: 0x1DCB3AC85866EFD

Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\MICROSOFT.MINECRAFTUWP_1.26.301.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe

Fehlerhafter Modulpfad: C:\Program Files\WindowsApps\MICROSOFT.MINECRAFTUWP_1.26.301.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe

Berichts-ID: 7eacb39a-f730-444e-b4a1-dcdef460a84b

Vollständiger Name des fehlerhaften Pakets: MICROSOFT.MINECRAFTUWP_1.26.301.0_x64__8wekyb3d8bbwe

Fehlerhafte paketbezogene Anwendungs-ID: Game

Fehlerbucket 1289894785619315268, Typ 5

Ereignisname: MoAppCrash

Antwort: Nicht verfügbar

CAB-Datei-ID: 0

Problemsignatur:

P1: MICROSOFT.MINECRAFTUWP_1.26.301.0_x64__8wekyb3d8bbwe

P2: praid:Game

P3: 1.26.3.1

P4: 69a0e1aa

P5: Minecraft.Windows.exe

P6: 1.26.3.1

P7: 69a0e1aa

P8: c0000005

P9: 0000000000006823

P10:

Angefügte Dateien:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9d1ea352-984a-4888-bb38-e503b59ad5d7.tmp.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f89c2a59-f372-46b5-bcb3-56d70d259048.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d6862209-9e5a-434a-80f5-a85b9dc03a7f.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.32113307-7837-451e-ab2c-b49533446e6c.tmp.txt

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d67d0433-0e6c-437e-a8ba-bf50f9e8a1fc.tmp.xml

Diese Dateien befinden sich möglicherweise hier:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MICROSOFT.MINECR_27cf6852b2f0598d506460d42b1151873d5495_ac3fd90a_8362603c-650b-4868-aa35-72de89e182f9

Analysesymbol:

Es wird erneut nach einer Lösung gesucht: 0

Berichts-ID: 7eacb39a-f730-444e-b4a1-dcdef460a84b

Berichtstatus: 268435456

Bucket mit Hash: dd7195205a08982571e6a0792e77ca44

CAB-Datei-Guid: 0

108CAM

(Unassigned)

1548642

Confirmed

Windows

26.3

Retrieved