After I updated the game to version 26.40.27, a window appeared upon launching asking me to choose between local storage and the cloud; I chose the cloud. When I checked the storage in the options, it showed 0 bytes used out of 0 bytes—with the bar indicating it was full—yet the worlds were still there. It didn't show whether the worlds were in the cloud or on the computer. When I closed and reopened the game, the storage returned to normal, displaying 4 GB, but the worlds had moved out of the cloud; the local storage icon appeared on the worlds, indicating they weren't in the cloud, so I uploaded them again. They shouldn't have left the cloud like that.
Attachments
Comments 6
This issue has been reviewed by our team.
Please add new, relevant information if it helps us understand or reproduce the issue. To show that you’re affected, use the vote feature rather than commenting.
If a fix is implemented, it will be listed in our official changelogs.
For major outages or urgent assistance, visit the Minecraft Help Center.
Before I encountered the issue, Minecraft Preview wasn't installed yet; I installed it and launched the game, which presented two options—directly from Windows settings or something similar—asking me to choose between using local storage or the cloud, and I selected the cloud. Basically, it’s a startup error that occurs when the game is opened for the first time; that might be what's happening.
A quick correction: the game isn't exactly being opened for the first time—I was already playing it. Before uninstalling, I had uploaded a world to the cloud and uninstalled Minecraft Preview; then I reinstalled it, and all this happened.
I might have found the main factor now, though I could be wrong. I had a different Microsoft account on my computer, so I created a new user profile—effectively a new setup—and removed the old account. Then, on the new account, I purchased and installed Minecraft Preview; the old account had stored an old world in the cloud for Minecraft Preview. While this was the first time I installed the game on the *new* account, it wasn't the first time on the computer itself, and that’s when the error occurred. I could be mistaken, but this is the most accurate information I have, and I’m fairly certain the bug can be reproduced.
Thank you for helping us improve Minecraft! We saved your files: