"There was a problem loading this world" for one world

A file sharing site like onedrive, Googledrive, mediafire, etc.

https://drive.google.com/file/d/1eC2JBHKtti-aS6NVIl1m0fSZzTX271TF/view?usp=sharing is this how i do it?

I imported the world and got the same message, "there was a problem loading this world," when I tried to load it. When I tried to open it in MCCToolchest I got a warning that worlds made from marketplace map templates cannot be opened in 3rd-party viewers in order to protect the intellectual property of the map creator.

Could the issue here be that the marketplace map template was purchased with a different account than the one you are logged in with when you try to open this world?

no, ive used the same account this whole time

I'm having this issue on xbox. It's happened with multiple worlds now. On each occurrence, the world file size seems to grow exponentially just before it fails. Regularly copying the file (before any issues) seems to reduce the file size to more normal sizes again for some reason

I am also having this problem on xbox. I can't load up my main world even after reinstalling minecraft, re-syncing my save files etc. I can open other worlds or start a new world but when I try to load my main world, I get the "there was a problem loading this world" message and can't open any other world afterwards so I have to quit the game completely.

About the file size, it's important to note that the file sizes shown in the world list have always changed in unpredictable ways. Apparently this is Working As Intended to some extent per MCPE-23462. However,

• There is a confirmed bug with how Minecraft detects file sizes and storage space: MCPE-32501.

• I have always found that when simply copying a world, the copy will show as much smaller than the original in the Minecraft worlds list. I have never compared what is shown to the actual disk space uses by the world folder, but I suspect there is a bug and the displayed world sizes are unreliable.

So I started a new world as it seems there is no easy quick fix and have run into the same problem again.

This time, minecraft crashed half way through loading the world and my xbox shutdown. Any attempt to load the new world leads to the same error message as above so I have now lost two worlds.

@GoldenHelmet

My new world has been working fine for several weeks now with no crashes as I have been regularly backing it up. Before I started this regular backing up of my worlds, crashed happened fairly frequently and I have lost 3 worlds already to this bug. It could be unrelated but seems to at least help reduce the frequency of the issue

I’ve had this issue but with almost all my worlds.

Is this ever going to be fixed? If so when? I’ve (and lots of others) have not been able to play our main worlds for nearly a month now and for some over a month... very boring in lockdown also...

I have this error, tried copying my world which gave the same file size (84.4mb - not massive), the file size hasn't changed but no matter what I do I can't get onto my main world - the only one I had before today because I only got minecraft 3 weeks ago!

If anyone else could provide a copy of an affected world that would be very helpful.

please find my world at the link (too heavy to attache the file here)

https://www.dropbox.com/s/o0t48p1h5wijlq3/Archivio.zip?dl=0 

as a side note I was able to have it work (saving at least once)  copying the file directly within the game (in the world options before launching the world). 

this workaround works if every time I play I first create a copy and then launch the game, but it is obviously not a sustainable way of managing the world

@Gennaro Galdo: I'm sorry but I cannot read or import the files you provided. What we need is a .mcworld file or a single world folder copied directly from the game files. On my iPhone I can find the world save folders with the files app in {{Minecraft\com.mojang\games\minecraftWorlds}}.

the file is taken from a PS4

My son is having the same issue on his xbox one, none of his saved worlds will open.  

We tried clearing xbox local storage, uninstalling / reinstalling, and hard reboot. 

I just attached a .mcworld file that has this issue

I imported Cooper Barnes world

and had the same experience that I did with sarah's world (see earlier comment).

In addition, after getting the "There was a problem loading this world" message, I am unable to open any worlds at all because clicking on them does nothing.

I can only open other worlds after closing and restarting Minecraft.

Is anyone experiencing this bug with a world that was not made using a marketplace world template?

The world I put in, "Beetroot Battles" is not a Market Place world template. Do you know if there would be any way to fix it??

Sorry, I have no workarounds. My guess is that some data in the world save is getting corrupted and that makes MCCToolchest think it is encrypted so it gives the message about marketplace maps.

There is another known issue where world save data gets corrupted: MCPE-50467. In that case it's isolatable to a specific variable in the ~local_player data apparently being altered by an overflow every time the world is saved or loaded. With this bug, it seems only developers would have the tools to analyze the world save to see what has happened.

I have a partially corrupted world that's giving this same error. GoldenHelmet's MCCToolChest is very likely going to misinterpret mine as a marketplace map.

