Dungeons II Error Codes 0059, 0060, 0064: Fixes

If Minecraft Dungeons II (Minecraft Dungeons 2) shows error 0059, 0064 or 0029, the code comes from the Microsoft sign-in and ownership check, not from a damaged install. The fixes most players report: set the Windows clock and time zone to automatic (0059), link your Steam account to your Xbox account in the Xbox app and update the Xbox app and Xbox Game Bar (0064, 0029), and make sure the game is not running as administrator (0029). These are player reports from Steam threads and reviews, not official fixes.

Which code means what

Mojang has not published an error-code list. The “meaning” column is inferred from what players described.

Code	What players describe	What players say helped	Confidence
0059	“Account doesn’t own the game” though it does	Synchronize the system clock or set the correct time zone	Three player reports
0064	Sign-in fails at startup	Link Steam to Xbox; English-only name; launch from the Xbox app	Several player reports, none official
0029	Fails to log in at startup	Do not run the game as administrator; link Steam to Xbox	One fix thread, two players confirmed related steps
0020	Game won’t start in Steam Offline Mode, even with an offline hero; also a sudden kick to the menu while playing when Steam’s community services went down for a minute or two	Offline Mode: a reply says you must be online when you start. Kick: nothing to fix, three other players said it happened to them too	Two threads
0042	“Can’t connect to Steam” when starting the exe directly while the game is stuck on “Running install script”	Update Gaming Services and Xbox in Microsoft Store Downloads, sign in to the Xbox app, restart the PC	Single thread
0058	Sign-in error (Portuguese-language thread)	Reset the Microsoft Store with wsreset.exe, check the clock, sync time, try another time server	Single post
0015	“Session disconnected”, lost connection to the dedicated server, and a no-internet message while connected; seen mid-dungeon	One player refunded and bought it through the Minecraft Launcher (result unknown)	Two threads, no fix
0060	“Unexpected error when verifying game ownership” (English and French threads)	One reply says installing pending Windows and graphics driver updates fixed it for them	Single reply
0063, 0073, 0041	Asked about in separate threads	Nothing reported yet	Unknown

Reinstalling alone did not help several players: one reviewer reinstalled, rebooted and deleted the manifest without success, and a poster on another thread reinstalled twice and still saw 0059 or 0064.

Error 0060

0060 is shown with “unexpected error when verifying game ownership”, the same kind of message as 0059, and has been reported in English and French Steam threads. The only fix posted is one reply saying pending Windows updates and graphics driver updates resolved it for them. We found no Reddit, Help Center or official entry for it. Try that update step first, then the clock, Xbox app and Steam-link steps below. This is player-reported, not official.

Fixes to try, in order

1. Set the date, time and time zone to automatic

Open Settings > Time & language > Date & time, turn on Set time automatically and Set time zone automatically, then press Sync now. Another poster (“check your system clock, that worked for me”) and two more (one Portuguese-language) also told 0059 sufferers to synchronize all their PC clocks. A Steam reviewer fixed 0059 by synchronizing the clock (dual-booting had knocked it off), a Steam poster fixed it by setting their time zone, and a player who got past 0064 and 0059 listed a wrong Windows clock among the things they fixed. Sign-in tokens can fail when the clock is off.

2. Update the Xbox app and Xbox Game Bar, and sign in

In the Microsoft Store, update both Xbox and Xbox Game Bar, open the Xbox app, and confirm you are signed in with the account you play on. A Steam poster’s fix thread says these can fall behind and cause linking problems.

3. Link Steam to your Xbox account (0064, 0029)

In the Xbox app, click your profile name at the top left, open Settings, and use the option at the bottom to link Steam. Reboot the game afterwards. The poster called this the ultimate fix for them, and two replies said linking Xbox and Steam fixed 0064 for them and that opening the Xbox app and Game Bar got a stuck sign-in working. Others in the same thread said nothing worked, so it is not a cure for everyone. The menu wording may differ between app versions.

4. Do not run the game as administrator (0029)

The same poster said running the game as administrator seems to break the Steam link and cause 0029. If a UAC prompt appears when you start it, look for Run this program as an administrator in the executable’s Properties > Compatibility tab and turn it off. This is one player’s finding.

5. If the sign-in window is white or the game freezes when linking

A player whose game froze on a white Xbox login screen said this sequence fixed it, without knowing how many steps are needed: turn off the Steam overlay, close the game, sign out of Steam and close it, sign in to the Minecraft Launcher with the same Microsoft account, open the Xbox app, sign in and link Steam to that account, restart Steam and launch the game, then link the account in the game.

6. If the Link button does nothing

In a separate thread, players whose Link Microsoft Account button did nothing or bounced them out of the game suggested: press Esc at the link prompt, open Settings, set video to windowed, go back and try linking again; turn off the Steam overlay; or simply restart the game and try again. One of them got it working after a restart about ten minutes later. All are player reports.

7. Try the extra steps other players added (0064, 0059)

Players in that thread reported these, without confirmation from anyone else: adding -windowed to the Steam launch options, running wsreset.exe from the Windows Run box (it resets the Microsoft Store cache), and restarting the game repeatedly until the login succeeds. One player also said using only English letters in the name resolved 0064, and another asked people to launch from the Xbox app. Try one at a time.

8. Repair Gaming Services and restart

Sign-in relies on Microsoft’s Gaming Services. Follow the repair steps in crash on launch, then restart. See Microsoft account link failed for the ownership message.

9. Wait and retry

Launch-day traffic on Microsoft’s sign-in caused failures, and one poster guessed server overload. If nothing else changed, retrying after an hour or two is legitimate. See stuck on loading screen if the sign-in hangs instead of showing a code.

Still stuck on 0029?

Some players say nothing has worked. One posted that they had tried everything in the fix thread and also cleared their Windows Credential Manager entries, and still got a Windows sign-in error (0x89245104) before the game’s own login. Another had already synced the clock, checked the admin box, updated the Game Bar, synced Xbox to Steam and run the repair tool, and asked for a refund fix. We have no working answer for those cases.

Error 0020 appears when Steam is set to Offline Mode: a poster reported it even with an offline hero, and a reply says the game needs an internet connection when it starts. This is a player statement, not an official rule.

Error 0059 is also reported by a player using Steam Family Sharing who had updated everything and was considering reinstalling Windows; no fix there.

What we do not know

• What each code officially means.
• Whether 0059, 0060 and the “unable to verify ownership” message are the same failure.
• Whether the Steam-to-Xbox link is required or only helps some accounts.
• Whether 0059 is tied to a mismatch between Steam and Microsoft account emails (one poster claimed it; nobody confirmed) or to the Deluxe Edition (a single poster’s guess).
• What 0063, 0073 and 0041 mean.
• Whether Family Sharing copies can pass the ownership check.

We will change this page when Mojang, Microsoft or Steam publishes something, or when enough players confirm a fix. None of the steps above is guaranteed.