M1 Mac BattleNet and Agent Broken - Stopping WoW installation

I was able to play over the past couple weeks thanks to Girodo’s files which he kindly provides over Discord, however with the latest update I now once again get error BLZBNTAGT0000138F. To be clear this is an issue for both Retail and Classic.

I tried every other solution offered including changing every individual folder’s permissions and nothing works for me. I am now unable to update the game and thus unable to play.

I am really confused as to why the last blue post was in JUNE when people have been continuously reporting this problem over and over. Will Blizzard ever look at this thread again? It has almost 15k views and has gone unresolved for 6 months. I was able to play for a total of 12 days before an update made the game unplayable again. If this doesn’t get fixed I paid the rest of my subscription time to just stare at Battle.net failing to do its only job.

1 Like

Worked for me, too. Also, not using the beta client.

In my case, I tried everything I found here and on some reddit threads, but nothing worked. It starts to download the game and gets stuck at around 70-90 mb.
I noticed in activity monitor that Agent process is going nuts, utilizing more than 100% cpu and new process starts every time I want to install the game, without killing the previous one.
Kind of sucks that they could not fix it after so many weeks. I wanted to return to wow after longer brake but I guess I am not playing it anymore :smiley:

On the other hand I had no issues updating Hearthstone so it seems it is related only to wow.

I am on m1 mac Sonoma.

2 Likes

MacOS Sonoma.
Tried all the suggestions I could find to fix the problem. No luck so far. Both Classic and Retail stuck on “Initialize” step during an update.

1 Like

Here’s what worked for me:

Ok so it seems that I fixed the issue for myself. I was able to get past the initializing step and now the game is downloading.

However there is another issue and that is the download speed. My connection is 287.94 Mbps but the download speed is constantly degrading untill it stops downloading the game entirely and I have to close and reopen the battle.net or pause and start the download. It starts at the highest speed and then degrading over time down to 0 basically.

What I did was:

  • delete Agent folder from users/shared/battle.net
  • give read/write permissions to your name to World of Warcraft folder inside Applications directory
  • switch to beta battle.net app
  • kill all the agent/battle.net processes in the monitoring
  • open the beta app, start downloading the retail and wait untill the Agent app starts using significant CPU. Once it gets close to 100%, pause the installation, switch to classic WOTLK and install that instead. Once the classic is installed, you can switch to retail and download it. But the same issue with download speed, maybe even worst, is affecting retail as well, but that may be just something temporary.

That is really strange behaviour, it seems like they broke the battle.net app for WOW client entirely. What bugs me the most, as the developer myself, that they had this issues for over several months now and they are doing jack sh about it. Cannot imagine we would have bug that severe with those many complaints and affected users and just keep it unresolved.

edit:
alright, so the download speed was fixed by setting 9999999 KB/s for download limits.

3 Likes

M1 Pro here, Sonoma recently installed.

This happened a few months ago and this is how I fixed it: M1 Mac BattleNet and Agent Broken - Stopping WoW installation - #106 by Adtralza-ragnaros

With 10.2 the same problem started again, so what I did is check out which app had disk permissions again, and Battlenet, Wow and relauncher still had access, but there was a SECOND relauncher (named exactly the same) in the options below. I gave that one access as well, and the patch could finally start downloading. Game is running fine again.

I didn’t delete or reinstall anything.

The thing that worked for me instantly was to give Relauncher full disk access. Even though I appear to have eight of them.

1 Like

I have it now working after getting a Battle Net App update (2.26.1.14494). I finally got this update on my 5th install.

Did you delete everything and started the updated again for 5 times or did you try to continue? I did both whiteout any success…

1 Like

Sonoma, M1 Pro. I gave battle.net permissions to “App Management” & “Full Disk Access” and it worked. The game is downloading.

Also I have beta version of battle.net but I don’t think it matters.

Hi All
I solved by doing all of the above and continuing to do it for +30 times. Eventually I succeeded. Dont no why but many thanks for all the advice :slight_smile:

M1 pro macbook here as well. In the summer I downloaded Wow thanks to a guy sharing a Wow.zip file containing classic. Today everything died again for me. I could not update any of them, nor could I start classic hardcore which was already updated and ready to play. I deleted all of them, and tried to do the same thing I did in the summer. That doesn’t work anymore…

1 Like

After trying everything and failing on a M1 Pro, today I tried on a Macbook Pro with Intel chipset.

Same error, same steps attempted, no way to make it work.

I don’t understand how they can leave a client completely broken and no alternative solution to install…

1 Like

Hi, just installed Battle.net App and WoW on my new M3 Max yesterday. Since then the Agent keeps wanting “to change the system” and requires a (Mac-)Password. After I enter it, the app rewards me with an popup that WoW is now playable.

This happens every few hours if the battle.net App is running in background. On other Topics (wich are years old and automatic closed after nobody did read) I read, that this prompt will take focus from whatever you do in the moment (even if you are in WoW).

It would be nice, if that issue which seems to be around for a while, would finally be fixed.
It would also be nice, if there was an Apple Silicon Version of the battle.net App. Task Monitor stills says “intel” even tho WoW (Retail) is Apple.

Also, I need to allow incoming traffic whenever I start the battle.net App.

Edit:
Battle.net - Version 2.26.1.14494
Battle.net Update Agent - Version 2.31.3.8445

Just wanted to point out that this seems to be a permission issue.

And, what solved this for me was to first close the Battle.net app, then open “System Settings → Privacy Security → Full Disk Access”. There I intially had a bunch of “Relauncher” entries. All but one were grayed out, I deleted the grey ones by marking them and pushing the “-” button. Then for the one “Relauncher” entry that was not grey, but black I think, I gave that full access. I also added the “Battle.net” app itself to the list and gave it full access, not sure if it was needed though. Then I opened the Battle.net app and updates were able to complete.

Let me know if anything I wrote was unclear.

I am on an M1 MAX running Sonoma 14.1 and Battle.net 2.26.1.14494.

Best of luck.

2 Likes

It’s strange that eventually with different approaches we all manage to get it working again. I really wish we didn’t have to spend hours troubleshooting with every major update.

BLIZZARD: This is a permissions issue that is not usually resolved by simply allowing full disk access like the only blue post here suggests. Please please please look into fixing this because even if people do get it working it’s far from ideal and many people had to download files (the indices that Battle.net seems unable to download on its own) from a third party which is something you would discourage.

Do you still have a MacOS dev team? Are they aware of this problem? Would love to hear SOMETHING, anything.

1 Like

I wasn’t even able to make it work. Tried everything above. They don’t even care.

1 Like

I tried:

  • full permissions approach for battle.net and agent
  • kill manually agent process and agent folder
  • doing the battle net beta upgrade
  • creating separate installation folders from default with full access to all element inside

And I tried all these strategies, on two different Mac laptops, one M1 Pro and one Intel i5…

I mean, seriously? It still doesn’t work…

1 Like

Ok for some strange reason ( update maybe) mine started working again this morning