Error Codes

troubleshootingpclaunch
Error Codes

Launch-day PC startup failures in Gameplay Overview centered on one step: the Microsoft account link and verification. Sign-in failures were the second most common complaint in Steam negative reviews that evening, and three error codes kept appearing — 0029 and 0064 most commonly, plus 0060 "Verification Failed." No official fix was published by the evening of September 29, but players found workarounds. Here are the codes and the fixes, in the order most likely to work.

What each code means

The fixes, in order

  1. Update the Xbox app and Xbox Game Bar from the Microsoft Store. This was the most reported cause of the launch-day failures, and updating both clears 0029 for most players.
  2. Sign into the Xbox app with the same Microsoft account you use for the game. A mismatched or signed-out account is the next most common trigger.
  3. On Steam, link Steam to your Xbox account via the Xbox app profile → Settings. This is the step 0029 usually complains about.
  4. Do not run the game as administrator. Running as admin breaks the Steam link and brings 0029 right back — launch it normally.
  5. For 0064: sync your Windows date and time, sign out and back in inside the game, and repair the Minecraft Launcher.
  6. Run Windows Update and update your graphics drivers. One player's 0060 cleared after doing both.
  7. Reinstall as a last resort if nothing above helps.

If it still fails

Check that your PC meets the Minecraft Dungeons II PC Requirements — the game needs Windows 10 64-bit (1703+) at minimum. Also confirm your platform: the game launched on PC, Xbox Series X|S, PS5, Switch, and Switch 2 with full crossplay via one Microsoft account, so a persistent sign-in failure on PC can also be tested by checking whether the same account signs in cleanly on another device. If a fix eventually comes from Mojang or Microsoft, it will land through the Xbox app or launcher updates, so keep both current.