Recently, my Battle.Net Launcher somehow lost the location of all of my games. I had to go in and relocate each of them and it was fine, except for World of Warcraft. I had WotLK and retail installed but it still could not locate either one even after manually pointing it at the file location.
In order to play, I’ve tried to reinstall the game. However, I’m running into more issues.
No matter what I’ve tried I cannot get my launcher to actually install the game. It hangs on “Initializing (2159810/2159810)”.
Things I have tried so far:
Restarting my computer
Checking for Windows update
Restarting Battle.net Launcher
Running Battle.net Launcher as admin
Running Battle.net Update Agent as admin
Installing in new directories
Uninstalling and Reinstalling Battle.net Launcher
Disabling all anti-virus/malware services
I will continue to troubleshoot and reply if I find a solution, but if anybody has something else I can try, I would be very appreciative
Make that two people stuck at the exact same initializing sequence.
Digging through some older posts that dealt with the same problem (w/different details) I came across one mentioning the download manager attempting to perform an update at the same time. Which is exactly what’s happening with mine, and I have it set to never auto update. Yet, it’s doing so anyway.
The download reached 689 mb then stalled in this loop.
I have done each step+ deep cleaning, etc to no avail.
I should note that the first time I attempted the install I hadn’t checked for a Nvidia update prior. I did after the first failed download attempt & there was an update, which I did. There’s no relevance; just wanted to cover semantics for inquiring minds.
Update, after finding I have the steam client, Discord etc running in the background (Systray) I exited them both restarted Battle.net client now I’m installing finally past being suck.
Are you on windows 11? try updating the “optional” updates for windows, and making sure you don’t have any razer processes (the mouse software) running in the background
You could try going to into run>msconfig>boot>safe_boot + networking box checked
I fixed this as well. Using procmon I was able to see the Agent.exe application attempting and failing to connect to an internal kubernetes cluster (I think just docker) that they apparently are using to manage the downloads.
I set Docker Desktop to not launch on setup and rebooted, and the download was able to proceed.