If you add me on BNet I can try to talk you through it. (posting on WOW Classic toon)
Just had this issue installing on my M1 Max MBP and your solution worked perfectly! Thanks. Oddly enough no issues on my Mac Studio yesterday. Odd that the common thread is the MBP with the problem.
More inclined to believe itâs just fresh installs vs migrated ones.
The work around almost simulates a migrated one by purposely using older version.
I never have issues on my MBP, but i havenât clean installed in 3 macs now. I always migrate.
The thing is, it should work outside the directory. Iâve placed it in dozens of other directories and tried to install from HPFS+ drives. Nothing seems to work unless the app is placed inside that folder and run with that specific argument. And itâs not permission creep either. I run it as sudo - still wonât work unless itâs in that particular folder. Itâs really odd.
It also doesnât require an older version. The original work-around I came up with did. But using a current version of Battle.net-Setup.app from Battle.net also pulls the files/installs correctly.
If you look in the log files, absent of the particular switch, there is an error thrown about read-only file system.
I actually think itâs how theyâre running the app in Rosetta IMO theyâre running it in /var or something to unpack.
I donât know a lot about how Rosetta works and emulates or whatever it actually does to run x86_64 code on ARM but that seems to be the actual problem (because thatâs way above of my pay grade)
1 Like
Yea mine is a fresh install and the directory thing is bugging out on my end. Not able to install still.
Just add me on Bnet and Iâll walk you through it.
Sarcasmic#11208
This worked for me as well, thank you so much <3
I managed to install Battle(dot)net and I still canât install WOW, game keeps installing infinitely T-T
Try doing scan/repair.
Restarting the Battle.net agent executables in activity monitor
also add battle.net/agent to macOS firewall (or turn it off either way)
Alternatively you can add me to Battle.net and Iâll try to help you.
Battelnet and Wow installer Agent hangs at 45 percent. Tried on three different versions of macOS. 12, 13 and 14 macOS with same results. No firewall or VPN present. Files completely deleted including any files mentioning Blizzard or Battlenet and any installations of Blizzard games, ie, WOW, Diablo, etc⌠Same results. Whatâs going on Blizzard? Are you dropping macOS support? Good thing I didnât purchase the new expansion. Iâll give you guys another week before I cancel my Blizzard subscription for good.
Still having issues when downloading where it gets stuck in the 80% when initializing which appears to be a separate issue after getting installed. Adding permissions hasnât fixed this either. M1 Pro w/ latest Sonoma.
Thank you it worked 
Whatâs ironic. I never have issues with bnet on macOS, but windows bnet in wine got stuck and hosed at 45% updating Diablo 4. sadly I could not find a good fix for it besides disabling entirety of system integrity protection because I canât really move that to a diff folder where it would inherit permissions it needed for file access.
so whatever they broke they actually broke it windows side too, well windows side running on macOS cause that always worked too til recent update.
Are you using wine or wine-staging?
FOR THOSE OF YOU WITH WINDOWS-Try this, it worked for me. Delete all of your blizzard and Battlenet folders in the Program 86 folder. You have to delete the Program Data folders as well. That folder is hidden in C drive, so go into the control panel and select (show all hidden folders). Once there at C/programdata , delete both Blizzard and Battle net folders. Then run the new exe install you downloaded from battlenet , and it should work. I Hope this helps!
just an observation, Blizzard suggests that you disable your firewall⌠so has anyone thought of doing that before they attempt the download⌠Plus having the VPN active will hinder your download.
The macOS firewall is generally pretty permissive. I do tell people that on Battle.net when they add me. Although you can just drag/drop the apps into the firewall context menu and itâll let those apps pass through.
1 Like
Iâve never actually see macOS firewall cause issues. it lets any developer signed app through it automatically. one of itâs default options is automatic approval for known developers.
While, battle.net is bordering on malware with how much of a mess it is, itâs still signed by a known developer so itâs issues are generally itâs own, not cause apple didnât allow it through firewall.
1 Like
Yeah thatâs what I meant by âgenerally permissiveâ lol. I have helped around 3 dozen people now with this installer issue over Battle.net and Iâve actually seen 1 or 2 where adding it to the firewall or turning off the firewall made a difference. I donât know why tbh because like you said âŚsigned developer.