Battle.net app stuck on "Launching"

Hi there,

Saw an older post from Skinnbones posted on July 12, 2024 about the game not launching after clicking on “Play” from the Battle.net app.

Has anyone else had any similar issues and/or found a solution?

I have the M1 Pro Mac on macOS 14.6.1 and have been playing the past month without issue until today. I tried everything such as:

  • Scan and repair the game folder
  • Switched the Battle.net app to Beta version to see if it works
  • Redownloaded the game and did a clean install
  • Deleted the add-on folder to make sure it’s clean
  • Used added command line argument “-d3d11” to run it using Direct 11
  • Uninstalled the battle.net app and re-installed a new version
  • Shut down my Mac/updated to the latest OS
  • Made sure the folder and game had full disk access and read/write permissions
  • Launched the game from the folder instead of battle.net

There doesn’t seem to be any solid solution online. Would appreciate any help!

Edit (15/08/2024): For anyone else with a similar problem, after trying about everything, I ended up launching the game from Battle.net app and just leaving it alone even if the app says “Application is not responding”. Instead of force quitting, after about 6 minutes and 15 seconds (Actually timed it lol), the game started working. I start the game this way now, and it’s consistently been 6 mins+ to start.

Edit (20/08/24): SOLUTION: Would like to give credit to Nivsvdh for the solution, amazing find.

For MAC users, here is our workaround since, Nivsvdh is using Windows. Unfortunately, natively Mac firewall can only block incoming connections and not outgoing connections. So, you will need a third-party software to perform this. In my case, I have Little Snitch, an amazing app.

  1. Open Little Snitch, or your preferred software. Let it run and diagnose all outgoing connections.
  2. Open Battle.net, click on “Play” and wait for WoW to launch (6mins+).
  3. Once the game has launched, on Little Snitch, under “World of Warcraft”, you’ll see all outgoing connections from the app.
  4. Expanded view: World of Warcraft > blizzard. com > cdn.blizzard. com
  5. Block outgoing access to this particular IP. Which is mentioned in Nivsvdh’s post to be “IP range 137.221.64.0/24”
  6. Close battle.net, close WoW.
  7. Relaunch, and it works perfect, startup is less than 5 seconds.

This was a LONG and TECHNICAL solution, but as a Mac user, just had to be found. I hope this helps anyone else. Has been bugging me for quite a while, so I’m glad it’s fixed for now.

2 Likes

I’m having the exact same problem since yesterday, and this is the only thread that actually is relevant. I tried everything you tried but it won’t launch. The WoW icon jumps once and doesn’t actually start.

In my case it doesn’t even say “Application is not Responding”… No idea what else to do.

2 Likes

I’m sorry to hear that, I really don’t have a solution myself. Every time I launch the game, the wait is 6 mins before it starts. The funny thing is, I Installed Classic, clicked on “Play” and it launched in seconds. Went back to Retail and it still took 6 mins.

I’m hoping they release a hotfix or a small update in the future that fixes it.

Having the same issue
Client app works, but click wow and it bounces and doesn’t respond
Noticed there’s a Mac system update
Trying that and going from there

1 Like

I was fine yesterday, but upgraded to 14.6.1 overnight and now I have launch issues.

1 Like

Only solution is what post before mine said

Wait 6ish minutes for it to finally open and then just don’t log out lol

1 Like

I am having the exact same issue. I haven’t played WoW in about a decade and wanted to give it a try again. I’ve tried to start the game probably like 30 times in the last 3 days (installed it 3 days ago) and was able to actually play twice. Not a good look @blizzard … AND not a good way to win over NEW OR RETURNING Mac gamers …

2 Likes

For anyone else who might have not yet updated., as of 21/08/2024

V.11.0.2.56196 of the game seems to have fixed the issue. Even without the solution I gave, it launches fine now.

Nothing yet for Vanilla :frowning: