The game updates with every ladder reset - check your facts. I haven’t updated anything before the ladder reset and didn’t have any issues. Ladder reset came, I still haven’t updated anything and the issues were online. The other interesting part is - why only d2r suffer from windows update?
Follow your own advice.
A game update is not required for a ladder reset. It never was for any Blizzard game.
The current D2R build was made on 12/7/24 right before Season 9 started and it has not changed since.
check your facts yet agin…
tons of games had problems with 24h2 build of windows 11, the fact is that most games sufered BSODs because of some anticheat software, M$ blocked updates to 24h2 on those machines that M$ spyware detected said anticheat software installed, yet recently blizz is very slow in reacting to issues with games that don’t bring significant revenue to the table…
Just a followup, the fix that I posted earlier stopped working. This game used to run flawlessly, now it runs like a concrete turd stuck in quicksand. I can’t believe that a world class video game designer would release something as crappy as this in this day and age. The old Blizzard is probably rolling in their graves when they downloaded this **** update.
How horrible.
Try “Realtime” instead of “High Priority”.
Tried that too. Even tried low priority. The problem I have is that this game actually ran flawlessly before this patch. Now it runs like a turd. I’ll wait for the next season to see if they fix it, not trying anything else.
@FatDumbKitty
If You’re wiling to participate and don’t mind breaking Microsoft’s EULA ( i’m talking of windows EULA here not D2R being owned by M$) and also promse to keep your mouth shut and not spread the method i can give you, then drop me your battle tag, i’ll discuss some measures how to “improove” your connection with the server, though it puts increased strain on the servers, so it’s not something that should be allowe to everyone, that’s wath the part about keeping your mouth shut was…
If you’re in then drop your battle tag and state your server i usually play on eu, but i can join US for the sake of our conversation, and if you’re out than please say so.
I think I just solved this painful experience for myself in Windows 11. I had multiple crashes and freezes with D2R, even though ~20 other games ran perfectly.
- In Settings > System > Display > Graphics, I turned OFF this one option:
- Optimizations for windowed games
- In Settings > System > Display > Graphics > Advanced Graphics Settings, I turned both options OFF:
- Hardware-accelerated GPU scheduling
- Variable refresh rate
I would guess that turning off Hardware-accelerated GPU scheduling was the one that fixed it, but I didn’t test individually, and now that it’s working, I’ll leave it well alone.
Good luck!
Your proposals might not nessecarily be the fix… You see the problem has been for some time regarding M$ handling certain outdated game features, like for example certain not updated anticheat protection was causing 24h2 to either BSOD or freeze and CTD, somethimes intermitten game freezes and or intermitten mouse lag… some of those annoyances have been tackled by M$, with a hotfix deployed shortly after this month’s patch tuesday a.k.a. during past week… especially the patch ending with KB… 3060 is sepose to do the trick…
So maybe or maybe not the thing You’ve discovered… this might be simply a result of your rig installing M$ hotfix… there’s still an ongoing issue with Intel AlderLake+ generations of processors that cause the games to behave unstable with 24h2…
I just fixed this problem by doing a fresh install of Windows 10, and dumping W11. (as well as dumping intel 13th/14th gen CPUs)
I can now effortlessly run (8) copies of the game again on the same desktop machine… just like I could back in the day before W11 + D2R went south back in March 2025.
Desktop Specs (machine #1)
Ryzen 9600x
128gb DDR5 RAM
RTX 4060
Desktop Specs (machine #2)
Ryzen 5600x
128gb DDR4 RAM
RTX 3060 12gb
After setting the priority to the diablo .exe’s the issue seems to be fixed. Keep in mind that once you set it from Task Manager it is not permanently, for this there is a way in the windows registry to do so. This must be done once and all your instances will have set priority to high. Hope this helps.