*My Minecraft version is 1.14.41. I could not find it under the "Affects Version" so I selected Future Release. I am aware of the other issue titled "There Was A Problem Loading This World" but it was not helpful since I am on PS4.
The issue I am having is that when I try to open my world, the game will freeze for a few minutes. Then, a message will pop up saying, "There Was A Problem Loading This World" and I can only return to the title screen. Unfortunately, I had just backed my world up to cloud storage right before this happened, So I cannot revert to an old backup (except for an old backup on a USB drive that was done about a month ago)
Before this started happening, I exited the game as I usually do. I closed Minecraft once the world was done saving, and backed it up. Nothing out of the ordinary. A few hours later, I came back and tried launching the world and got the error message. I deleted the world and downloaded the backup. Still not working. I turned off the texture pack and tried again to no avail. This issue is only happening to this world, and not any of my other ones.
I also tried making a copy of the world to see if that would change anything. When I did, I could see in the picture that appears next to the world name that I was in a different place than in the picture of the original world. The world size also went up to 1019mb (around 300mb larger than the original world). When I would try launching the world, it would say it's corrupt.
This is the first time this issue has happened in the 2 years of having this MC world. I updated to 1.14.41 on March 3rd and this problem began on March 8th.
Linked issues
Comments


This just happened to my world last night. Almost the exact same story right down to accidentally uploading the corrupt backup. Also, my last usb backup is from February 11. My error message went straight to "corruption" tho.
I wanted to take a break from building to have a snack so I saved and quit. Everything seemed perfect so I made an online psn backup and went about my business. I came back later to the world not loading. I disabled my texture pack too just to be safe but it still wouldn't load. It would give me pink and black squares instead of the loading screen and then crash. After trying and crashing a few times I started to consistently get "disconnected due to world corruption." Of course the backup I made is corrupt also and follows the same pattern. My most recent viable backup is from 2 months ago. This just started with 1.14.41. Maybe in trying to fix the crash while saving and quitting (which still happens a lot) it now adds a chance to corrupt your world? How's that for a "surprise mechanic" EA?
Losing progress like this is upsetting and we have no way of knowing if this is a one-off or a brand new ps4 bug that will keep happening, as this never happened prior to 1.14.41. This isn't the first time I've experienced game breaking bugs like this with bedrock. You can tell people to make multiple backups but what this really boils down to is that the game is very broken for a lot of people. It should not corrupt your save file from simply closing the game, and in the correct way. This is the only game I have ever owned that comes with this much game breaking risk. No other video game does this. Fix your game Mojang!

I Just had the same issue with my survival world. I also had an issue similar to this about 2 weeks ago and blamed it as a one off. i do make copies once a week but that can be a lot of progress and will often avoid turning the game on for a couple days😞 out of frustration. I hope there is a fix for this soon because it can be painful moment for people when starting up their system

I Just had the same issue with my survival world. I also had an issue similar to this about 2 weeks ago and blamed it as a one off. i do make copies once a week but that can be a lot of progress and will often avoid turning the game on for a couple days😞 out of frustration. I hope there is a fix for this soon because it can be painful moment for people when starting up their system

Any staff able to help with this issue?

Any staff able to help with this issue?

It has been a while since this report has been updated. Can anyone confirm that this is still an issue?

It has been a while since this report has been updated. Can anyone confirm that this is still an issue?

Yes, it is.

Yes, it is.

That's great! Have you found a way to reproduce this issue? Otherwise, it will be hard for the developers to fix it as well.

That's great! Have you found a way to reproduce this issue? Otherwise, it will be hard for the developers to fix it as well.

I myself havent had this happen again, mostly because i have barely played since this happened. But i do remember that when I logged off before backing up, i had alot of shulker boxes in my inventory, all filled with items. Is it possible that could have caused the save to corrupt? Also, is there any way to possibly repair this world?

I myself havent had this happen again, mostly because i have barely played since this happened. But i do remember that when I logged off before backing up, i had alot of shulker boxes in my inventory, all filled with items. Is it possible that could have caused the save to corrupt? Also, is there any way to possibly repair this world?

No worries if your world got corrupted. Minecraft Bedrock has a special system built in that slowly fixes corrupted worlds every time it's been opened. Eventually, the game will revert back so many times that your world will be fixed. So, in theory, keep opening your world until it opens. I got this tip from Helen Angel.

No worries if your world got corrupted. Minecraft Bedrock has a special system built in that slowly fixes corrupted worlds every time it's been opened. Eventually, the game will revert back so many times that your world will be fixed. So, in theory, keep opening your world until it opens. I got this tip from Helen Angel.

I am currently trying that and all that happens now is minecraft crashes and i get error code CE-34878-0

I am currently trying that and all that happens now is minecraft crashes and i get error code CE-34878-0

Had this issue last night on PS4. Been playing the world for about 6 months no issues. The longer weve played the longer it seems to take to save but it does always save. The interesting thing before what now seems like a corrupt world was that in the last Save and Quit it saved in about 2 seconds. Seemed odd but thought nothing of it. Now when I try to go into the world there is no loading bar and after about 5 minutes I get the "there was a problem loading this world".
The only thing I could think to try was copy world. That worked but when I try to access the copied world the game blue screens almost instantly. Bad times.
Euwills comment is interesting if that's true I guess I'll just keep accessing the world every so often see if it rights itself. Otherwise I guess game over. The only other thing I was thinking was getting the save files off the PS4 onto a PC and trying some of the online video steps on PC?

Had this issue last night on PS4. Been playing the world for about 6 months no issues. The longer weve played the longer it seems to take to save but it does always save. The interesting thing before what now seems like a corrupt world was that in the last Save and Quit it saved in about 2 seconds. Seemed odd but thought nothing of it. Now when I try to go into the world there is no loading bar and after about 5 minutes I get the "there was a problem loading this world".
The only thing I could think to try was copy world. That worked but when I try to access the copied world the game blue screens almost instantly. Bad times.
Euwills comment is interesting if that's true I guess I'll just keep accessing the world every so often see if it rights itself. Otherwise I guess game over. The only other thing I was thinking was getting the save files off the PS4 onto a PC and trying some of the online video steps on PC?

This problem is still existing for me and the world will not launch. My game is updated to the current version and the launching the world over and over again has done nothing.

This problem is still existing for me and the world will not launch. My game is updated to the current version and the launching the world over and over again has done nothing.

I'm having the same issue. My world is over a year old, last week I had an error message when trying to load the world that said "there was a problem loading this world". Super annoying. Don't want to start over now. Need a fix for this.

I'm having the same issue. My world is over a year old, last week I had an error message when trying to load the world that said "there was a problem loading this world". Super annoying. Don't want to start over now. Need a fix for this.

Just wanted to add my 8 month old world to this list also having this issue. I've been repeatedly attempting to open the world as suggested but this has not worked yet. First time this occurred we were about 15k blocks out from spawn looking for a woodland mansion (which ended up being around 22k blocks from spawn). I loaded an earlier backup and we were able to continue. however after returning to the spawn area this occurred again. Again having to return to an older copy and losing progress. Hope this is something Mojang will be addressing in the near future.

Just wanted to add my 8 month old world to this list also having this issue. I've been repeatedly attempting to open the world as suggested but this has not worked yet. First time this occurred we were about 15k blocks out from spawn looking for a woodland mansion (which ended up being around 22k blocks from spawn). I loaded an earlier backup and we were able to continue. however after returning to the spawn area this occurred again. Again having to return to an older copy and losing progress. Hope this is something Mojang will be addressing in the near future.

Just want to add that our year (ish) old world keeps doing this. Each time we go back to the most recent back up and it works fine for a couple of days, but then refuses to load again, so need to go back to the same back up.
At this point, we've mined out the same 50 x 2 x 50 block area three times and we're pretty close to just giving up on it entirely.

Just want to add that our year (ish) old world keeps doing this. Each time we go back to the most recent back up and it works fine for a couple of days, but then refuses to load again, so need to go back to the same back up.
At this point, we've mined out the same 50 x 2 x 50 block area three times and we're pretty close to just giving up on it entirely.

Interesting you should say you've been getting it after mining a large area as we'd done this on the world that crashed also.
Additionally I've noticed recently on a new world that after digging out a large 30ishx20x20 area crashes have started to happen. I assume it just cant handle certain levels of change on the save file on PS4.

Interesting you should say you've been getting it after mining a large area as we'd done this on the world that crashed also.
Additionally I've noticed recently on a new world that after digging out a large 30ishx20x20 area crashes have started to happen. I assume it just cant handle certain levels of change on the save file on PS4.

On what version do you experience the issue now?

On what version do you experience the issue now?

I lost a world to this in version 1.16.000, the world is still unusable now in 1.16.4 with the same error, "there was a problem loading this world." This is on PS4.

I lost a world to this in version 1.16.000, the world is still unusable now in 1.16.4 with the same error, "there was a problem loading this world." This is on PS4.

Update: was playing on a friend's world yesterday, PS4 and version 1.17.2. The game then kicked us both back to the menu with a message about the file suddenly being corrupted, and now he is also getting the "there was a problem" message, making the world unplayable. For both of us this has happened when the file size has exceeded 1gb, but not immediately after doing so and not during exploration of new areas. The world spontaneously corrupting while we were playing was new, mine had just started showing this error on loading one day.

Update: was playing on a friend's world yesterday, PS4 and version 1.17.2. The game then kicked us both back to the menu with a message about the file suddenly being corrupted, and now he is also getting the "there was a problem" message, making the world unplayable. For both of us this has happened when the file size has exceeded 1gb, but not immediately after doing so and not during exploration of new areas. The world spontaneously corrupting while we were playing was new, mine had just started showing this error on loading one day.

We have been tracking this issue at MCPE-117062 for all devices. If anyone can provide a copy of an affected world on that ticket it would be helpful.

We have been tracking this issue at MCPE-117062 for all devices. If anyone can provide a copy of an affected world on that ticket it would be helpful.
This just happened to my world last night. Almost the exact same story right down to accidentally uploading the corrupt backup. Also, my last usb backup is from February 11. My error message went straight to "corruption" tho.
I wanted to take a break from building to have a snack so I saved and quit. Everything seemed perfect so I made an online psn backup and went about my business. I came back later to the world not loading. I disabled my texture pack too just to be safe but it still wouldn't load. It would give me pink and black squares instead of the loading screen and then crash. After trying and crashing a few times I started to consistently get "disconnected due to world corruption." Of course the backup I made is corrupt also and follows the same pattern. My most recent viable backup is from 2 months ago. This just started with 1.14.41. Maybe in trying to fix the crash while saving and quitting (which still happens a lot) it now adds a chance to corrupt your world? How's that for a "surprise mechanic" EA?
Losing progress like this is upsetting and we have no way of knowing if this is a one-off or a brand new ps4 bug that will keep happening, as this never happened prior to 1.14.41. This isn't the first time I've experienced game breaking bugs like this with bedrock. You can tell people to make multiple backups but what this really boils down to is that the game is very broken for a lot of people. It should not corrupt your save file from simply closing the game, and in the correct way. This is the only game I have ever owned that comes with this much game breaking risk. No other video game does this. Fix your game Mojang!