Minecraft Dungeons II Steam Deck Support: Mojang Responds as Proton Gaming Services Workaround Emerges

Two things need to stay separate here. The official statement is a promise of work in progress, not a patch or a release date. The community workaround is unofficial third-party code. It is not a Microsoft fix and nobody guarantees it.

What Mojang actually said​

The official word came on the Minecraft Feedback site, not in a press release. GamingOnLinux reports that the developer didn't answer its email, but the team did post a note on the Steam Deck Support thread there. The note reads: "We've seen your feedback about Steam Deck support for Minecraft Dungeons II. The team is working on it and we hope to have more to share soon. Thanks for your patience, and keep the feedback coming."

Steam Deck HQ read it the same way. The reply doesn't give a timeline on when it could happen, but it's still an acknowledgment of the possibility of it becoming compatible.

So some headlines have jumped ahead. "Official fix coming" suggests something scheduled. What exists is a statement that work is underway, with no ETA and no named Proton or SteamOS target.

It's also a change of tone. WindowsForum reported before launch that Mojang developer Marc Watson said the team had not announced support for that platform when asked about Linux. Minecraft's listed requirements are still Windows 10 64-bit, version 1703 or newer, for both minimum and recommended configurations, plus DirectX 11; they do not list Linux or SteamOS.

Section summary: Mojang says it is working on Steam Deck support. That is progress, but it isn't a patch, a date or a promise of general Linux support.

What goes wrong at launch​

Reports agree on what happens. A compatibility report filed on Valve's Proton GitHub tracker on September 29 used Proton Experimental on a CachyOS system with an AMD Radeon RX 9060 XT and Mesa 26.2.3. It says the game asks to install Gaming Services. Once the user accepts, the process stays running but no window ever appears. Valve labels the issue "Game compatibility – Unofficial." At the time of writing it had no assignee and no milestone.

Other testers saw the same thing on the Deck. Gaming on Steam tried GE-Proton, DW-Proton and Proton Experimental, and no matter which one was used, the game hit the same Microsoft gaming services prompt and failed in the same way. Steam Deck HQ added that it will always fail at this spot, no matter what Proton layer is being chosen or what update channel we're on.

The cause is the dependency on Microsoft's PC gaming runtime. Proton translates Windows API calls well, but it doesn't reproduce the Microsoft Gaming Services stack that the Xbox PC app and Microsoft Store titles use. This Steam release apparently still expects that stack, the way a guest turns up at a party expecting a host who isn't there. A TechPowerUp contributor also cited a Steam reviewer who suspected that missing Microsoft Store API dependencies are to blame. That fits the symptoms, but it's a community diagnosis, not an official root-cause statement.

About the Windows claims: TechPowerUp says Windows players are also having launch problems. The primary sources checked here don't show a Windows-wide failure. One Steam reviewer did post a Windows tip: do not run the game as admin, as this appears to be breaking the steam link and causing error 0029. That reviewer suggests checking the compatibility tab on the executable's properties. It's worth trying if you're on Windows and see that error, but it's one user's tip, not official guidance.

Section summary: On SteamOS and Linux, the game stalls at the Gaming Services install prompt on every Proton build reported so far. Windows problems appear to be scattered, not systemic.

How the community workaround works​

The best-known workaround is an MIT-licensed GitHub project called Dungeons2_linux_fix, maintained by Kubas556. It describes itself as a local stand-in for Microsoft Gaming Services that lets Minecraft Dungeons II (Steam app 1912410) start under Proton.

The game looks for a file called xgameruntime.dll. The project builds a replacement for it, and the repository says it neither modifies the game nor includes Microsoft's own library.

According to the README, setup looks like this:

1. Prerequisites: Proton and Python 3.
2. Clone the repo into ~/.local/share/dungeons2-compat, which is where the DLL looks for its helper files. Then make install.sh and xauth.py executable.
3. Quit the game completely first. A running process keeps using the old DLL.
4. Run install.sh. It copies the replacement DLL next to Dungeons.exe, next to Dungeons-Win64-Shipping.exe, and into the Proton prefix's drive_c/windows/system32. It reads Steam's libraryfolders.vdf to find other libraries. If Steam isn't installed in ~/.local/share/Steam, set STEAM_ROOT to point at it.
5. Set the Steam launch option in the game's properties: WINEDLLOVERRIDES="xgameruntime=n" %command%. This tells Wine to load the native (replacement) DLL instead of its built-in one.
6. First launch: a window shows a code and opens Microsoft's device-code sign-in page at microsoft.com/link. Enter the code and sign in with the Microsoft account that should own the Xbox profile.

