"Whoops! Looks like Blizzard Broke Something. Give it another shot, by which we mean we expect you to solve our problems.
More Help: BLZBNTGT0000138F"
This has been happening way too long and way too often. This is in no way normal software behavior. When will Blizzard decide this is important enough to fix? When?
You didn’t say what troubleshooting steps you’ve already tried, but have you done the following:
Reboot your computer. BattleNet has a bunch of background processes that can go wonky, and trying to force quit them may not get them all.
Open BattleNet, click the cogwheel and select Scan and Repair.
I should not have to reboot my computer multiple times a day because the Battle.net launcher glitches. Yes, Rebooting work. That’s not the point.
Oh, and I just got another similar error as the launcher tries to down load an update again.
Please just fix this and putting the stop-gap measures on players.
Oh, and while you’re here. The JC profession in MoP-Classic has a bug. Any word on if it will be fixed?
Buddy, I’m just a regular user like you, suggesting the solution I and others have done to resolve that issue.
And you didn’t mention running Scan and Repair, which is the important part. Rebooting just puts your computer in a clean state so the scan can do its thing.
I have gone through all of the steps in the blizzard link. ALL of them. Then the next time I play the game I often get the same error popping up.
So yes, I’ve done everything you and blizzard have suggested. Still the same thing over and over. At some point I stop getting the error and I get 1-2 months of peace and quiet… Then back to this same song and dance.
I apologize for confusing you with a Blizzard employee but thank you for your suggestions.
You can avoid rebooting by opening Activity Monitor (In the Utilities folder under Applications), finding Agent and force quitting it. It may reopen, so you may have to force quit more than once. Once Agent isn’t running, you click the Update button in Battle.net and it should work.
That won’t mean it works long-term, but it’ll get you past the immediate issue. I keep Activity Monitor open now because this bug sucks.
A appreciate you pointing this out and I’ll try it next time.
I will say to Blizzard once again, my computer hung up and failed to launch the game after “updating” the game from version 5.5.0.62959 to … drum roll please… version 5.5.0.62959
That said, let me get this straight… blizzard’s software is sophisticated enough to run a game connecting ten of thousands of players across multiple continents… it can detect and report bots and similar cheats and hacks … BUT, it’s can’t do a version check of the current software to determine to NOT update the software when it’s already up to date?
… Again, for all the Blizzard Employees who are NOT here and are actively ignoring these reports. I should not have to restart my computer or go through other extraordinary lengths because you guys can’t fix your code.
I occasionally get this problem. The easiest solution which requires neither restarting your computer or quitting the Battle.net app is to open activity monitor and search for the agent process. You can kill the agent process while battle.net is still open. Then you just click update in the battle.net client again.