Both versions of wow require an update, but upon clicking the button to do so will create the error “Whoops! Looks like something broke. You could try restarting Battle.net. More help: BLZBNTAGT00001389”.
Force-quitting and restarting does not work, and I get the same error when I try to use the scan & repair feature. Should I try to reinstall at this point, or is anyone else experiencing the same thing?
Have you tried rebooting? Sounds like battlenetisnt shutting down completely.
I’m getting a similar error that says it thinks there’s something wrong with my internet and I’m not connected. A restart fixes it. I just LOVE restarting my computer every time I want to install a patch, even a tiny <100mb hotfix.
Usually I’m able to brute force through it by restarting battle.net or just playing the game directly but that’s not even working.
And it’s all battle.net games including Diablo 3 and Hearthstone.
Diablo 4 via crossover is working fine so it’s clearly something wrong with the Mac battle.net client.
I have the exact same problem. For a long time it’s been wanting to update pretty much every time I get on to play… short updates whatever (if?) it is. But a few days ago I got the same error as you. It went away eventually, but it’s back again tonight. No battle or wow processes appear to be running.
BTW quitting for a few minutes and then restarting battle.net seems to fix the issue.
Use activity monitor or other app kill tools to fully get rid of any battle net instances seems to work if you don’t want to restart.
Actually all you need to kill through Activity Monitor is the process named Agent, it will have a Blizzard icon and be a major consumer of memory if left running too long. I once caught it over 2gb
No agent running afaik… and yet the problem persists. Again, quitting for a couple of minutes and restarting battle.net does seem to clear the issue for me.
I think it’s a battlenet app bug. There is a workaround. Find your WoW app and run it manually without battlenet. You’ll find that the Update button turns into a Play button. Dismiss the running WoW app (unless you want to input your credentials manually) and hit Play and you’re up and running.
Unfortunately after you quit the game later, the button will turn back into Update. Blizz needs to fix that bug.
I get this issue often, and I don’t think it has anything to do with our computers or with the launcher. The reason I suspect this is when it happens I just start WoW directly, which works fine, I just need to type in my password. Then without doing anything to my computer or the launcher updates will start working again later.
Note that the first time starting WoW directly you have to enter your email address, and there is a check box for “Remember Account”. Then you provide a code from the phone app, but this only needs to be done the first time.
Ok, I was wrong. After reading more posts here I started watching the bnet Agent process. It has a memory leak as people noted. It seems that when it gets to the point where it is using 5GB of RAM that updates stop working at all. Then not long after that I think Agent crashes, and is restarted. I haven’t actually seen this happen, but I saw Agent go from over 5GB of RAM to less than 1GB. After that updates would work again.
Is there a fix for this yet?