Is there any possible way that I could get that world back or fixed or is it going to be broken forever.

To Barnes' new comment, I'm not sure why your Beetroot Battles world doesn't have the builds, because @unknown's world still has all their builds (or at least their house and small farm). I've also updated the instructions and tested both worlds with the new steps, same result.

Potential workaround

1. Backup your world, do it now

2. Open C:\Users\User\AppData\Local\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds or the location where your worlds are stored

3. Find your corrupted world, open it and open 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, save

7. Attempt to play your world again

Note that not all of the steps might be needed but this is the one thing that I tested.

(This was before I found the workaround)

I could open both OP's world and the Beetroot world using Universal Minecraft Editor, which does not have a marketplace map warning. The db data under View Files also does not seem to be expandable.
Both worlds did not show a ~local_player under the Players tab which is supposed to show up. Additionally, attempting to save any edits shows a popup saying that the world could not be saved, but reopening the editor seems to suggest that the save was in fact successful.

This lets me get into the world, however none of the builds are saved and nothing is saved.

I was able to confirm that the \db\CURRENT file in an affected world was in fact what was corrupted. However, in the case of Cooper's Beetroot Battles, there are additional corrupt files in the \db folder as listed:

000900.ldb

000901.ldb

000902.ldb

000903.ldb

For this, excessive patching may be required to recover the world

for people on console they can't fix any of that on there own, unless you guys make a way for them to get to the files of the game and fix it.

so since yesterdays 1.17.2 update on xbox ive lost 2 worlds due to this. My xbox has turnt off both times while trying to load my world. When i turn the console back on and load world i get this message. How can people on console get their worlds back?

ANFIELDARMY: XBox completely shutting down is tracked at MCPE-53665, but based on your comment and some of the comments on that ticket it sounds like these issue may overlap. What I mean is maybe this issue manifests as MCPE-53665 on the XBox One X / Series X.

@Cooper Barnes: If this is the main build in your Beetroot Battles world, then it is still there after using the workaround posted by Skajie.

I have run both sarah's world and

through MCBERepair's repair function, and it works just as well as Skajie's workaround to make the worlds playable again. It also gives output logs:

The logs show that the only corrupted files in "copy of handsome squidward" are 008277.log and the MANIFEST, but "beetroot battles" has several corrupted files.

will there be a way for you to automatically input that into console worlds to make them work again?

also with the repair function does it keep everything in the world?

Jarod Colbourne: the only way to view or modify a world from a console would be to transfer the world to a realm, then download it from the realm to a PC. For help with the mcberepair tool you can ask it's creator on the Analyzing Minecraft Discord, but please understand he and the tool are not affiliated or endorsed by Mojang or the bug tracker, so use it at your own risk. What the tool can save from a world depends on what data has been corrupted.

So you are still working on this bug and their may not be a fix for a little longer?

Jarod Colbourne: The Helpers and Moderators on the bug tracker are volunteers. We do not work for Mojang and we do not have access to the developers' their internal priorities and updates. Once we confirm a bug it gets forwarded to their internal tracker. I was adding my findings to the ticket in hopes that it will help them in their research into the cause and possible fixes for the problem.

Do you guys report these serious bugs to the team at mojang or is it just you guys working on resolving this issue on your own time?

We've been having this issue on our PS4 since the 1.17 update and haven't been able to get back into the world since.

Since we had this issue after 1.16, but fixed it with an uninstall reinstall, then had it again at some point and fixed it by going back in our saves, we tried both of those. Neither seems to be working this time, though.

Jarod Colbourne: Yes, bugs reported here are forwarded to the Mojang devlopers, usually soon after a moderator updates the "Confirmation Status" to "Confirmed" or "Community Consensus." You can tell that a report is tracked internally by Mojang when it has a number in the "ADO" field.

You can find answers to other questions in the Bug Tracker FAQ.

I just got this problem on a 1.3GB world on PS4.  I tried many times and always get that error message.

So I tried loading a backup of 3 days before.  It worked and we played for a few days but then yesterday I got the same problem with it.  It was working fine and was saved properly. 

If I knew there was a size limit, I would not have spent so many hours making maps just to find a jungle. 😞

Me and my son played this world for 6 months.   Very disappointing...

Seems there is a duplicate MCPE-64999.  Perhaps the 'votes' can be combined to make it a higher priority bug?

Thanks for mentioning the duplicate. I have linked it to this ticket.

