Frosty99

I've been watching this issue since I commented on it on 19th August 2019. What I've seen since then is a number of similar issues closed indicating this is the main issue with this focus and a number of people list the same issue in the comments (as well as what most of us have already tried to rescue our worlds). I've seen updates on Hotfixs and yet still no actual dedicated fix or comment on the Jira from anyone at Mojang since my first comment. This has in essence become a frustrated community board conversation. It is not being looked at with a view to fixing our worlds.

This is a known issue. It seems to be for worlds that have become too big for them to sync correctly every time - indeed corrupting them beyond repair. The right thing to do would be to say that and that the worlds have gone. Ironically them being the largest size means they are the worlds we spent hours, days, months and years playing and creating.

The worlds are gone, corrupted and cannot be retrieved is my honest opinion. Maybe there will be a fix to stop this happening for future worlds, but as much as it pains me to say it the truth of the matter these are gone and if Mojang can actually have the courage and transparency to say that we can all move on and choose how we want to play the game going forward - or not as will be the case for some.

I feel your pain Griffin! Still nothing 😞 I've essentially stopped playing Minecraft through fear of losing another world I spend hours/days on...

So far, I've not been able to recover this world. I've also lost a new world too, but fortunately had a back up this time. Seems to be worlds over a a certain size when the Xbox needs to be rest (factory reset) or when a user is removed and reinstated and the worlds need to sync from their database it's corrupting my larger sized worlds. Makes me hesitant playing on these worlds to add more data (size) as I'll ultimately lose all progress!!!

I have the same issue and can't copy the world as the feature is disabled by the sync failure - just comes up with the same error...