I started to receive odd loading and exit game freeze. I would have to terminate the Diablo 4 process manually. It wasn’t all the time but enough to force me to test various solutions. I finally resolved it for my Diablo 4 experience and thought I would share in case it helps anyone else.
- In the Windows search box type “firewall”
- click Firewall and Network protection (standard windows firewall)
- click Allow an app through firewall
- click Change settings (you can’t add or remove without this)
- I had previously allowed Diablo 4 though the firewall so I found the previous entry and Removed (deleted) it.
- click Allow another app
- Browse to your Diablo 4 Retail executable and choose it.
- Browse to your Diablo 4 Launcher executable and choose it.
I no longer experience any loading or exit game freezes. This is old school and I haven’t had to open the windows firewall in ages but it appears to have resolved my issue. I hope it helps anyone else that is experiencing the same frustration.
2 Likes
Thanks for the information Mr. Scott.
Despite the people who don’t like D 4 and troll on the D 4 forums for w/e reason thanks for letting those know about this WHO do enjoy Diablo 4.
1 Like
I was getting the application hanging when I exited for few days.
It is no longer doing that. But I haven’t changed anything, it just kinda fixed itself, likely on their end.
1 Like
Mine was for several weeks. A few days isn’t enough to get me to try to find a solution. Glad yours auto fixed itself. On one hand it is nice when that happens but on the other it leaves it open to happen again since the cause is unknown. I am not a fan of sometimes errors, I prefer it to always error or never error. Always errors are easier to diagnose and resolve.
1 Like
It is not the worst error I have seen, after Fenris… 
So yeah going to taskmanager to kill the process wasn’t as bad. I do think they did an update after which I stopped seeing it.
1 Like
this used to happen to me all the time, then my pc died, and my new one doesnt have this issue. i think mine was a hardware problem