Comments on MCPE-64999 suggest that the corruption and/or inability to load the world could be related to mining out large areas (e.g. 50x20x50) or having a lot of full shulker boxes in the player inventory.

Sem Looij: you can see that a report is tracked internally by Mojang when there is a number in the ADO field in the report header.

On my world, I had been building something the previous day. No shulker boxes, and no large mining areas. The next day I tried to open the world and got the error. I believe I still have that world backed up in cloud storage, if so I'll try to upload a copy. 

Jared Colbourne: your comments are being removed because they do not add new information relevant to reproducing or fixing the bug.

This is a bug tracker, not a support site. Usually the only update here from Mojang would be if they announce a fix in a changelog. Feedback and suggestions should be directed to feedback.Minecraft.net or to a Mojang community manager on Twitter. For discussion about bugs and to ask questions about the bug tracker use the Mojira Discord.

I am currently working to identify specifics on this issue on my PS5 and a PS4. It appears the bug is in the minecraft world save file generated by the application. Once the minecraft save file is over 1G two save files are generated. Once created these two save files work one time for loading and appear to save properly when exiting the world however will not load the next time and will generate a "there was a problem loading this world" and take you back to the main screen. Request developers fix this bug as a priority and include in the next update.

Was also having this issue on MCPE on latest Android on Samsung S20. Tried reinstalling, clearing cache etc. Can confirm copying the MANIFEST-XXXX filename into the CURRENT txt/db file (which was empty) solved my issue too. Thanks for the solution!!

I read through the comments on this as well as the Xbox series X crashing when loading up Minecraft worlds thread. This issue has happened for a long time now on the other related thread. Any news on a fix that will be coming out for those affected on the series x? the only difference with my situation for me is that I made a support post and used their troubleshooting advice. The thing that worked was deleting the saved data from my console and then reloading Minecraft. Eventually that stopped working with the Xbox crashes and moved onto the” there was a problem loading this world” and so I made a new world. This today just crashed that new world and my Xbox series x and when loading Minecraft back up and doing any further troubleshooting or updating it now just says “there was a problem loading this world” and it won’t let me play either world anymore and probably won’t let any Xbox series x minecrafters play successfully until this is fixed.  Is this issue going to be resolved when 1.18 comes out? Do we know if these worlds will eventually be recoverable for people on the new console? Because if not it would be greatly appreciated if someone could let us know so the series x community stops wasting their time making worlds that will eventually be unplayable with this error process. 

News from PS5 side on this exact issue...my 4 yo (2 files 900+ & 400+ mb) world just got into "strange mode"...I try to be safe and backup both cloud and usb, every other save to different place...so recently I got my world corrupted (happens a lot thus those safety measures), than i loaded backup from the cloud and played for some time with no issue, saved the game, closed app, backup done on usb this time, went to sleep...next day got the "There was a problem,.." when opening this safetly saved world...loaded backup from usb...still the same issue...loaded backup from cloud...world loaded and I could play...so I played, saved the world, closed the app, backup done to usb again this time, went to sleep...next day there was no issue playing during several sessions, and when I was done saved the backup to cloud...next day got the "There was a problem,.."...and here when it gets STRANGE...loaded backup from cloud...still the same issue, loaded backup from usb...got it but after multiple atempts I am not able now to get proper save of this world. Everytime after save when coming back I have "The problem", the save on usb seems to be good enough to open each time but fails to be saved...so I got my pefert world in status where I can play it but will not get any progress saved...strange state, isn't it? 😞  I tried all soft reset options, clearing cache+,+ reinstalations etc, tried to save game on different scenarios...each time not succesfull to reopen. Got a Schrodinger's world...both corrupted and good at the same time.

I was really hoping that there will be a way to recover my world or at least keep all this from happening, but seeing a February bug report still not being close to being solved, I'm kind of losing faith. Basically what I see from this is that the game is currently unplayable for me and probably will be for a long time. I don't want to make my world over and over and over again to get to the same point of losing it.

Mine got corrupted by closing the game the usual way, through Save & Quit. It all went the same way as usual, but when I came back to the world, it didn't let me in anymore. I've tried some troubleshooting I found online, like reinstalling, force close of the game and many more, but nothing helped me recover my world.

Edit - It is happening for me since 1.17, Samsung Galaxy Tab S6 Lite, Android 11. Running the newest version of Minecraft, not the experimental one. It is a newly created world, nothing from marketplace except for a texture pack.

