A patch meant to clean things up seems to have knocked some players offline
Diablo II: Resurrected got a fresh 3.1.2 patch on April 1, with Blizzard listing fixes for crashes, disconnects, UI sizing, graphics rendering, chat names, Blood Oath, and Warlock pet behavior. On paper, that sounds like a tidy little maintenance patch. In practice, some Steam players say it did the exact opposite by making the game stop launching altogether.
The main complaint showing up across Blizzard’s D2R forums is blunt and ugly: after the update, the Steam version throws “Initialization Error: Failed to initialize data (corrupted?) — Error Code: 1” on startup. Multiple players say the game was working fine before the patch and broke immediately afterward, which is never a great look for a stability update.
What players are reporting
One detailed Technical Support thread says the player already tried the usual ritual sacrifices to the PC gaming gods: verifying files, deleting config files, deleting the saved-game folder, reinstalling, running as admin, flushing DNS, and reinstalling Visual C++ packages. According to that report, none of it fixed the startup error. That matters because it makes this look less like one bad local install and more like a patch-side problem affecting at least part of the Steam audience.
The issue also spilled into General Discussion, where other players reported the same launch failure and tied it directly to the new Steam build. By later replies in Blizzard’s update thread, community members were already passing around a manual .build.info workaround, and several players claimed that fix got the game running again, including on Steam Deck. That is useful for affected players, but it is also the kind of sentence Blizzard probably doesn’t want attached to a routine patch day.
Why this one lands badly
A launch-breaking patch is always worse than a boring patch. Nobody gets excited about UI fixes, but at least those let you play the game. When the “fix various crash issues” patch becomes the patch that stops the client from opening, people notice. Fast.
There’s also an awkward bit of timing here. Blizzard’s official patch notes present 3.1.2 as a cleanup pass for Reign of the Warlock, not some risky overhaul. So if Steam users are getting bounced at launch with Error Code 1, this is less “new feature teething pain” and more “the patch tripped over its own boots on the way out the door.”
Right now, the forums are ahead of the official fix
As of the latest forum activity, players are still comparing notes, sharing the error, and testing community workarounds. Blizzard has the patch notes up, but the bigger story for some Steam users is a lot simpler: the patch is live, and the game they were planning to play tonight currently disagrees.
