Battle net tries to update WoW Shadowlands but the Agent fails to do so. Even with admin permissions, reinstall and chmod changes. I can not enter the game and this is a serious issue affecting a lot of people.
As mentioned in the separate US forums, I have the same issues
they posted a possible solution to this error in the US forum and there was also a possible solution posted in a german speaking thread in the eu forum.
You can try this solutions and hopefully they will work as they worked for me.
Iām also a Mac user affected by this issue. The problem with all the workarounds/solutions posted by users in the US thread is that none of them are permanent. If I reboot my Mac or quit and restart the Battle.net app then Iām back to square one.
Fortunately I can play WoW by bypassing Battle.net and running the WoW apps directly.
It seems youāve missed my mention on chmod. It does not work. I already checked the permissions for the complete directory, the shared agent and moved the application to my users folder to try circumvent any administrator privilege f*ck ups from the battle.net client but to no avail.
Iām running WoW via Wine and had the same problem on Ubuntu. Tried various proposed solutions on the US forums, including sudo chmod, with no success. Then I tried the one with the addons and it workedā¦ temporarily! My method is:
Open the Battle.net launcher and donāt exit it (minimising should be OK)
Move the AddOns folder to a folder outside of the install folder (keep it on the same drive so the operation doesnāt take much time).
Press the Update button in the Battle.net launcher and let it finish.
Move the AddOns folder back into the Interface folder.
Launch the game.
Not sure if it works for Macs but you should definitely try it if the other methods didnāt work for you.
Somebody has posted a fix which appears to be permanent on the US Blizzard Mac forum. In my case, the file was completely different but deleting it worked:
Find your agent apps. Users/Shared/Battle.net/Agent. There will probably be a few folders named something like Agent7531 and Agent7581
Open the Agen7531 folder and locate the Agent app in that folder, but donāt do anything with it yet. You just need to have it open now for below when it says āIMMEDIATELYā you need to double click (start) this app quickly.
Start Activity Monitor
Start Battle.net
After Battle.net starts, youāll get the error, close the error message
In Activity Monitor, find the Agent process and force quit it (select Agent and click the āxā in the upper left)
IMMEDIATELY double-click the Agent app in the 7531 folder
This may just be me, but Iāve found if I just ignore battle.net and instead go directly to the wow folder and navigate to the application itself then it will open as normal. Requires you to manually enter your login and authenticator details but no other problems. Playing classic generally so dunno if retail also opens that way without issue.
Tried everything excluding sudo and nothing worked. However, starting and then immediately stopping all updates in the Download arrow worked perfectly. Now I have 3 paused updates and see the button Play and can enter the game.
Edit:
I have even uninstalled and reinstalled the game, but STILL this happens. Also tried to locate different files etc that have previously been suggested, but with no successā¦ Please Blizz or anyone, help!
The chmod fix worked for me, but it does not seem to work for everyone.
In the meantime, you can launch the application directly and bypass the Battle.net app. In the absence of a fix this will work until the game needs updating.
Weirdly it was gubbed last Wednesday/Thursday but on Friday through the weekend it worked fine WITHOUT me doing anything to any files. But again today Battlenet keeps giving me an error message.
TBH I dont see why I should be messing about with files when the problem lies with Blizz, they need to get their finger out and sort it.
Exactly. Iāve seen a lot of people discussing āfixesā which mean people need to mess about with files they donāt understand when itās not necessary because this issue is on blizzards end, and blizzard need put out a fix.
They used to be really good at fixing things like this promptly but itās been over a week now with no fix or updates from them