People, a solution is here! It actually works! Girodo, a person replied here, shared a folder with already downloaded WoW Classic version of the game (up to 5Gb folder) and there what I did to make it work:
Installed Battle.net
I didn’t give it some permissions to Full disk access or anything, the only permission it has is App Management by Agent (by default after an installation of Battle.nett app)
Closed Battle.net app
Put the folder with WoW Classic into my Applications folder on MacBook
Opened Battle.net app
Went to WoW Classic tab and located the game folder manually
And after doing so my Retail version started to update and it went through initialization and started to download the game! I suppose, if it doesn’t start to update/download by itself, try to click the Install button manually and it should work
I’ve discovered now which files are really needed for Battle.net to function properly. In the Application folder > World of Warcraft > Data > indices, there are thousands of files (450MB) that are unreadable for me, but are essential for Battle.net to work and, for example, install WoW Classic.
It appears that once the game files are in place, Battle.net operates smoothly. The issue seems to lie primarily with downloading the game files from scratch.
So, I’ve made these necessary files available for download (450MB)
Please contact me on discord (axynokay), I can’t share links here.
After downloading, carry out the following steps:
Close Battle.net.
Open the Activity Monitor (Application folder > Utilities) and end all Agent.app processes.
Alternatively: Restart your Mac.
Go to the Application folder and delete the “World of Warcraft” folder (if it exists).
Unzip the downloaded “World of Warcraft.zip” file and place it in the Application folder.
Launch Battle.net, go to WoW Classic (not WOTLK) and click on “Locate the game”
Select the new “World of Warcraft” folder.
Install additional WoW versions if needed.
If someone needs help, contact me on Discord: axynokay
We’re aware of an issue where the error BLZBNTAGT0000138F happens when trying to install WoW classic. This is already being investigated by our developers.
As a workaround, it can help to open the Mac Privacy settings and in here the App Permissions. In the App Permissions allow both the Agent and the Battle.net App full access.
If this doesn’t help, we can only ask for your patience, while this is being investigated.
No, this approach doesn’t seem to work. Furthermore, there appear to be two different Agent apps, which is quite confusing. The issue isn’t related to permissions because if you have the files from the indices folder, Battle.net operates without any problems, and there’s no need to tweak the Agent.app or mess around with permission settings.
It really does seem to be a matter of luck as to how the Agent.app behaves. If it freezes within the right timeframe, the download and installation process goes smoothly. However, it’s almost like playing roulette. But I’m sure people here didn’t download battle.net to play casino.
I genuinely don’t understand why downloading game files has to be this complicated. The issue could be easily resolved if the Battle.net installer simply downloaded the indices files first as a workaround.
Since MacOS Ventura you don’t have an option to give “full access”. I tried to go 1 by 1 and Agent only appears under “Full Disk Access” and Battle.net app does not even appear at all.
You can over the + symbol add another app to give it full permission. But as I already wrote, it will not help you.
It is not a permission issue, there is a significant bug with the Agent.app.
Agent.app is tasked with monitoring game installations and assists the downloader in correctly installing the games.
When certain game files, such as the indices, are already installed, the Agent behaves normally. However, when attempting a fresh installation, the Agent enters an installation loop (after ~80MB), which triggers it to launch multiple instances of Agent until the CPU is at full capacity.
You can try to terminate the Agent app in the right timeframe and the installation will run normally, but you have to be very lucky.
I did it!
I got a new Mac M1 Max. I could see that there was a ton of Agent applications launching when clicking update. However if you close(force quit) all Agents and and Battle.net application from the Activity Monitor. Then you open up Battle.net and WoW will instantly try and update(but it will not work yet), if you then go into ActivityMonitor you will see 2 Agents, and 2 Battle.net Helper. First I deleted both Agents, then I deleted one of the Battle.net Helper. Then it started to update and download. I hope this works for you guys as well. <3
I’m having the same issues on my Macbook Pro 14 M1 Pro using Mac OS 13.4.1. I tried to install the WOW Classic ERA PTR client. A bunch of Agent processes spawn at 100% CPU to a degree that the system is barely responsive any more. Then the installation cancels with error BLZBNTAGT0000138F but the Agents are still running and consuming CPU until force killed by the user.
Please let me know if you need any more information to reproduce the issue. Looking forward for a fix so I can test the WOW Classic Hardcore client on my Mac.
Right click the “Data” folder in WOW root folder and then click the padlock under “Sharing & Permissions” (even if everything is already set to “Read & Write”).
Then click the “…”-button and choose “Apply to enclosed items”.
Now I finally got only 1 Agent.app running and it seems to be downloading fine at 30MB/s. (only got 2-3MB/s when it had 10 Agent.app running)
I also have the same problem on mb pro - M1 Max. I tried everything out to fix it by myself. But nothing worked out for me. I really want to try dragon flight out. Fortunately I waited with buying the game :-/
