Good find, I can also make it work if I set
[ FirstTimeFlowCompleted “1”
Which means some tedious settings must be redone each time, but it is reliable.
This still is not fixed. None of these worked for me. I’m sad and frustrated that i bought the expensive version of the expansion. Cannot get my money back it seems so instead i will just give up on Blizzard and cancel my other subs. Will take the money back that way. Bye!
March 30 I had the same problem and with the -disableds command it started perfectly in less than 1 minute thank you very much.
Been having this problem on and off for a while. Sometimes it would get past the login screen after a couple of tries, but sometime I would be killing D4 over and over with no results.
The extra commandline arguments did not seem to help. I’m on an AMD GPU, so can’t be NVidia issue either.
Someone in this thread suggested to let the “Vessel of Hatred” into video play out (which only takes a few seconds anyway) and for some reason that seems to help. The last couple of times, I let it play out, and the game logged me in within seconds without a hitch.
I’ll report back if it starts crashing again, but for me that seems to fix the issue. I would guess there’s something loading in the background that’s interrupted or not finished when you skip the cinematic. If so, they probably have a race condition in their resource loader.
it happened with me too. since yesterday small new patch, i got difficulty to log in. said to check my connection.
+1. MeToo.
(Partial solution found).
Happened after I changed my PC platform (CPU+MB+RAM).
Moved OLD NVMe drive with old Win 11 installation to lower M.2 slot (connected not to CPU but to chipset). Everything worx fine EXCEPT Diablo 4 which freezes of “Loging into Diablo 4” always.
SOLUTION found (partial) - i moved the whole Diablo IV installation folder from ProgramFiles (x86) to external drive (and pointed Battle.Net App it’s new location) and it worx fine now. Putting it back to initial location makes it freeze again.
Any consideration, fellows?
I wonder what kind of bug is that that game freezes depending on the location of the installation folder! Maybe it really has something to do with DirectStorage ?
UPD: Stupid me! -disableds sommand line key worked fine, thank you!
Would gently assume the lower layer of problem is that now my SSD M.2 drive is secondary M.2 slot, connected via B760 chipset, not in the first one, connectded directly to CPU.
UPD2: I reassembled my old platform (9600KF/Z790 MSI Ace) and - YES! - on the old platform D4 worx fine without “-disableds” key! Yes, usability of DirectStorage IS dependant on the hardware (or BIOS settions. or drivers).
Game might not like some drives or drive configs, hence why the -disableds command works.
I run a Kingston Fury Renegade 1TB Gen 4 SSD. Thing runs near to the top of the speed limit for Gen 4 and it hasn’t given me any issues.
However.
Direct Storage will not load on it, despite being compatible and not disabled with that command. So it may be that its simply not running on my system, even though everywhere I have looked for it, it should be running.
I haven’t bothered with fixing it, since the game plays perfectly fine regardless.
This is happening to me as well. I tried as many workarounds as I could (don’t dismiss the videos, reset my settings, disableds, tweak various video settings) and none of them helped. I didn’t try moving the game to external USB storage though.
What many of these workarounds seemed to have in common was they all delayed the connection to the server, so what if it was trying to connect too soon? These cherrypicked entries in FenrisDebug.txt caught my attention:
I 2025.04.14 15:05:42.773064 142 [BgsClient] BgsConnection: connected. | connection_index: 0 | connection_id: 1
I 2025.04.14 15:07:10.276061 215 [Game] [SNOPreload::InitializeAfterLogin] Waited for SNOs: 78273.09 ms
I 2025.04.14 15:07:30.094316 218 [BgsClient] BgsConnection: disconnected. | connection_index: 0 | connection_id: 1 | bgs_error_code: 1016
I 2025.04.14 15:07:32.845054 240 [BgsClient] BgsConnection: connected. | connection_index: 0 | connection_id: 2
I 2025.04.14 15:07:33.219343 243 [BgsClient] – CAuthHandler::OnExternalChallenge() - Aurora has rejected the token.
It looked like the first connection timed out while waiting for whatever “SNOs” are, and the reconnect attempt failed due to an Aurora error. So I came up with a way to delay the initial connection attempt and give more time for those “SNOs” to load before the timeout clock starts ticking. It seems like there’s a bug in the reconnect flow, so I wanted to avoid it.
What worked for me with 100% success is this ritual:
- Launch the game.
- Immediately after the game opens, firewall off all TCP traffic outbound to port 1119. Make sure the packets are dropped silently, otherwise you’ll get the error “Unable to connect to Battle.net. Please check your network settings. (Code 1016)” The goal is to delay the connection attempt, not to cause it to fail.
- Wait for the splash screen videos to play.
- Wait an additional 10-15 seconds or so. But don’t wait too long or the connection handshake will time out.
- Remove the port 1119 firewall rule.
Here are the logs from a successful attempt where I removed the firewall rule 10 seconds after the splash screen videos finished:
I 2025.04.14 15:23:37.760874 233 [BgsClient] BgsConnection: connected. | connection_index: 0 | connection_id: 1
I 2025.04.14 15:23:54.324166 304 [Game] [SNOPreload::InitializeAfterLogin] Waited for SNOs: 7605.75 ms
This time there was no disconnect/reconnect.
I was excited to see a new expansion had been released while I was away, but I’m going to hold off on buying it until the game is playable without workarounds like this.
I still think some of these problems relate to location and pathing, ISP used, network hardware in-between and incompatibility with some networking protocols that Blizzard is using for this game.
Keep in mind, this game is trying to instance different towns, areas and events across the entire planet at once.
You can be connected to different servers in different parts of the country at any time while playing the game.
It relies on trying to figure out where you are in the world and connecting you to what the game thinks is the best place for you to connect, but this probably fails more than one would think.
This is why VPNs sometimes magically fix issues, or why changing an ISP can resolve a problem.
Times where one router causes issues, but another doesn’t, or hardwire connections work better than a WiFi connection, stuff like this.
The game is simply too fussy at times.
That all said, I personally don’t run into these sorts of issues, unless its a larger scale outage or my own ISP is having an issue.
But I hate that so many do. Just wanted to frame it a bit as to why these can affect some players, but not the majority of players.
I had the same issue when I tried to log in tonight. I simply deleted the LocalPrefs file located in ‘Documents/DiabloIV’, and it’s been working since then. It can still be a bit of a struggle to connect, but it does go through eventually.
Still, it’s hard to believe something this dumb hasn’t been fixed by now—then again, it’s Blizzard, so I guess it’s not that surprising anymore.
new season, still the same problem