mojira.dev
MCPE-158591

All worlds report "there was a problem loading this world".

This issue is very similar to MCPE-149193 except I am unable to load any of my worlds regardless of file size. This issue affected me on my ps5 and ps4
I have tested 10 different worlds every one of them had the same issue. Expected result. The world loads properly and is able to be played.  Current result. The world trys to load for 50 seconds then displays the attached screen shot. I have tried everything that I know to do. I have Uninstalled the game and cleared the cache. Update. I wouldn't say this issue is fully resolved however most of my world do work again! Large worlds are still giving me problems every now and then. Update2. This problem is still present  even after all this time. However, you can fix this issue (on windows) check the pinned comment. However, mojang should fix this for those who can't afford minecraft realms/don't want to pay to move there world to a pc to fix it. Or those of you that don't have a pc/laptop!

Linked issues

Attachments

Comments 5

All_Out_Savage

1.19.10 has made this issue change. I am now able to load smaller worlds (under 500 mb) it seems  the issue that effected playstation in 1.18/1.18.1 has come back the exact same way it was in https://bugs.mojang.com/browse/MCPE-149193 I have attached new screenshots 

All_Out_Savage

This issue is not as bad as it was 2 months ago. I can load most of my worlds now. However after I exit the world, it can only be loaded one more time. The (There was a problem loading this world) message appears again. To counteract this I must make a backup of the world on a USB drive and re-download it on my console. I have to repeat this process every time I save and quit or the world is lost. This doesn't always work so I keep some backups on my computer 

All_Out_Savage

These 6 steps restored my world so I thought I would share the fix

 

 

 

1.If your world is on console you will need to buy a realm and download the world on a computer 

 

 

 

2to to C/Users/(you're username)/app data/local/Packages/Microsoft.minecraftUWP/localstate/games/Com.mojang/minecraft worlds/

 

 

 

3.Find your corrupted world, open it and find the db folder

 

 

 

4.Locate the MANIFEST-xxxxxx file and copy the name (not the file)

 

 

 

5.Open the CURRENT file with a text editor such as Notepad++

 

 

 

6.Delete everything in the file (not the file itself) and paste in MANIFEST-xxxxxx

Thank you for your report!
We're tracking this issue in MCPE-117062, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.

I just got this issue last night on PS5, was playing earlier fine, saved and since I've had problems with corrupted worlds in the past i save to the cloud every 3 days or so. Since it was about 3 days after saving my world no problems, I then saved manually to cloud storage but when i started it the world up again hours later I got the "there was a problem loading this world" message after about 1 min of loading in and the title screen seemed to freeze after the first 5 seconds. The green bar would not load at all during the minute and I have also tried downloading my save from the cloud with no luck. The thumbnail of the world still shows where i had logged out from and I came here hoping for any advise after trying many different recommendations from searching online.

All_Out_Savage

(Unassigned)

Unconfirmed

PlayStation

Corruption, GameBreaking, Unplayeble, WorldCorrupt

1.19.2 Hotfix, 1.19.10, 1.19.11 Hotfix, 1.19.20, 1.19.21 Hotfix, ..., 1.19.71, 1.19.73, 1.20.12 Hotfix, 1.20.13 Hotfix, 1.20.14 Hotfix

Retrieved