Success means the game opens a window instead of hanging after the Gaming Services prompt.

A correction to early coverage​

Some early coverage quoted an older description of this project. That version said sign-in was a manual xauth.py step with no in-game prompt. The current README says otherwise: the first launch starts the device-code flow itself. The token is cached at ~/.local/share/dungeons2-compat/tokens.txt with file mode 0600, and later launches reuse it until it expires. After that, the helper refreshes the token or asks you to sign in again.

Known failure points​

• Microsoft account linking in game settings may fail with a server error. The README says PlayFab rejects the Xbox token that the main build supplies. The maintainer points to a cursor/playfab-account-linking branch as a fix: check it out, rerun install.sh, and sign in again on the next launch.
• Game in a non-default Steam library: make sure STEAM_ROOT is set correctly so the script can find it.
• Nothing changed after installing: the game was probably still running. Quit it completely and run the installer again.
• Rebuilding from source: a prebuilt DLL ships in src/. Building your own needs a MinGW-w64 POSIX cross-compiler.

The maintainer says the DLL answers the specific Gaming Services calls this game makes: task queues, the signed-in Xbox user (your real XUID and gamertag from the cache), the title ID, the retail sandbox, persistent local storage, and the HTTPS security settings XCurl asks for. PlayFab login reportedly still uses the Steam session. These are the maintainer's own descriptions. No independent security audit has been done.

This isn't the only fix circulating. One Steam reviewer said they got it to work on the steam deck using a solution posted in the Proton issue thread, and later added that someone streamlined the solution for less savvy users.

Section summary: The workaround swaps in a homemade Gaming Services DLL, adds a Wine override and handles Microsoft sign-in itself. According to its maintainer it works, but it has rough edges such as PlayFab account linking.

Should you use it?​

Should you let a GitHub project you've never seen handle a Microsoft account token and put a DLL into your Proton prefix's system32? Some readers will, and that's their call. Here's what they're taking on:

• You're running unaudited third-party code that sits between the game and your Microsoft account. Read install.sh and the C source before running anything. Don't paste terminal commands you don't understand.
• The token file is account authentication material. Don't post it in bug reports, screenshots or Discord threads.
• The legal position is unclear. GamingOnLinux says the third-party login script reportedly can get you logged in but seems the legal situation with it can be messy, best just to wait for an official fix. Nobody has shown that it breaks any rules. But reimplementing a Microsoft authentication component is exactly the kind of thing that can look bad to an anti-tamper system or a terms-of-service review. No such action has been reported.
• An official update may replace it. When Mojang ships its own Steam Deck support, you'll want to remove the override and the replacement DLL so they don't clash with the real fix.

To be fair to the community: projects like this regularly push publishers to act, and this one is open-source and clear about what it does. It doesn't hide what it is. Still, "it works" and "it's been checked" aren't the same thing.

The bigger picture for Xbox on PC​

This is a familiar pattern for Microsoft games on Steam. The studios want players on Valve's store, but the games often carry Xbox PC plumbing like Gaming Services and Xbox identity that assumes a Windows machine. That gap barely matters on a Windows desktop. It matters a lot on SteamOS devices, which are now a real market.

Steam Deck HQ reported that the game was very playable on the Xbox Ally X, running at around 80-90 FPS on High settings at 1920x1080 resolution. That suggests the hardware isn't what's holding the Deck back. The problem is the plumbing.

Players have a precedent to point to. On Steam, the first Minecraft Dungeons is officially rated Unsupported, yet community members report it runs on the Deck with Proton GE. How quickly the sequel gets fixed will show how seriously Microsoft takes SteamOS as a place to sell its games.

Bottom line: Mojang says Steam Deck support is being worked on, with no date. A community Gaming Services replacement can get the game running under Proton now if you're comfortable reviewing and running third-party code with your Microsoft account. If you're not, the safe choice is to wait.