Fix sign-in errors, back up worlds before updates, and confirm what an official game drop actually changed. Every step points back at Minecraft Help — this site does not sell the game, does not host installers, and does not verify every fix first-hand.
Each module solves one job — start with the symptom, back up before a patch, recover a broken save, verify what changed after an update, or check the current install routes. Methodology: how we source answers.
Crash on load, sign-in loop, cannot join, sync hang, Marketplace stuck — ordered steps with links to the Mojang Help article that owns each step.
Where the device exposes Export World, save a .mcworld; on Xbox, PlayStation, and Switch, use a Realm upload/download as the generally supported cross-device route. Screenshot Settings > About, confirm free storage, and mark the current Bedrock version before a game drop lands.
Import a .mcworld without touching the broken slot, download a Realm copy, decide when to repair versus reinstall on Windows.
Smoke-test worlds, compare Bedrock version numbers with your group, and retry Marketplace maps that stopped opening after the patch.
Named game drops link back to the Mojang updates hub only — no unofficial patch numbers, no rumour posts.
Microsoft Store and console app stores — this site cannot check you out, and does not host any installer or launcher.
Match the symptom you have to the first thing to try. Every row links deeper into the guides page — none of these rows recommend a reinstall as the first move.
| Symptom | Where it usually is | First safe check |
|---|---|---|
| Sign-in screen hangs | System clock, family privacy, or Xbox status | Check clock, then Xbox status page; sign out and back in |
| Friend cannot join world after a game drop | Version mismatch | Compare Settings > About on both devices; update the older one |
| Multiplayer button greyed out | Child-account Xbox privacy setting | Adjust Xbox family privacy; child signs out and back in |
| Realm slot missing after payment lapse | Subscription entitlement | Download within Mojang's current 18-month post-expiry window; contact Support if unavailable |
| World crashes on load after new pack | Pack incompatibility | Export .mcworld where available, or download a Realm copy; disable newest pack, retry |
| Marketplace map stopped opening | Creator pack needs update | Check the pack's Marketplace entry for an update; keep the old .mcworld |
| RTX toggle greyed after driver update | GPU driver or supported GPU list | Vanilla world without RTX pack works? Update GPU drivers; confirm hardware on ray tracing page |
| Featured Servers list empty | Live Mojang service outage or partial refresh | Check Xbox status; retry after a few minutes — do not reinstall |
Full trees, exact clicks, and platform screenshots live on the guides page. Every route in the table above is documented by Mojang or Microsoft — not reverse-engineered here.
Almost every recovery step on this site depends on a working .mcworld export or a downloaded Realm copy. Direct .mcworld export is not generally available on Xbox, PlayStation, or Switch; for those consoles, a Realm is the supported transfer route when the world can be uploaded and the account can use Realms.
On devices that expose Play > Worlds > Edit > Export World, keep recent .mcworld files outside game storage. Xbox, PlayStation, and Switch do not generally offer direct .mcworld export; upload the world to a Realm and download it on a supported destination instead. This requires working Realm access and does not turn console storage into a general file browser.
Open Realm settings > Download World before renaming a slot, changing packs, or upgrading a subscription. Mojang currently provides an 18-month download window after a subscription expires, but that finite window is not a substitute for your own long-term copy.
The version number is the single most useful piece of evidence when a friend cannot join or a Marketplace map stops opening.
When a pack breaks the world, you already know which one changed. Saves ten minutes of guesswork during a crash loop.
Reference: Minecraft Help Center owns the current backup and world-import steps.
Bedrock advances in one direction — Mojang states you can only play the latest stable version or a preview/beta build. That single rule causes the three most common post-drop tickets:
A slower console has not finished updating. Compare Settings > About numbers, force an update through the platform store, retry the invite. Old versions cannot be pinned. Reference: Mojang, Java or Bedrock Edition.
Packs are versioned separately from the base game. When the base advances, some packs need a compatibility update from their creator before the world will load again. Do not delete the world — export a .mcworld where that control exists, or preserve a Realm copy for console worlds, and wait.
Download a local copy through Realm settings first, then wait 15 minutes in case a build fix is still rolling out, then check Minecraft Help for a known-issue post before uploading the copy back to the slot.
The number in Settings > About is the single most useful piece of evidence when something breaks. It tells you which build every device in a group must reach before “we cannot join” is worth troubleshooting further.
Bedrock versions read as a series of dotted numbers — a major, a minor, a patch, and a build. When Mojang ships a game drop, the minor number advances for every platform on the same schedule. Two devices with different minor numbers cannot join the same session.
Mojang runs a Stable channel that most players sit on, and a separate Preview or Beta channel with early builds of the next drop. A Preview device cannot join a Stable device even if the numbers look close. Confirm the channel as well as the number when a Realm or friend refuses to load.
Each platform's store pushes Bedrock updates on its own schedule. A slower console can lag Windows by hours or days after a drop. The fix is always to force an update on the older device — old builds cannot be pinned in place.
Reference: Mojang, Java or Bedrock Edition for the version model, and Mojang feedback, Beta / Preview changelogs for the current Preview build.
Recovery tickets often mix two different failures into “the game will not launch”. Separating them saves reinstalls that were never going to help.
The Xbox status page shows an incident, the sign-in screen loops, or the game accepts credentials and then reports offline. The problem is on Microsoft's side or in the family privacy setting for that account. Reinstalling does nothing — wait, or fix the family setting.
Sign-in succeeds but the game asks Buy Again, refuses to open a paid Realm, or hides Marketplace purchases you know you own. The problem is a mismatch between the account signed into the game and the account that owns the license. Fix: sign out and back in with the owning account.
Open the Xbox status page in a browser. If it lists an active sign-in or Live incident, treat this as sign-in. Otherwise open account order history at account.microsoft.com/billing/orders and confirm the Minecraft entitlement is on the account signed into the game. If it is not, this is an entitlement mismatch, not a sign-in bug.
This site collects patterns from the Minecraft Help Center, the Xbox status page, and player reports. It does not open tickets on your behalf, does not access your account, and does not verify every fix. Escalate to Mojang when the four checks below all pass and the symptom persists.
Then open a ticket at help.minecraft.net > Submit a request with the platform, the game version, the exact error text, and the Microsoft account email. For an actual bug that reproduces cleanly, the correct destination is bugs.mojang.com.
Click-by-click symptom tree, backup checklist, world-recovery flow, post-update verification, and Windows Store reset steps.
Sourced answers on world backups, sign-in loops, Realm slot recovery, pack failures, and when a reinstall is actually the right step.
Cross-play, Realms, Marketplace, split-screen, Add-Ons, ray tracing — each feature paired with its post-drop failure signature.
Official-store links for every device, and a short checklist before you reinstall — because reinstall does not fix account, privacy, or version-mismatch problems.
If you have not bought Bedrock yet, minecraftbedrock.app covers platform choice, licensing, and Buy Again fixes. This site covers what happens after install.
The independence statement, the citation policy, and the failure boundaries — including the promise that the linked Mojang article always wins.
Reviewed 28 August 2026. Bedrock behaviour changes between game drops — subscription tiers, Marketplace catalogs, and platform requirements move without notice. Every claim above links back to the official Mojang, Xbox, or Microsoft page that owns the current version, and that page is the version to trust.