It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
The game crashes into desktop when I try to play it. The launcher comes up, but when I click to play either the Diablo or Diablo classic options my screen goes to black for a couple of seconds, and then I get back to desktop. I've tried booting diablo.exe with administrative privileges and compatiblity settings for Win XP, but that doesn't work either.

I've got a Win10 64bit (I installed it yesterday, so it's basically clean) with a ATI Radeon HD 6670. I've got Direct Play and DirectX properly installed, and according to dxconfig and my graphics card software all drivers are up to date. I've tried a couple of old games (Epic 40K Final Liberation and Unreal) and they run fine.

Does anybody else has the same problem?

SOLUTION: Disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diablo executable to the exception list).
Post edited March 07, 2019 by Xulomander
This question / problem has been solved by bdschneiimage
avatar
Xulomander: The game crashes into desktop when I try to play it. The launcher comes up, but when I click to play either the Diablo or Diablo classic options my screen goes to black for a couple of seconds, and then I get back to desktop. I've tried booting diablo.exe with administrative privileges and compatiblity settings for Win XP, but that doesn't work either.

I've got a Win10 64bit (I installed it yesterday, so it's basically clean) with a ATI Radeon HD 6670. I've got Direct Play and DirectX properly installed, and according to dxconfig and my graphics card software all drivers are up to date. I've tried a couple of old games (Epic 40K Final Liberation and Unreal) and they run fine.

Does anybody else has the same problem?
I do if i start the game with GOG version and when I set any of their options differently than "default"
avatar
Xulomander: The game crashes into desktop when I try to play it. The launcher comes up, but when I click to play either the Diablo or Diablo classic options my screen goes to black for a couple of seconds, and then I get back to desktop. I've tried booting diablo.exe with administrative privileges and compatiblity settings for Win XP, but that doesn't work either.

I've got a Win10 64bit (I installed it yesterday, so it's basically clean) with a ATI Radeon HD 6670. I've got Direct Play and DirectX properly installed, and according to dxconfig and my graphics card software all drivers are up to date. I've tried a couple of old games (Epic 40K Final Liberation and Unreal) and they run fine.

Does anybody else has the same problem?
The same happens to me too. Can't really start the game no matter what I try. I tried to change the settings to my standard monitor resolution and wanted to try the other improvements and it just resulted in crashes. Even after I set it back to "default" it is still not working.

You are definately NOT alone!

Really hope it will get fixed soon or I want my money back.
Same with me, both versions and with any combination of video settings and all the tricks I remembered to try and get my old CD version to run. Extremely disappointing.
It would be rather problematic to help all of you in this thread, so if you still experience any issues with the game, feel free to contact our wonderful support team :)
Crashes at start for me too, I've just contacted support.
I'm really sad that it doesn't work, I was really looking forward playing Diablo again. :(
+1. I've contacted support, and the representative I got in touch with (if you're reading this, thanks for the help, Genoan!) exhausted all possible options for fixing the game, and nothing worked. We tried updating drivers, setting the correct graphics card (I've got a laptop with both integrated and dedicated graphics), deleting SMASHW32.dll, and the representative looked through all the error logs from Windows and everything and still couldn't figure out what the problem was. We even tried doing a "clean boot" (basically disabling all non-essential programs and restarting) and that didn't do anything to fix the crashing. At this point, the representative has offered me a refund, which I accepted. I have not received a response since then, but I did find the actual error logs from Diablo itself, which I hadn't noticed previously. I sent them to the representative through the support ticket, but again, still no response.
me too crash at launch
I experienced similar symptoms. For me it helped to disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diable executable to the exception list)
Post edited March 07, 2019 by bdschnei
avatar
bdschnei: I experienced similar symptoms. For me it helped to disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diable executable to the exception list)
Helped for me too.
avatar
bdschnei: I experienced similar symptoms. For me it helped to disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diable executable to the exception list)
I can confirm that manually adding Diablo.exe to the exception list fixed the "classic" version, but not the "modern" version. I will try globally disabling DEP next, and will update this post once I've restarted my laptop and tried running the game again.

UPDATE: It works! Disabling DEP has fixed my issues.
Post edited March 07, 2019 by YaBoiCreepachu
avatar
bdschnei: I experienced similar symptoms. For me it helped to disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diable executable to the exception list)
avatar
YaBoiCreepachu: I can confirm that manually adding Diablo.exe to the exception list fixed the "classic" version, but not the "modern" version. I will try globally disabling DEP next, and will update this post once I've restarted my laptop and tried running the game again.
Turning OFF DEP helps both versions run perfectly.
avatar
YaBoiCreepachu: I can confirm that manually adding Diablo.exe to the exception list fixed the "classic" version, but not the "modern" version. I will try globally disabling DEP next, and will update this post once I've restarted my laptop and tried running the game again.
avatar
HarryQC: Turning OFF DEP helps both versions run perfectly.
Yep, just tried again after disabling DEP globally, and I can confirm that it works.
Great news :) I already passed that find to our Support and a relevant article should be available shortly
avatar
Thiev: Great news :) I already passed that find to our Support and a relevant article should be available shortly
Any chance you could tell them my issue was fixed? I think Genoan went through with the refund...I can't access my support ticket, and I can't launch the game through GOG Galaxy.
EDIT: Apparently the game process was still open, which is what was preventing Galaxy from opening the game. Still can't access my support ticket though.
EDIT 2: Disregard this post. Idk what happened, but I was just able to access my ticket again. Have updated it to say that disabling DEP fixed the issue.
Post edited March 07, 2019 by YaBoiCreepachu