Update - I've managed to access my world after making a copy. It took exactly 2 saves for the world to crash once again, doing different actions, each time on 4.4MB. Also, the Copy trick is not working anymore.

Update 2 - After reinstalling my game, everything seems to be fine. I can even access the previously corrupted worlds now. Looks like the app itself got severely messed up somehow.

Does anyone know if this issue has reached the devs yet?

Reply from @unknown: I already answered you directly 4 months ago when you asked the same question. I removed your comments then because you posted them right after I had just explained the answer for someone else. Please stop spamming the bug tracker with pointless comments.

Has anyone found a way to fix this on ps4 yet?

The old worlds open well but once the save is done it is impossible to reopen. They can only be reopened if you go to a completely new chunk. In my case, I'm over 5,000 blocks away. It is not possible to play in this situation.

In the new 1.18.2 release on ps4 they fixed an issue fairly similar to this issue, it basically fixed issues with large worlds that were impossible to be opened and some sort of pink and black square texture would replace the normale textures. That is basically the issue that i started having with my world before i got this issue with it. Now in wondering if first this recent fix also fixes this issue or not. And if you all also first had the black and pink square issue before you got the “there was a problem opening your world” error message.

Yes this is the problem. I can open my old world and play fine but every time I close it it's impossible reopen the world. I have try everything. Reset the ps4, reinstall minecraft, save the world in the new chunk, in the nether, but no result. I'm very disappointed. 

Hello there,

i have the same problem with my ps5 SaveGame. When i start the SaveDate it will be open fine. But when i Exit and Save i cant open the SaveDate and the Screen is showing the text: There was a problem loading this world. This is very hard because there are days of Gameplay in this world. Does anyone know how i can fix it?

But someone find a solution?

I inadvertently created another thread (MCPE-152481) and was directed to this one, so I'll write about it. The bottom line is that version 1.18.10 has not solved this problem on my PS4, and the occurrence is becoming more frequent.
The save data is 1.5GB that I have been playing with after overcoming the problem in 1.18.0. I haven't had this problem yet with the new, smaller save data I created.
I really hope this problem will be solved soon.😭

うっかり別なスレッド（MCPE-152481）を作ってしまい、こちらに誘導されてきたので書きますが、要はバージョン1.18.10でも私のPS4でこの問題が解決されておらず、発生が頻繁になってきているということです。
セーブデータは1.18.0の問題を乗り越えてプレイしてきた1.5GBあるものです。新しく作った小さなセーブデータではこの問題はまだ起きていません。
さっさとこの問題が解決されることを強く願います😭

silencing the public I see, I'm just keeping this active so we actually have a chance to get this fix. Rather than 12 trillion small texture bugs.

Jared Colbourne: As I have explained to you before here and here, this is a bug tracker and not a discussion forum. I will again point you to the bug tracker guidelines and FAQ which explains how it works.

Please limit your comments to new information that might be help to the developers to fix the bug. A report is not a "thread" that needs to be "bumped" to make it look "alive", and comments are not for expressing yourself or giving feedback about Mojang's development decisions. Comments that do not add new, relevant information to a report are subject to removal, and continued disregard of our guidelines may result in a ban.

Im having the same sort of issue. PS4 my world worked fine before we recently purchased a PS5. When i tried to log into my world on the PS5 i got the "There was a problem loading this world" error message.  I then tried my PS4 and it now gives the same message. 

Smaller worlds load fine, new worlds load fine.

This was the same for my PS4 directly after Caves and Cliffs part 2 came out but was fixed with an update. 

After latest update, im still have the issue where i cannot log into my world. "There was a problem loading this world"

With the latest update I'm not able to play on my friends world either, and today is it's 2 anniversary.

This bug has appeared again on the newest wild update as of 6/11/22

This glitch happened to my 1.1gb world. I tried to use a copy and it set me back but it was working until I tried playing another time (after I saved and logged off) where the error came back. This has happened to my main world and 5 backups on my ps4. Please fix this as I have put well over a thousand hours into the world and would hate to lose it. I would certainly have a hard time ever putting time into a Minecraft world again if problems like this aren’t fixed and ruin saves.

It is since November of last year that there is this bug affecting only large worlds for ps4 it is not possible to save progress, all solutions have been tried, manual save, reset, save the world while in the nether . Say done I stopped playing.

