Stephen Geist

Seems it's fixed for me as well. Glad this either resolved itself or was fixed. Yay!
@deCoroftheMatter - Clever lol

@Koolen Glenn

Hahaha! My daughter started balling after seeing the state of our virtual home. Luckily I knew beforehand the original world file would be unchanged so I laughed and assured her it is in-tact (then showed her). She too fully expected me to be able to troubleshoot my way around it and try I did... to no avail. We'll have our fun soon enough 🙂

@Ian completely agreed, this should probably be split to 2 topics. Also, yeah the drama is a bit much. I understand people are upset (including myself) because we want this new release of the game to work soooo bad. However, they aren't keeping us from playing the same game we built our worlds in and it seems like that fact is being forgotten. The worlds are still there in the previous version, unchanged.

1.2.1 came out and I thought based on the patch notes that this issue would have been resolved. Unfortunately the same problem exists. I converted less than an hour ago and the world size converted from 334.5mb to 160mb. I was like "Okay maybe there is a difference in how it saves, lets just load it up and see."

Loaded up the world, crashed within 15 seconds. Had to hard reset the xbox one s, and now I'm back in the game and the converted world is no longer in the list at all.

This issue needs to be fixed asap as it is the main problem Mojang is facing in converting people over to the new version.

@Daniel Bohn Johansen
As Ian commented, importing from Xbox to Windows 10 is not the issue. Converting worlds from the Xbox One Edition to Minecraft (also on Xbox One, better known as Better Together, or MCPE or Bedrock) is the problem. I reckon the conversion feature will be fixed with the update that is currently waiting on certification and expected to be out towards the end of this week (or should be fixed, lest we see massive community uproar).

If the conversion was not intended to work right away, the new version should not have been released until that was added as a feature. If you have any source of information that states the Xbox One Edition conversion to Minecraft Bedrock was not actually intended to be functional until a later date and not at launch, I'd love to read it (not being sarcastic).

I am having similar issues. My world is around 335mb normally. THe first time I converted it was 180mb, with entire maps replaced, my hostile farm no longer works at all for some reason as well. Reconverted a 2nd time and it came out to be 170mb with the same issues but different maps replaced. The last time I got through the conversion process it turned out to be 48.5mb.

Now, when I try to convert, it gets to various %'s from 30% to 80% and crashes the Xbox One. It just flat out turns itself off!

EDIT: Got through conversion process with the world size ending up being 178.5mb. Loaded world, turned around once, and crash to black screen. Can't get to Home screen. Had to hard reset again.

I can still play my XB1 Edition with no issues but I desperately want to be using keyboard and mouse, and let my wife and daughter play on my world via their computers without taking up part of my tv screen. 😉

I'll keep up with this issue before I finally pay for Realms.

EDIT 2: I have been toying with the conversion to see if there is any consistency to what is going on. The main thing I've noticed that is the same every single time is that the back side of my base is replaced by the same exact map every time. It cuts off at the same point, same hill to the right and the same exact Village as well.. I've tested this several times so there is definitely some sort of consistency to what is going on. Just need to lock down the cause.