Unable to log into Cata Classic/Bnet launcher broken

I have tried the methods in https://us.forums.blizzard.com/en/blizzard/t/battlenet-update-agent-hangs-at-45/51546/5

  1. delete C:\ProgramData\Battle.net
  2. delete C:\ProgramData\Blizzard Entertainment\Battle.net
  3. delete C:\ProgramData\Battle.net_components
  4. delete C:\Program Files (x86)\Battle.net
  5. delete C:\Users\<MY_USER>\AppData\Local\Battle.net
  6. delete C:\Users\<MY_USER>\AppData\Roaming\Battle.net
  7. delete registry key Computer\HKEY_CURRENT_USER\SOFTWARE\Blizzard Entertainment
  8. Run Battle.net installer

I do not run an anti-virus - I have disabled windows defender - I have ran all available updates on my PC. I can get wowclassic.exe to launch and I get to the login screen and am stuck at “connecting”.

Have rebooted my router and PC numerous times, I have changed my DNS settings from 1.1.1.1 and 4.2.2.4 to 8.8.8.8 and 8.8.4.4 to see if its a DNS issue.

In the agent logs I am getting the following errors “[I 2024-11-11 22:28:42.0832] switcher argument[0]: ‘–locale=enUS’
switcher argument[1]: '–session=3557988632080580687”

Trying to manually uninstall WoW and all of its related folders I am getting the following errors -

"I 2024-11-11 22:51:00.978245 [Main] {4590} Logging started for Uninstaller 1.18.6.106
I 2024-11-11 22:51:00.978301 [Main] {4590} Initializing Uninstaller UI, uid=wow; locale=enUS
W 2024-11-11 22:51:01.018750 [Main] {26e0} Transport changed to CURL
I 2024-11-11 22:51:01.064340 [Main] {26e0} Agent opted into beta successfully
E 2024-11-11 22:51:06.019596 [Main] {4590} Timed out waiting for Agent!
E 2024-11-11 22:51:06.019655 [Main] {4590} Uninstall error reported, code=6
I 2024-11-11 22:51:06.022648 [Main] {4590} Showing screen: screen.uninstall_error
I 2024-11-11 22:51:07.656058 [Main] {4590} Closing Uninstaller…
D 2024-11-11 22:51:07.656563 [Analytics] {4590} Analytics request sent. type=Blizzard.Telemetry.App.Uninstaller
I 2024-11-11 22:51:07.681819 [Main] {4590} Shutting down Uninstaller…
"

Tried these steps and it did not correct the problem still -

1:Press Windows+Q and type cmd into the search bar that pops up.
2:Right-click on Command Prompt and select Run as Administrator
3:Type net stop winmgmt into the command prompt and press enter.
4:When prompted if you wish to continue, type Y and press enter.
5:Type winmgmt /resetrepository into the command prompt and press enter.
6:Restart your computer to pick up the changes

Switched to hopspot and was able to download battle.net but when I switched back to primary ISP I am not stuck on “connecting” on battle.net

Tracing route to us.battle.net [137.221.106.102]
over a maximum of 30 hops:

  "1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     1 ms    <1 ms     1 ms  155.254.201.1
  3     4 ms     3 ms     3 ms  10.1.255.5
  4    10 ms    10 ms    11 ms  ip-64-146-225-73.noanet.net [64.146.225.73]
  5    12 ms    10 ms    10 ms  six.blizzardonline.net [206.81.81.122]
  6    41 ms    41 ms    40 ms  ae1-br01-eqse2.as57976.net [137.221.73.33]
  7    44 ms    41 ms    42 ms  xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
  8    39 ms    40 ms    41 ms  et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
  9    41 ms    41 ms    41 ms  et-0-0-4-br02-eqla1.as57976.net [137.221.65.6]
 10   141 ms   379 ms   597 ms  et-0-0-29-br01-eqla1.as57976.net [137.221.65.0]
 11     *        *        *     Request timed out.
 12    40 ms    39 ms    55 ms  et-0-0-0-pe03-swlv10.as57976.net [137.221.83.85]
 13    40 ms    40 ms    40 ms  las-swlv10-ia-bons-03.as57976.net [137.221.66.21]
 14    41 ms    41 ms    40 ms  137.221.105.25
 15    40 ms    40 ms    40 ms  137.221.106.102"

Trace complete.

So your ISP route to Blizzard is probably having issues, but the hotspot provider is not. Unfortunately, that means speaking to the ISP. You’d say something along the lines of: “I can’t connect to services in the US over my internet connection, but I can with my phone, so it’s a problem with the ISP service.”

Make sure when you’re trying to close down the Agent process, you’re shutting down the computer for a few minutes, then rebooting. Simply rebooting may allow some processes to continue running.