The broken-patch story now has an actual update
Yesterday’s Diablo II: Resurrected Steam mess has moved from pure damage report into follow-up territory. After players flooded Blizzard’s forums with complaints that the new 3.1.2 update was causing an “Initialization Error: Failed to initialize data (corrupted?) — Error Code: 1” on launch, Blizzard posted that it had rolled out a fix on Steam and that players should now be able to get back into the game. That makes this a real update, not just the same bug story reheated.
What Blizzard said
The clearest official response showed up directly in the forum threads where players were reporting the issue. In both General Discussion and Technical Support, Blizzard staffer Marcoose replied that a fix had been rolled out on Steam. That is the important part here: Blizzard did not just acknowledge the bug existed. It said a platform-specific fix was already live.
What players were seeing before the fix
Before that response, the problem looked pretty ugly. Multiple Steam players said Diablo II: Resurrected stopped launching immediately after the April 1 update, while forum posts described the error as affecting the Steam version specifically and contrasted it with Battle.net installs that appeared to be working normally. Blizzard’s own 3.1.2 patch notes had framed the update as a practical cleanup patch covering crashes, disconnects, UI, graphics, chat names, Blood Oath, and Warlock pets, which made the launch failure land even harder. A patch meant to fix technical issues had, for some players, become the technical issue.
The awkward part: not everyone was instantly back in
That said, the fix rollout did not seem to produce instant universal relief. In the same Technical Support thread where Blizzard said the Steam fix had been deployed, later replies still reported the game was not working for everyone right away. At the same time, players were sharing a manual .build.info workaround in separate forum threads, which suggests the community was still patching around the patch while waiting to see whether Blizzard’s Steam-side fix had fully settled in.
A cleaner ending, but not a pretty one
So yes, this one has moved forward. Blizzard says the Steam issue is fixed, and that is real news. But it is still the kind of patch-day story that leaves a mark, because the follow-up is not “what a smooth maintenance update.” It is “the emergency response arrived after the patch faceplanted on launch.” Diablo players are used to dealing with demons. They are a little less patient when the loader screen becomes one.
