After server tragedy

[Torq-11171]

Diablo 3 doesnt load after server maintenance. Tried reinstall and pretty much everything. Anyone else have this issue?

[TheTias-1192]

What error are you getting? If it’s the VCRUNTIME DLL error, see this post. That should fix the problem for you. If it’s a different error, please share as much information as you can so we can diagnose the problem and try to fix it.

[Nemo-1174]

I am experiencing the same pain that you are

[Drakken-1531]

yup i got that VCRUNTIME104_1.dll have gone to a couple of listed links in other posting to get the files and did so with failure , still get same message even after remove and install new battle net , while rebooting system several time to make sure clean installs - one package i did gave me the VC++ 2005 missing , installed those for standard X32 along with the X64 and X86 and still same failure !!!

[Argos-1307]

I was hoping the patch would fix my D3 from crashing to my desktop. I can’t even play it 10 minutes on my new PC before it crashes out of the game. I’m relegated to playing D3 on my old computer. Tried everything! Still no fix.

[fxm-1132]

I have this issue!
I hit the Play button, I get Launching > Playing Now > then after about 5 or so seconds, the Play button returns. The game NEVER starts. Scan & Repair do not help.

VCRuntime DLL will not help as I am on a Mac and that’s a “Windows thing”.

After what happened with season 33 (the best I was ever having), I am really annoyed.

[TheTias-1192]

The macOS issue is a missing reference key on a file inside the D3 app bundle. Blizzard needs to rebuild the app with the key present in order to fix this.

[Krysdavar-1808]

Game just crashed and now battlenet won’t load. Joy and Rapture.

[Krysdavar-1808]

Scratch that, next try everything worked fine again.

[MommaBear-11893]

Please fix! Can’t play…downloaded the files, restarted, reinstalled…still no cure for the vcruntime 140_1.dll

[fxm-1132]

This fixed it (or at least allows Mac users to play):

Game does not launch after 2.8.0 update

I just tried this, and I was able to launch D3 after some dabbling, although I edited it with a text editor (which is a better solution in this case anyway). It IS quite the mess though, and Battle.net will be fighting you all the way. Once you edit the plist file Battle.net will offer an update (which is to revert the plist file to the broken version again). What you need to do is this: Open /Applications/Diablo III/Diablo III.app/Contents/Info.plist with a text editor Add the following lin…

There’s still an issue that the Game Icon is reset to a “generic” application icon in the Finder and it keeps asking to Allow network connections on startup, even though Diablo III is allowed a connection in the Security & Privacy system preference. (Minor issues as long as the game is working!)

[TheTias-1192]

@fxm-1132

There’s still an issue that the Game Icon is reset to a “generic” application icon in the Finder and it keeps asking to Allow network connections on startup, even though Diablo III is allowed a connection in the Security & Privacy system preference.

The reason you’re getting the connection nag and the generic icon is because you’ve altered the app in a way that causes it to no longer match its internal hash value and macOS can see this. macOS is doing exactly what it’s supposed to do - protect you from yourself. That doesn’t mean the step isn’t necessary to play at the moment on macOS, just that this is expected behaviour for that OS.

[Adventurer-120973105]

Same thing with me. Im on a Mac and the play button pops up after trying to launch. weird thing happened to my Diablo icon, it changed to a white label with a capital T on it. what do you suppose that is all about?