Well over half the time I launch the game it freezes while logging in, on the last step “Logging into Diablo 4”. Going back through bug report history, it appears this has been a recurring issue for a long, long time and while previous hotfixes were supposed to address it, it’s still a frequent occurance.
4 Likes
I’ve been playing since release and every season with the exception of one and this just started happening to me today for some reason. I have to kill the process in task manager and keep trying until it works.
This has been happening to me for about the last 2 months. My frustration level is very high. Is this widespread? It seems odd that this just started for me after having virtually no problems with login prior to that time.
Happened to me last season, googled it and it got fixed after I did what the posts said
Been able to play once this season and keep getting the disconnect message.
I am not happy about this.
This is strange, and no idea why it works, but I have this same issue and have found that if I start the game and then switch to a different application it loads fine. If I leave it on D4 it freezes at the login screen.
This started happening to me after the last patch of season 6. Usually I can get in after ending the task and retrying. Just now it took me 5 tries to get in. Some rather glaring bugs just never seem to get fixed.
Same issue here. Uninstalled and Reinstalled the game, same issue happens. delete the localpref text file… same issue will reoccur on next launch.
The workaround that works for most people is: Don’t skip the “Diablo IV: Vessel of Hatred” flying logo. You can skip the Blizzard one, but you have to let the next one play all the way through. Then the login lockup doesn’t happen. It doesn’t make any sense, but it’s been working for me and a lot of people in the technical support thread about this.
Nothing else I’ve tried works consistently, and considering that simply doing an End Task and then relaunching the game works a lot of the time, I don’t think those other workarounds were actually doing anything. But, every time I let the Diablo IV flying logo animation play in full, I get in. If I skip it, probably about 80% of the time it locks up at login.
Given how long this bug has been around and how it seems like there have been no attempts to fix it, I think Blizzard just doesn’t care.
1 Like
Many _FenrisDebug-#.txt files exist in the Diablo IV folder that show the error, but only Blizzard would know what the errors mean.
|I 2025.02.04 07:28:53.992073 999|[Game] bgs Connecting to prod.actual.battle.net:1119|
|---|---|
|I 2025.02.04 07:28:55.741610 1013|[Interface.BgsLow] I 07:28:55.741600 [BGS] |event=Connection metering enabled.|connection_id=2 (C:\Fenris\shared\Contrib\bgs-sdk\8.2.1\src\low\core\connection_handler.cpp:263)|
|I 2025.02.04 07:28:55.741625 1013|[Interface.BgsLow] I 07:28:55.741621 [BGS] |event=Connection to Battle.net ready.|connection_id=2|address=prod.actual.battle.net|port=1119 (C:\Fenris\shared\Contrib\bgs-sdk\8.2.1\src\low\core\connection_handler.cpp:283)|
|I 2025.02.04 07:28:55.741630 1013|[BgsClient] BgsConnection: connected. | connection_index: 0 | connection_id: 2|
|I 2025.02.04 07:28:55.741634 1013|[Online.Systems.CAuthSession] StartSilentReconnect: Connect callback | client_user_id: 0 | bgs_error_code: 0 | bgs_connection_id: 2|
|I 2025.02.04 07:28:56.116284 1016|[BgsClient] -- CAuthHandler::OnExternalChallenge() - Aurora has rejected the token.|
|I 2025.02.04 07:28:59.241285 1041|[Online.Systems.CUserProxy] Attempting to find and connect to user proxy | client_user_id: 0|
|I 2025.02.04 07:28:59.366330 1042|[Online.Systems.CUserProxy] GetContentLicenses - Find user proxy | num_licenses: 0|
|I 2025.02.04 07:28:59.741269 1045|[BgsClient] ProcessClientRequest RPC failed | bgs_error_code: 3025 | request: bgs.protocol.game_utilities.v2.client.ProcessTaskRequest { attribute { name: fenris_message_id value { uint_value: 0 } } attribute { name: version value { string_value: 2.1.0.61504 } } payload { name: fenris_message_payload value { blob_value: \334\257\331\243\201\253\373\002*$1641ce50-e2c9-11ef-9c37-a50a9bee41242\007us-west:@_\210\333(!\\;7<$\237\272\201\317\251\261\346\225\270\215\335Z\022\244{\366\244\226\205\277\2712\363}O\006\346\370y)\357\375P\265Xd\322Q\315\207N\305;x\177\023W_\246$s\255x\215P\001 } } }|
|E 2025.02.04 07:28:59.741321 1045|[Online.Systems.CUserProxy] Failed to send find user proxy request via BGS | bgs_error_code: 3025|
|I 2025.02.04 07:28:59.741443 1045|[Interface.BgsLow] I 07:28:59.741430 [BGS] |event=Disconnected|method=OnDisconnectComplete|address=prod.actual.battle.net|port=1119|status=3025 (C:\Fenris\shared\Contrib\bgs-sdk\8.2.1\src\low\core\connection_handler.cpp:245)|
|I 2025.02.04 07:28:59.741451 1045|[BgsClient] BgsConnection: disconnected. | connection_index: 0 | connection_id: 2 | bgs_error_code: 3025|
This bug was hitting me until the Feb 4th patch. My workaround was even stupider than the “click/don’t click” one but was 100% reliable. I had to edit the LocalPrefs.txt file and remove some lines before launch. If I did that 100% reliable… without it I launched 1 time in 10 or 12.
But the bug was caused by a race condition and I have no idea if the patch fixed or more simply moved it to somewhere else. More Blizzard clown show.
Confirmed still happening after today’s patch (not that there was anything in there even related to this).
Same problem, first time I have had this problem since launch
This problem is unsolved and my experience mirrors all those notes and attempts for work arounds listed above. None of the other Battlenet accessible games have this problem. Only D4. Please fix or post a plan. Please.
add me to the club. Clrt+Alt+Del keys are melting.
1 Like
Ditto here.
Wonder when the letters are going to start wearing off my keys.
Clearly no attempt has been made to correct this issue, as it has been happening for me the last two weeks. Will give the “watch VoH marquee” a try and see if I can get in. Sometimes, ctrl+alt+del works and I can get in after one reset, sometimes it never works and I reset my computer, and now that doesn’t even seem to help. Perhaps instead of Blizzard gaslighting me into it being a user error, they can review the debug reports and provide a real solution to this problem. Or I will go back to college (again), get a computer science degree, and learn how to fix the code myself. Probably a faster solution.
This is a problem with me currently. I have to end game with task manager and keep trying hoping it works. ive tried to watch videos to find a fix but i cannot find one.
happens to me also, i have to do the same, always on first login it freezes.
This problem is back with a vengeance. First appeared (for me) during a patch last December. Has sometimes been rare for a while, but since this patch it usually takes me 2-3 times to get past logging in. Have to kill the app and restart. Today I had 4 minutes to get in in time for a world boss and couldn’t get in in time. This is looking like one of the many annoying bugs that they just don’t ever bother to fix (or don’t have the talent to fix).
Bug still isn’t fixed.