I am now expirencing this as well, it was working fine yesterday. Now to day stuck there at “Logging into Daiblo 4…” I am on PC I have tried everything that is recommended here and that I have found on the Internet on the issue nothing works. Even uninstalled and re-installed the game.
Nothing works, how can we fix this?
Same issue. Intel CPU, NVidia Card, 64gb RAM, NOT a WD SSD. Eventually I will get in but often takes 4-10 times of forcing the app closed and retrying and takes about 3-4 minutes of waiting before I do to realize it’s going to fail.
If I wait it out it eventually says “Reconnecting to Diablo…” and then the app closes completely back to desktop.
One other item, I looked for any type of log but could not find anything that indicates error or issue.
Happens to me too. NVidia card here, if it matters.
Hi, I seem to have fixed my own login freeze issues. I basically uninstalled everything Diablo 4, uninstalled the PTR realm I still had and I went into my drives, both internal and external and deleted every D4 related folder. I did a full fresh reinstall overnight with High Resolution textures enabled to download too. Having no login issues, my only issues now and stuttering still and exiting the game it decides to spaz out at times, but so far on all 4 attempts had no login freezes. Have no idea what fixed it but can only suggest people try that.
Are we all on Nvidia cards with this issue?
I’m not, I have an AMD RX 5500 XT with up to date software and whatnot. AMD CPU - Ryzen 7 2700X.
Thanks for chiming in! Seems pretty widespread…hopefully we get a hotfix soon.
I have found this solution from DTMace a few months back very helpful since it fixed it real quick:
It used to take like almost 3 minutes or so to logging in to the character select screen but inputting that in the command line made me login in like less than 5 seconds. If the OP of that solution/post (DTMace) could help maybe elaborate or explain what does this solution do or why it fixes this issue, I would love it and appreciate it very much (for my own curiosity, of course, since I was baffled on how it fixed my issue instantly, heh).
Well, not much to explain. The tech behind Direct Storage was to allow the programs to have direct control (or more direct access) to the storage device.
The problem arises in that not all parts are built equal…
You have different chipsets on the motherboards, you have different brands and models of SSDs, as well as different OS and driver versions.
All we are doing is disabling the game from attempting to use the feature to read/write to the drive. From a performance perspective, I doubt anyone would even notice a difference perceptively.
It won’t affect anything else, other games, or the system, but it can help sometimes.
Other ways to address it is to try to use different hardware, make sure drive firmware is up to date, motherboard drivers are using the latest offered by the manufacturer, not what Windows thinks is correct, things like that.
Yes, thank you so much for replying and explaining it 
Opened a ticket and in true Blizzard fashion was asked to check here to find a solution I hate NEW Blizzard so much.
I was so hopeful about this when I found the same thread and tried this morning, but unfortunately it did not work for me nor renaming that DLL to try and force the issue. There’s got to be something more / new here with S7. I remembered I had a Geforce Now sub, so I tried that earlier today and thankfully that works so I at least have a workaround sort of …
I turned on ray tracing through nvidia geforce and it “fixed” the issue idk, was having the same problem and this seemed to fix it for now for me at least.
Interesting. You would think the opposite would be true. RT is pretty hardware demanding.
Though all this does spark a thought.
Has anyone tried resetting their LocalPrefs file?
Its located in Documents\Diablo IV\
You can either rename it or delete it. But make sure you close out of D4 first. Then it will recreate the file and put you through first time config of the game settings.
Have any of you having this issue tried that?
This works but is only a temporary fix.
Renaming or deleting the file allowed me to log into the game. I had to redo my settings but was able to play the game. The problem that arose was the fact that after I completely exited the game, I tried relogging and was stuck with the original problem of the screen loading, freezing, and then the music cutting out.
I tested this process three times and the results were the same. So, for now, it seems that the only options are to wait for a patch fix or to keep renaming/deleting the file and redoing the settings each time to access the game. Here’s to hoping that the former will come, soon 
Having the same problem.
After the “Queued for login” window, “Logging into Diablo IV…” appears and then nothing more. The loading ring stops spinning and the cursor changes to the normal Windows cursor.
But the music is still playing.
I was still able to play last night.
I haven’t changed anything in my graphics settings since yesterday.
I have already tried client repair.
I had the same experience that Teriri below me had with this method. Deleting the LocalPrefs DID in fact let me back in, so you are onto something! But as soon as I fixed up my settings again, closed the game, and tried to go back in … freeze once more. 
But now it begs the question as to what about that works and why it won’t stick.
Oyi.
Wow, so I just had my first lockup even on GeForce Now cloud computer! That was how I played yesterday and this morning without issue. Then I had to quit out for a bit and trying again, freeze on “Logging into …”! It’s got to also / mostly be something on Blizzard side it seems like??
This still works for me as of 1/24/2025