My Battle.net is regularly stuck in UPDATE mode. If I click on it, it complains it can’t be done.
The solution is to kill Agent. I do a Force Quit from Activity Monitor.
But I have to do this most every day.
Its functional, but tedious, and shouldn’t be happening.
2020 iMac, Sequoia 15.4.1
Routinely killing Agent is also advisable because it appears to have a memory leak and will balloon in usage over time.
I am having the same (or a similar) problem. Battle.net says it needs to update WoW despite being configured to automatically install updates. When I click the update button, it tries, then says it can’t download the update and I should check my internet connection. At the same time, it accurately shows me which of my friends are online, so it’s obviously not having any issue with the internet.
When I first looked into the issue, it seemed like file permissions were a likely culprit, so I tried running Disk Utility’s first aid. That did find an issue and was unable to fix it, so I decided to erase my HD and restore from a backup. That fixed whatever Disk Utility was finding, but the WoW update issue persisted.
My solution has been to delete /Users/Shared/Battle.net/Agent every time it happens. That solves the problem for several hours.
Quite annoying.
tim apple help there is an agent on my computer
ok serious answer. the launcher doesnt work very well on mac. opened activity monitor now and agent isnt open at all despite the game running. I set the launcher to close after game boots. presumbly you can just kill the secret agent
Killing Agent is required if the client fails an update. Yeah, the memory consumption is ridiculous the longer it runs.
This is a problem I have been having around once a week or so, usually on my nights off work, for a month or two. I took some steps to try and fix it, deleting the Agent folder, then the Battle.net folder. It should be reinstalling those when I try to launch the game. But it’s halting at 5% downloaded, every time, and Blizzard Support said I should ask here, because they don’t know.
Okay, after a few days of launching WoW, and Battle.net wouldn’t fix itself, I tried clicking on Starcraft 2, and that worked. So now I can play WoW again. The darnedest thing.
Nova to the rescue! Why didn’t I think of tactical nuking my Mac…“just to be sure”.
I’ve found that quitting battle.net for a few minutes fixes it… but what a pain.
As mentioned somewhere in the Forums some while ago, if you kill Battle.net, open Activity Monitor (a good thing to have in your Dock), select the “CPU” tab, and order the display by Process Name, you should see the Blizzards Agent process (with a familiar icon). Wait for it to disappear (somewhere around 15 seconds after exiting Battle.net), then restart Battle.net, and Bob should be your uncle… until the next time.
So, my current mitigation for this was to create a script that kills the Agent. Then I created a launchd config that runs it every 15 minutes.
The end result is that I often come back to an UPDATE button, but at least when I press it, it actually updates vs forcing me to hunt down agent myself.
I’m not going to flag this as a “solution”, because it doesn’t solve anything, just makes the whole process this ][ much less painful.
Its hard to express how much this saddens me. Battle NET used to be a rock on my computer. Launch once at boot, stayed alive, stayed logged in, painless background updates. For weeks and months. Just that happy helper quietly humming in the background.
But not now. Now I’m constantly getting logged out, this agent thing, none of the updates happening without, figuratively, pulling teeth. Now it’s always in my face.
It’s just…disappointing.
This bug happens constantly for me. Its quite annoying having to quit the Launcher each time.
So, as a follow up, I routinely come back to my machine with a dialog saying something “Oops, looks like something broke or crashed, you might want to restart BNET”.
But, I just click OK, it goes away, and I can click on the UPDATE button and have it update. So, so far it’s a net win for me.