Same problem. It seems to be an issue with the battle.net app. TBC Classic runs fine by right click and Open /Applications/World of Warcraft/classic/World of Warcraft Classic.app
Hi all, my ticket was answered and they said that this is a known issue with bnet that their Q&A department are working on. They pointed me to this thread also to keep up with updates:
WoW won’t update - Support / Mac Technical Support - World of Warcraft Forums (blizzard.com)
I am currently having the same exact issues! I am on Mac. This has never been a problem before today.
1 Like
I’m having this issue on macOS 12.0. Things were fine yesterday
When I launch the bnet app, theres a popup asking for permission for Agent to make changes. Entering my password still does not let bnet update WoW and gives the BLZBNTAGT00000841 error.
Please fix ASAP
Here’s what fixed it for me. Go to:
Application > World of Warcraft > _retail
There is a separate WoW launcher (an icon called World of Warcraft) in there that bypasses Battle.net and opens the game directly (without updating with the patch).
Hope that helps.
2 Likes
I just installed the latest desktop launcher that showed up, but it does not fix the problem. Tried on two computers.
1 Like
Same issue here on my MacOS, so frustrating as the name reservation on Classic SoM already started and I can’t log in. Some logs below
default 17:13:37.006006+1300 talagent - -: TAL launch still in progress because net.battle.app is unstopped (yes) and/or unhidden (yes)
default 17:13:37.006033+1300 talagent - -: Still waiting for registration from net.battle.app, com.apple.Safari, com.googlecode.iterm2
default 17:13:38.504753+1300 talagent - -: TAL launch still in progress because net.battle.app is unstopped (yes) and/or unhidden (yes)
default 17:13:38.504786+1300 talagent - -: Still waiting for registration from net.battle.app, com.googlecode.iterm2
default 17:13:38.967364+1300 lockoutagent Requesting policy for bundle IDs: (
“com.apple.systempreferences”,
“com.apple.finder”,
“com.apple.Safari”,
“net.battle.app”,
“com.apple.Console”
)
default 17:13:40.342426+1300 backgroundtaskmanagementagent SecTaskCopyDebugDescription: Battle.net[370]/0#-1 LF=0
default 17:13:40.448307+1300 talagent - net.battle.app: Registered as TAL ready
default 17:13:40.480246+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.482911+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.503840+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.536572+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.540095+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.613276+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.615736+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.620397+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.623294+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.645996+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:40.661823+1300 Agent Trust evaluate failure: [leaf TemporalValidity]
default 17:13:46.957218+1300 Agent _LSLaunch(’’)
default 17:13:46.958690+1300 Agent LAUNCHING:0x0-0x3a03a Agent foreground=0 bringForward=0 seed=104 userActivityCount=0
default 17:13:46.964737+1300 Agent OSStatus _LSLaunch(LSContext *, FSNode *, LSLaunchFlags, void *, CFArrayRef, const AppleEvent *, const AEDescList *, CFArrayRef, CFDictionaryRef, LSBundleID, const audit_token_t *, const _LSOpen2Options *, ProcessSerialNumber *, Boolean *, NSError **): launching ‘’ result=0
default 17:13:57.978048+1300 Agent LSExceptions shared instance invalidated for timeout.
default 17:14:16.984092+1300 Agent FRONTLOGGING: version 1
default 17:14:16.984102+1300 Agent Registering, pid=533
default 17:14:16.984256+1300 Agent CHECKIN: pid=533
default 17:14:16.991837+1300 Agent CHECKEDIN: pid=533 asn=0x0-0x2d02d foreground=0
default 17:14:16.998558+1300 Agent Registered, pid=533 ASN=0x0,0x2d02d
default 17:14:16.998644+1300 Agent Registered, pid=533 cgConnectionID=8936f
default 17:14:17.999536+1300 Agent BringForward: pid=533 asn=0x0-0x2d02d bringForward=0 foreground=0 uiElement=1 launchedByLS=1 modifiersCount=1 allDisabled=0
default 17:14:17.999663+1300 Agent BringFrontModifier: pid=533 asn=0x0-0x2d02d Modifier 0 hideAfter=0 hideOthers=0 dontMakeFrontmost=0 mouseDown=0/0 seed=0/0
default 17:14:27.003011+1300 Agent LSExceptions shared instance invalidated for timeout.
default 17:15:34.390036+1300 Agent _LSLaunch(’’)
default 17:15:34.390384+1300 Agent LAUNCHING:0x0-0x46046 Agent foreground=0 bringForward=0 seed=113 userActivityCount=0
default 17:15:34.394654+1300 Agent OSStatus _LSLaunch(LSContext *, FSNode *, LSLaunchFlags, void *, CFArrayRef, const AppleEvent *, const AEDescList *, CFArrayRef, CFDictionaryRef, LSBundleID, const audit_token_t *, const _LSOpen2Options *, ProcessSerialNumber *, Boolean *, NSError **): launching ‘’ result=0
default 17:15:44.387919+1300 Agent LSExceptions shared instance invalidated for timeout.
Who changed things today? Call them back to work and make them fix what they broke. i was on os11 but updated to 12 and nothing changed… because this is a YOU problem
1 Like
I can’t update shadowlands and because of that I can’t log in! If I am not the only one with the issue that means the problem must not be our Macs a connection failure somewhere, something similar happened with some banks today because of that no-one who gets paid through direct deposit got paid!!
all though i can’t scan nor repair either!!
Things would be better if they had a phone number we could call them! They need to put the phone service back!!
Same issue, Followed instruction for deleting Battle net agent files to no avail. Might try direct login with out going through battle net client.
hopefully they have a fix by Friday evening.
did all of this on windows 10 and still nothing i was playing fine on shadow lands to day but not after trying to do update
I am facing the exact same issue on windows, i am also facing a problem at the same time with the Battlenet Authentificator that is not working anymore only by SMS it works. And if i go into Battlenet.eu to account settings i will receive and 505-error code. so i think all of those are related.
Same issue with WoW, Mac OS 12.0.1. Except that direct launch through launcher won’t work either, because that has been broken for a week. Tried everything recommended on the blizzard site, including reinstall of battle.net app.
Update: I did a full root delete of WoW, then downloaded the full 72 GB again. Game started up the first time I tried it from battle.net app. Then I closed the game, and am back to square 1. Error 154 when I try to start from WoW launcher, admin error from the app.
Next time I uninstall I’ll leave it uninstalled.
3 Likes
Still the same issues with SC2 Win10 EU, tried a few methods posted here or on other threads.
Ticking full control in permissions/security on the sc2 folder in docs is not working as when battle net app starts they are being reverted - I had something like fake battle net update, then for a while there was battle net sleeping notification/error, then it came back to stuck updating SC2 - and here I’m back at start position with full control in the folder being unticked.
Same here, Admins! I thought my PC stuff or something. Just for SC2.
Was able to successfully update my BroodWar game and launch it.
I was trying to reinstal/clean cache, etc for Battle.net but didnt work. Then I tried to reinstall my SC2 but after uninstall I cant even install it back due to the same admin issue…
Please, fix this ASAP
Battle Net just update to 2.7.0.13177 Update Agent 2.25.2.7581 and restart
I was hopping but I was wrong… Same issue…
Some dev’s will go late in weekend to night
Possible solution, could somebody please verify?
I found that in my case the folder “HD/Users/Shared/Battle.net/Agent” contained two “Agent.75**” folders, both containing an Agent app and a Logs folder. I double-clicked the older Agent app, then started the battle.net app. Suddenly it works.
Not sure if it was my doing, or if the error was on Blizzards side and they changed something, but if you still have the same problem, please check if this solution works for you. (If it doesn’t, I’ll delete this post. No use sending people on a wild goose chase.)
4 Likes
nope. didn’t work for me. M1 Mac mini