I am trying to update my Minecraft to 1.20.50 to play on my realm but there is 1.20.41 the latest update i shaw on the microsoft website and there is 1.20.41 the latest
Linked issues
is duplicated by 8
Comments 4
Some additional explanation for those who have mentioned related issues:
Xbox downloads its games from the Microsoft Store too, so both Windows and Xbox will have the same experience.(note)
Likewise, Xbox Gamepass downloads games from the Store, so it has the same experience.(note)
Cross-play depends on both devices running the same release of Minecraft, so until this issue is fixed players on Windows or Xbox will not be able to cross-play with other platforms, and vice-versa. Windows and Xbox can cross-play with each other, and other platforms can cross-play within their group.
The version of Minecraft that runs on Realms (for Bedrock) servers is special and is different from the Store version. It is submitted to the Realms team directly by Mojang, so it was unaffected by this problem. However, I'm not sure whether the updated release has been implemented for Realms yet. If it has, Windows and Xbox players will get a version incompatibility error when trying to join a Realm, while other platforms will be able to join. Conversely, if Realms hasn't been updated yet, only Windows and Xbox players will be able to join.
Uninstalling and reinstalling Minecraft will not help, but if you want to try it anyway, be sure to export your worlds from the Windows version first so you'll be able to import them again afterward. (It's always wise to make backups of your important worlds anyway. Just sayin'.)
Note: I might be wrong about these first two items, based on comments received subsequently. It is my understanding that Xbox systems internally run a limited version of Windows, and I assumed that they must therefore use the same platform code, but that doesn't necessarily mean they get the code from the Store.
Please be patient while this problem is addressed. This isn't really a bug that should have been reported here because it's not an error in the game's logic. Instead, it's a problem with uploading the update to the Microsoft Store, which is managed by a Microsoft team, not Mojang. The staff here don't actually know where a better place to report it would have been, but we've accepted this bug report to have a means of communicating what's happening to you.
What we can tell you with some certainty is that the delay in making the update available on the Microsoft Store must be due to the procedure Mojang has to use to submit an update to the Store. The update is either delayed by the Store team–perhaps they have a backlog–or the Store team couldn't certify that the software meets their standards for some reason. In the latter case (which rarely happens) they report the reason for rejection back to Mojang, who might then have to change something (usually something pretty minor and not in the actual game logic) and resubmit. The Store team will then put it through the certification process again and, assuming it passes, make it available in the Store. This process should normally not require more than 48 hours. If it takes longer than that, it will probably be turned into a Hotfix release instead.
What you should gather from this explanation is that the problem is an internal one between the Microsoft Store team and Mojang, which means the people who need to know about it already do. Which further means that no bug tracker ticket is necessary and you, the bug tracker users, don't need to update this ticket. We'll let you know anything else we learn about it here. In the mean time, thank you for your patience.