I'm having this problem too.  Once world exceeds 1gb I can't load it.  This is game breaking.  Problem occurs on both PS4 & PS5.  Multiple worlds.  I can reproduce it virtually on demand.  PLEASE FIX.

Since the latest update my world will no longer save. It doesnt matter if i play an hour or 10 hours. When done i exit and save but when I go to reload the game i get a message saying "Tere was a problem loading the world". I have deleted the game and all saved data from the console and then reinstalled it and still doesnt fix the issue. This happens on my ps4 and my ps5 with this world. The world is 1.6GB and i have been playing fine for a long time with no issues. I don't want to lose my world and not sure what else I can try to fix it. 

Could any moderators answer if the problem has been considered for a solution? It is very frustrating not to be able to play with our old worlds after years of work.

I don't play this game anymore, with this bug it makes no sense to play. Nobody has been interested in fixing this problem for a year.

Me to. Me and my friends completely lost interest in this game once this bug happened to our world, for awhile after we tried different world but on java but they only last a few days. But my friends say that they don't want to invest more time into something that might get deleted again.

Hello everyone! All players who have this problem vote on the top right to keep the report high. Thank you!

I remind you to from now on, only post helpful or informative comments to that issue. Spamming will result in bans. This is a bug report site, not a forum or support site.

i get the same message and when i uninstall and reinstall my backup worlds lost from the cloud

Well it seems like all our affected worlds are +1GB big worlds, so it's probably due the saving limitations of Bedrock edition. Maybe adding more free space for worlds allowing us to make them bigger, just in devices capable of supporting such, would solve the problem. A Switch is gonna struggle with a 1GB world but a decent PC or a PS5 can run perfectly those. Just an idea

If you have a recent copy of the world available, you might like to upload a copy of it for investigation.

• On Windows 10 you can use the Export world feature.

• On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds

• On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)

Here are the steps to copy a world save on PlayStation:

1. Make sure your BLANK USB stick has been formatted to FAT32

2. On your PlayStation, go to Settings > Application Saved Data Management > Saved Data in System Storage > Copy to USB Storage Device > Select Minecraft > Select Saved World to copy > Copy

3. This should then copy the world save to the USB, which you can share to a file sharing site such as OneDrive, and then share the link.

If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.

https://drive.google.com/drive/folders/15CemYXxepYgnerPRrbpifCl2SJbYkzJu?usp=share_link

I share my PS4 World.
I created it in ver 1.16 and it was not loaded around 1.18.
This is the latest saved data in a readable state.
I can play with this save data, but once I save and try to resume, it cannot be loaded.

私のPS4のワールドを共有します。
ver 1.16で作り、1.18の頃に読み込めなくなりました。
これは読み込める状態での最新のセーブデータです。
このセーブデータでプレイすることはできますが、一度セーブして再開しようとすると読み込めなくなります。

Hello, I also have this issue and is there any way to play my world again or is it gone forever now?

Hello?

Also affects latest version(1.20.30) and the worlds still show the same signs.For me this problem started just after my world passed 1GB on my PS5 so might be a saving limitation issue as the world file is split in 2 in my cloud saves (one save around 960MB and another just over 100MB).This has made my main world unplayable and its backups showed the same issue i also have unaffected backups but im too afraid to open them.This issue has made me quit the game for a couple months now.

We just encountered this issue as well on ps5. Our world is also over 1 gb now. We got the same error. We deleted every local version of the world, uninstalled and reinstalled the game, then loaded copies from the cloud. None of the worlds would open until we got to a version from 11/16. We played on it a bit and then today, that same version got the same error and the 11/16 version was no longer available on the cloud to load. We had to go back to an 11/12 version. We have lost so much progress. It is very disheartening that we cannot progress on this world after years of work. It is also disheartening to see that this has been an issue for 2+ years and has not been resolved. Is there an update on this bug fix? 

I am experiencing this issue on Bedrock 1.20.60 and the latest 1.20.62 versions on ps5 (ps4 edition). For me, this issue started on 1.20.40 intermittently and became completely unplayable starting on 1.20.51. No worlds will load now and all are over 1GB in size. If helpful or relevant, I've encountered very similar issues during the last 2 major game update cycles between major versions (1.18>1.19 and 1.19>1.20) and each of the prior 2 cycles it didn't work until the last Bedrock update prior to the next major release. However, this issue has no workarounds that I've found where uninstalling/reinstalling and/or Realms would previously work on some occasions.