Game always freezes on "Logging Into Diablo 4" screen... tried everything

My friends and I play all the way through the original Diablo IV campaign, and then took a leave of absence. A few days ago I fired up my PC:

Alienware Aurora R15
Windows 11
13th Gen i9-13900KF
GeForce RTX 4090
32 Gigs Ram

I purchased the expansion, and was able to get into the game 1 time… for about 10 mins. Then I suddenly got a red message at the top of the screen stating “Reconnecting to Server”. I continued to play, for several minutes but that message never went away.

So I restarted the game, and from that point forward I have never been able to get into the game again. I get to the point where it is connecting to the server, and once I see the message “Logging Into Diablo 4” it just stops and seemingly freezes as the music stops.

I have tried renaming a dll file to dllbak like many have suggested, I have disable Razer Chroma like others have suggested, I completely wiped out and rebooted my windows install and started fresh… I get to the same exact screen “Logging Into Diablo 4”. The last thing I did was delete the 130 gig installation (again) and reinstalled the whole game, and still it freezes on the same screen.

I do not usually post in forums but this has been infuriating. Does anyone else have or have resolved this issue before. Please help!

I should also add, that this whole thing seemingly started after I went to turn up some of the graphics options to improve the look.

use the geforce experience app, lower the graphic settings, and try

First off, thanks for responding to my post.

I used the app, and attempted to lower the settings gradually and all attempts failed. Then I lowered everything to the lowest possible settings, and its still failing. Stopping at the same “Logging Into Diablo” screen

:confounded:

You may want to move this thread via edit to the tech support forum so the geek squad can look at it

Thank you, I have moved it. Didn’t even realize I was in the wrong place!

This would indicate a connection issue.

That would probably revolve around Direct Storage, which I doubt has an influence here, but you can disable that with a better method:

Probably not going to help anyway, but okay.

Okay, I want to make sure I understand. You completely reinstalled windows? Or did a Refresh (where it leaves stuff intact and essentially does a “repair” of Windows)? Those are two entirely different things. And that would mean that:

This would have already been done with the above step. Or it should have been.

This sounds like its a desktop? Is that correct?

Are you hardwired to your internet or using a wireless connection?

Any other details about your internet, what router, etc?

Does your system use an ethernet card based on an Intel I225-V model? (look in device manager) Assuming you are using a network cable and not wireless, those can be problematic with some routers, especially when set to auto negotiate speeds. I usually recommend setting them locked to the routers top speed for the port its connected to. Usually this is 1GB Full Duplex. The card can operate up to 2.5GB Full Duplex, but with some routers it can get stuck and cause issues, especially with Diablo IV when its set to auto-negotiate, which is its default setting.

The game started hanging on “logging into Diablo 4” consistently today. Would do it once in a while before, but now all the time. Adding -diableds to the command line arguments in the bnet launcher game settings for d4 did the trick for me. Thank you!

i have been playing diablo 4 just fine since the expansion launch, and suddenly, this afternoon, i now have this very same issue. I changed nothing. I did post some huraah’s for POE2 and 'dissed Diablo 4 in some youtube posts, my tinfoil hat is on and i think they purposely blocked me. (/laughs)

Same problem here as well. Started today for no reason.

Having same issue. Game freezes and no music at the “Logging Into Diablo IV …” dialogue and then after 10 or so minutes the game just closes. Relatively new issue over the past week or two.

Installed Nvidia Experience - no change. Occasionally the startup sequence will complete if I reboot PC, but not always.

This has been happening to me regularly since the last update. I’ve tried added the -disableds via the game settings, will see how that goes.

That might not help this, but let me know if it does.

You can also provide a copy of your FenrisDebug file from the game install folder. To share it:

  • Go to pastebin.com
  • Copy the contents of the file you want to share
  • Paste them into a new paste on pastebin
  • Create a paste
  • Copy the URL created
  • Paste the URL into your reply
  • Highlight the URL you just pasted
  • Click the </> button in the toolbar above the reply box ^ to render the URL unclickable (so you can post it without having to break it)

I can then review the log and see if there is something else to suggest.

I am having this same problem off an on ever since I got the expansion. I would love a fix.

Just started having this problem with latest patch. Freezes at “logging into Diablo IV” screen. Killing the game and retrying usually works.

Even that has stopped working for me. Not really sure what else to do.

Im locked out now today 12-10-24. No idea why. Was random crashing when playing for long periods. No just gone.

it appears to be better now… can anyone confim?

This problem went away for me for a few days, but today is back with a vengeance. Can’t get in at all this afternoon.

Ive had this same problem since the mid season patch. freezes/locks up at the last logging into screen 99% of the time with a rarity of getting in to play . Some help please would be great. TY
update @ 12/16/24 the issue persists with a vengeance, Last logging into screen appears music plays then music quits nothing happens game is frozen.
also have issues with battlenet loading the “GAMES” screens, but that is getting better down to about 50% of the time.
seriously ive been dealing with this since mid season some HELP please Blizz.

Same here…gets to the logging in screen then freezes…not like the devs havent had time to fix this…