Diablo IV's Season 14 — Season of Death Awakening — went live on July 1, and within hours it became clear Blizzard had broken something more than just balance numbers. Players running the game through Proton on Steam Deck and other SteamOS or Linux systems found it would launch, sit for a few seconds, and quit without ever opening a window. No amount of the usual troubleshooting helped.
What's actually broken
Reports on the official Blizzard forums describe the same failure across setups: the process starts, briefly appears in the task list, then exits before a window ever renders. Players tried fresh Proton prefixes, switching between several Proton versions including Experimental, running Steam's Scan and Repair tool, and various launch-option tweaks. None of it worked, which points to something broken in the build itself rather than a local configuration issue — the kind of regression that normally gets caught by testing against Proton before a patch ships.
The timing makes it worse than a typical bug. Diablo IV was one of the most-played games on Steam Deck as recently as May, so a season launch — usually the single biggest traffic spike a live-service game gets all year — is exactly when a platform-breaking regression does the most damage.
Blizzard's response so far
Blizzard community manager Marcoose confirmed on the forums that the team was aware and building a fix, initially hoping to ship it the same night. That first attempt didn't work. A follow-up post a few hours later was blunt about it: "our fix tonight did not solve the issue so we will regroup in the morning." As of this writing, Linux and SteamOS players are still locked out of Season 14 while Blizzard prepares a second attempt.
To Blizzard's credit, the studio has a longer history of taking Wine and Proton compatibility seriously than most large publishers — SDL's creator worked there for years, and the older Diablo games have generally played well under Proton. That history is part of why this particular regression stands out: whatever changed in the Season 14 build appears to have skipped Linux testing entirely before going live.
What to do in the meantime
There's currently no known workaround. If Diablo IV won't launch on your Steam Deck or SteamOS install right now, that's expected — it isn't specific to your hardware or your Proton version. The fix has to come from Blizzard's side. Watching the official forum thread or Blizzard's usual patch-note channels is the fastest way to know the moment a working build goes out — Season 14 content itself, including the new Horadric Gem changes and Uber Mephisto adjustments, is otherwise live and unaffected on Windows.
For context, this looks like a Blizzard-side regression rather than a platform-wide problem — Valve shipped its own SteamOS update this same week that fixed an unrelated crash-on-launch bug in FINAL FANTASY VII REBIRTH , so Proton itself isn't broken, just this particular Diablo IV build.
No comments yet