:1119/Agent 404 Error

Desktop App Tech Support
1

I am unable to install Battle.net due to the update agent. The update agent is clearly phoning home to the :1119/agent URL and getting a 404 error. This can be seen in the error logs the update agent itself provides.

[I 2025-05-08 12:30:09.0771] Agent started as Administrator
[I 2025-05-08 12:30:09.0772] Argument[0]: ‘–locale=enUS’ Argument[1]: ‘–session=11795012531142929377’
[I 2025-05-08 12:30:09.0781] Attempting to read local game data and states from ‘C:/ProgramData/Battle.net/Agent/product.db’
[W 2025-05-08 12:30:09.0782] Failed to read Install Info from ‘C:/ProgramData/Battle.net/Agent/.build.info’
[I 2025-05-08 12:30:09.0794] Handle Event: “update agent event” [I 2025-05-08 12:30:09.0794] Handle Event: “version refresh event”
[I 2025-05-08 12:30:09.0794] Checking Network Connection status to [http us patch battle net](http us patch battle net/):1119/agent
[I 2025-05-08 12:30:10.0030] Network Connection Response to [http us patch battle net](http us patch battle net/):1119/agent - CURL error: 0, Status Code: 404
[I 2025-05-08 12:30:11.0306] Executing operation: emergency_fix_com_flags ClsId=257A53D9-0BBB-476B-9500-A888092E0260 AppIdFlags = 0
[I 2025-05-08 12:30:11.0307] No registry key at ‘HKEY_CLASSES_ROOT\AppID{257A53D9-0BBB-476B-9500-A888092E0260}’
[I 2025-05-08 12:30:11.0307] Executing operation:validate_helper_service

How do I troubleshoot the agent 404 error? I got a 404 error when I went to the url as well so it does appear the agents are phoning home to :1119/agent and not getting the expected response.

PS: I had to remove all of the URLs from the agent logs because I literally can’t post URLs in this forum.

2

I’m getting a similar error. I tried completely uninstalling Battle.net, clearing out the folders, etc, but still get the same error. It’s like the launcher just decided to corrupt itself and nothing will fix it.

3

Ok, I can’t post links in this forum, but another other thread solved the issue for me. I had to restart a winmgmt service and reboot. If you google for "Resetting the WMI Repository
" you might find a related article. See if it helps.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.