Hi, I have an issue with Minecraft Windows 10 edition where I crash instantly on the mojang logo screen.
Sometimes I see the title Screen and it says
Global Resources caused a Crash
Global Resources have been reset.
Then it Crashes Again.
Could someone help?
Related issues
duplicates
Comments
migrated
migrated
I've Also had this issue in 0.15.0
[Mod] Celesian
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-19364
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
migrated
... "Resolved?" You didnt even tell me how to fix the Crash..
[Mojang] Mega_Spud (Jay)
The "Resolution" is that this is a duplicate of an earlier ticket, which is still open.
For game help or community support you might like to follow one of the links below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
migrated
Same here, can someone please help? I just enabled Minecraft Realms and it is a bummer not being able to play. >:v
migrated
Hey MCPE mods... please re read this request for help carefully. This one DOES NOT involve the user playing with global resources causing a reset like the one you linked when prematurely closing this thread, it involves a straight out full crash of the app in which the only message seen is Global Resources Reset, A Crash Was Detected.
Completely DIFFERENT problem, one that is happening to me as well and I DO NOT play with any resource packs or reset anything, so far I am seeing it as a full bug or glitch where I NEED or am FORCED to be connected to the internet to play it???? The fact no one from Mojang, Microsoft or whoever is listening properly and addressing these issues (and I have read quite a few) tells me that maybe we should all band together as unhappy users and DEMAND our money back for an inferior working game. Perhaps then the developers will stop prematurely closing threads for whatever excuse they think of and actually look into what is causing this issue.
This also happens on 1.0.1