Issue: Tried to launch game but got “Agent asleep” and couldn’t access any games; shop was still available (you can buy, but can’t play)
Short answer: Agent.9124 cannot connect to the patching location (Network Connection Response to http:// us.patch.battle. net:1119/agent - CURL error: 0, Status Code: 404) even though previous versions and other computers on the same network are able to. Discovered there were WMI errors (in battle net agent logs and then in computer) and ran fixes for mof files. Issue Resolved
Long detailed troubleshooting/analysis…
Troubleshooting:
Lots…but ended up:
- Deleting all battle.net folders and registry keys to do fresh install
- Fresh install attempted and install hung at updating Agent (45%) before crashing with BLZBNTBNA00000005 error like lots are having
- Tried this a few times with no success (with reboots in between steps)
------tried wire to router
-----------before and after refreshing config/flushing DNS
------tried wireless to router
------tried through mobile hotspot (mobile device not connected to local wi-fi) to validate if this was a DNS issues - Battle.net works for other computers on the network
- Tried coping battle.net files from working computer to non-working as I saw this in a post (tied before and after restoring registry entries from earlier saved copy)
- Tried changing languages (another post)
- Disabled AVS
- Removed AVS, switched to defender
- Avoided WMI (for now)
- Tried sleeping
- Tried again no luck
- Downloaded procmon to get more info
Current analysis:
- After running proc mon, noticed the latest version of battle.net was using Agent.9124 (which I saw in another post may be a bad version)
- Procmon showed me that the location of the logfiles so I checked those
Saw this: “Network Connection Response to http:// us.patch.battle .net:1119/agent - CURL error: 0, Status Code: 404” - Hmmm, 404 error, page not found…ok, so agent is unable to reach that location; since other systems on same network can, it must be local to my machine
- Went in and manually added firewall rule for agent.9124 to match other firewall rules for other agents that were still in there (2 rules per agent TCP & UDP)
- Ran installer again, still failed
- Revisted procmon and noticed when it failed it was continuously trying the following three things over and over and over
---------a) CreateFile \Battle.net-Setup.DEBUG
-------------------Result: NAME NOT FOUND
---------b) CreateFile \Apps\Battle.net\Agent\Agent.exe
--------------------Result: PATH NOT FOUND
---------c) CreateFile .htpasswd
--------------------Result: NAME NOT FOUND - Moved the install file from a secondary drive to the c:\ drive and ran again with the same result
- Ran again as Administrator (I’ve done that a few times above); same result
UPDATE #1:
Looked into a few more of the logs and in one of the telemetry-sdP logs noticed there were failures to execute WMI queries for Win32_Operating System (I’m on Windows 10 PRO).
Checked WMI Control (Computer Management → Services and Applications → right click WMI Control and select properties) and noticed errors:
-
Failed to initialize all required WMI classes.
-
Win32_Processor: WMI: Invalid class
-
Win32_WMISetting: WMI: Invalid class
-
Security information: Successful
-
Win32_OperatingSystem: WMI Invalid class
Well, shoot, appears to be WMI afterall. There are some posts on the topic here. I followed this article since the errors seemed to be the same.
Ran winmgmt /verifyrepository to validate and it came back as “consistent” but obviously there was still an error.
Came across this post external to Blizzard which had the same issue and looked like it address mof files so followed the instructions there:
https:// learn.microsoft. com/en-us/answers/questions/684166/failed-to-initialize-all-required-wmi-classes
Re-ran the installer as administrator and it finished install successfully. Was able to successfully log in.