[Main Thread] Windows 19041 - Freezing for 5-10 seconds

Seven-2656 · August 13, 2020, 4:58pm

Blizzard please fix your game i wanna play !

foureight84-1430 · August 14, 2020, 9:35pm

Launcher script documented here: [Main Thread] Windows 19041 - Freezing for 5-10 seconds - #16 by foureight84-1430

So you don’t have to keep copying the files over manually.

MisoShiru-11528 · August 15, 2020, 1:19am

Is there a way to prevent this? Getting the UPDATE despite running the script on multiple occasions.

Keyblade-6785 · August 15, 2020, 2:53am

Not that i am aware i just close BNET replace the file again and reopen it and hope it says PLAY. A bit manuall yes but it works till Blizzard Fixes this

foureight84-1430 · August 15, 2020, 6:04am

It’s always going to update. The point of the script is to copy and replace the fxmod file and then launch game.

Rename the fmodex64.dll to “fmodex64.dll.new” and move it to the Diablo 3 x64 folder.

Create a .bat file with the following lines:
@echo off
copy /Y "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll.new" "C:\Program Files (x86)\Diablo III\x64\fmodex64.dll"
cd "C:\Program Files (x86)\Battle.net\"
Battle.net.exe --exec="launch D3"
That will replace the dll file and launch Diablo 3 via the battle.net launcher. This will bypass the D3 login screen.

Run the bat file with battle.net client running and it will copy the dll and launch D3 right after. The dll may get updated later on but launching it via the bat file mentioned above addresses the update issue.

Kemerogh-1429 · August 16, 2020, 6:32pm

@Drakuloth it’s been 10 days since the last update and 2 months since this was reported. This is nuts, you have a game breaking bug for a meaningful percentage of the people who still play this game. WTF is Bliz doing?

dreadu-2211 · August 16, 2020, 7:20pm

An ETA on a potential fix would be nice after multiple weeks

Edit:
Just noticed the update was due this week (after pausing it a few times). Unfortunaltely I can NOT pause it any longer then August 29th… Pls fix or the game is going to break. I like playing with sound and not messing up .dlls…

Keyblade-6785 · August 17, 2020, 7:16am

Blizzard this is happening to more and more people are forced to update thanks to Microsoft. This only effects YOUR GAME.
Wheres the fix . I want game sound

TheTias-1192 · August 17, 2020, 7:17pm

I’m actually surprised they haven’t pushed a reversion to the last known working FMOD DLL set. That would resolve the current issue and give them time to fix the broken version they updated to previously.

sNaKe-2541 · August 18, 2020, 9:05pm

they will never release a bugfix that breaks sound instead. then this forum will be full with a gazillion crybabies that want to play WITH SOUND

Luchious-1946 · August 19, 2020, 2:10am

call us crybabies all you want we payed to play this game

nu4a-2432 · August 20, 2020, 7:10pm

Day 3223562 since the problem started. Still no blue post to give us some hope!

Drakuloth · August 21, 2020, 1:39am

Hey folks,

We still haven’t heard back from the developers with anything particularly useful for you all. We haven’t forgotten this, we just haven’t been bumping the thread since we try to avoid posting on known bugs when there isn’t important information to be communicated.

MisoShiru-11528 · August 21, 2020, 3:06am

Good to know that it’s still being actively looked into.

Dolk-2463 · August 21, 2020, 5:26am

Have the same issue, freezing for 5-10 seconds after upgrading to Windows 10 2004. Since i only play hardcore, atm. this game is 1oo% dead for me sadly.

TheTias-1192 · August 21, 2020, 6:50am

The question I’d be asking is if the client can be made to use the last known good working FMOD DLL version from before the complaints started coming in here. I know it can’t just be replaced, as that breaks sound, most likely at least in part due to the MD5 not matching the manifest, which is why it would have to be pushed via the Battle.net app instead of worked around by us.

Seems to me that’d be the logical course of action to take if possible, and to touch base with the FMOD developers to see if they can glean anything useful from your internal crash reports.

SirIanKhama-1108 · August 22, 2020, 3:50pm

I’d appreciate it if Blizzard would just tell us that this isn’t a priority and isn’t going to be fixed in any reasonable amount of time. To be honest, this would be less aggravating, because then I could stop hoping I might be able to play. This has been going on for MONTHS with absolutely no discernible progress from the GAME DEVELOPERS.

Meteorblade-2266 · August 22, 2020, 4:13pm

When the upgrade to 2004 stops being optional, and gets flagged as a mandatory upgrade by Microsoft, if Blizzard haven’t fixed it by then they’ll be in for a whole lot more posts about this. That 2004 upgrade was made available in May, so that time may not be too far off.

Vermouth-1885 · August 23, 2020, 5:41pm

This freeze effect has been happening to me more frequently lately – ~4-8 sec of freeze, and occasional stutters – every 20-30 min.

As I play on HC, I’m really averse to continuing playing while this remains an issue. It’d be more than a little annoying to lose optimized gear with augments I’ve been painstakingly collecting all season to this tech issue.

Would love to see a fix, or at least a blue post verifying that the user-created solution is the best (only) method to use.

Recko1983-1726 · August 23, 2020, 6:13pm

I actually just fixed all freezes, stutters and crashes by installing Diablo onto my C:
I’m using Windows 2004 as well.

I tried everything up to that point including installing it on a brand new formatted drive.
Haven’t had a single freeze or crash since and the game loads twice as fast, I remember having the same issue with Destiny 2 running like crap until i installed it on my C:\