Yesterday everything was still fine, but today, when I try to launch Diablo, nothing happens, the game does not launch through the Battle.net launcher or even directly through the .exe file. Although I managed to launch the game once today through a file in the game folder, it took a VERY long time (maybe 5 minutes.)
UPD
YA proveril cherez dispetcher zadach “Analiz tsepochki ozhidaniya” i uvidel, chto protsess Diablo IV .yekhe (PID: 9624) Potok: 3240 okazalsya v situatsii vzaimoblokirovki. Chto eto takoye?
Ещё
172 / 5 000
Результаты перевода
Перевод
I checked through the task manager “Waiting Chain Analysis” and saw that the Diablo IV .exe process (PID: 9624) Thread: 3240 was in a deadlock situation. What it is?
I have kind of same issue… When I launch D4 it says playing now, but nothing happens. Then I restart computer and the I can launch it. It started after I installed new driver for my gfx card…? Haven’t got at fix for it though, sry
Yeah I’ve had the same problems, yesterday I tried to scan and repair files and tried to launch it, and like you it’s on a constantly loop and nothing launches, hopefully they’ll be a fix soon. Maybe reinstalling it would help? Although that’s a last resort.
For me it takes like 5 minutes before the game starts. Its literally 5 minutes regardless,
You can repair, you can reinstall you can wipe bnet and d4 (cheer and be happy for an hour that the heretical software/bane of your existence is gone) then reinstall it and it will still take 5 mins.
Doesn’t matter on hardware either. Both my laptop and Desktop have the same issue.
Hello. Mine problem have to be the same. Recently my game lunch time is about 4:40-5:00 min. Try all above reinstal game. Uninstall hd content and install it again. PLS Blizard solve this issue.
Anche a me lo stesso problema clicco su Bnet e il gioco non si avvia ci mette almeno 10 minuti e sul task manager si vede che il processo esiste…risolvete il problema pls
Go to your Diablo 4 folder and rename dstorage.dll to dstorage.dllbak. Some people have just removed the file altogether and it still works. But rename it first, and see how it goes. You are welcome, it was not me. Found it from someone who found it from someone who found it from… you get it. Thanks Blizzard for not offerring a solution to this massive problem.
