An hour ago, the game worked. When I try to launch it now, the battle.net launcher tries to update the game, fails, and pops up a dialog that says this:
"Something went wrong with a file. We’re not sure what caused it, so please try again or click the code below for more information. Sorry about that!
More help: BLZBNTAGT00000840"
Uninstalling and reinstalling gets to the point where it says “reclaiming space…” and then fails with the same dialog.
- Device Type: PC
- Warcraft Rumble App Version: 11.1.0.112249
2 Likes
Same started happening for me since yesterday. Nothing helps - reinstall, clearing cache, restart pc, disabling firewall… And this is for other games as well - Wow, Diablo 2, etc… (I’m launching through Lutris on Linux).
Doesn’t seem as though Blizzard are all that concerned about customers being locked out of their game as a service MMO. Well here’s another person, same problem, same time frame. Maybe run your patches through the A team rather than let the cadets push whatever they like to live.
Same error here. Since yesterday. Can’t update on PC. Can still play on Mobile.
Repair and Scan did nothing.
Device: PC
Warcraft Rumble App Version: 11.1.0.112184
I’m just curious, what OS are you using, Windows?
No, I’m also running it on Linux 
With Bottles on Flatpak.
Id be very careful to go to sources outside of Blizzard. Even tho I am also I bit sad at blizzard right now for another game breaking bug.
Still I don´t recomend you guys going outside blizzard for “fixes”. Chances are the code or codes could steal your data!
2 Likes
I agree, better to wait for the proper fix if you don’t already have the older version of Battle.net Agent on your PC. Sounds a bit too risky to use some random .exe file that someone sent to you… Well, next time we will know to backup the older Agent versions. 
There is no “code”, it is literally removing the problematic new agent version and making a new immutable folder for it, forcing the agent to use the version that still works (providing you haven’t uninstalled battle.net to attempt to fix this, the old folder should still be there).