Unable to update games with error BLZBNTAGT00000840

Desktop App Bug Report
21

I’ve just managed to get it working:

  • rm-rf’ed .wine folder once again.
  • downloaded a fresh SC2 installer and started it via cmdLine: wine 'StarCraft-II-Setup.exe'
  • at the end of installing Bnet it crashed with BLZBNTAGT00000854, but it managed to create a Bnet desktop launcher right before dying.
  • clicked the launcher, it worked normally, Bnet started and I was able to login and start a fresh SC2 installation which managed to create an SC2 desktop launcher right before crashing with BLZBNTAGT00000840 at just few % of the download. Also Bnet window became totally unresponsive, but after 2 minutes of clicking the top right corner I did manage to close it.
  • clicked the new SC2 launcher, Bnet launched normally and reported that SC2 needs an update. I clicked the big blue UPDATE button and it continued downloading for a while and then again crashed with BLZBNTAGT00000840.
  • the above point had to be repeated like 2-3 times, but each time it was resuming from the pre-crash state of the download and finally it managed to finish: the big blue button became PLAY and worked normally after clicking :slight_smile:

I’m on Debian trixie, kernel-6.12.9, wine-9.0 slightly patched, but I’m completely almost sure these patches don’t matter in this case (the patches make wine correctly recognize Nvidia 30xx and 40xx GPUs as described in winehq bug 54339 (sorry, not allowed to include links) but I didn’t even have my Nvidia eGPU connected during the above procedure).

22

So how would you categorize your own posts in this thread? Seriously…

You are either tripping or have just moved here from some parallel reality: just search for BLZBNTAGT00000840 on reddit: more and more folks on windows-11 report that they are experiencing this issue as well (very few on mac indeed though and haven’t seen any on win-10).

5 Likes
23

Providing information about forum policies (asking someone to make a new thread for a different platform) or the stance on a specific platform (Linux being unsupported) is not form of trolling, it’s part of the volunteer role.

No need to be impolite, let’s count them together. There are 14 Reddit threads from the last week, many of which are for Linux (personal responsibility), and the rest of the results are from years ago. Additionally, many of them found solutions they performed on their local machine, with no changes from Blizzard. When major issues are caused on Blizzard’s side, reports are are usually in the hundreds or thousands.

24

Yes, yes, Linux is not supported ok ok everyone gets it thanks for the reminder

4 Likes
25

Thanks. This worked for me.

26

I have the same issue. Steamdeck user. Ran the bnet launcher and WOW.exe with zero issues since buying the console August 2024. Both Bnet launcher and Wow.exe are set to run compatibility proton ge811. based on Blizzards notes on the error I’ve run the repair (scan and repair) tool; uninstalled and attempted to reinstall WOW client files. Bnet client will not download any files now, including WOW client files.

Attempted to use every version of proton available through Steam, including experimental and hotfix. All failed to allow the update. Proton version 7.0 and lower will not load bnet or wow launcher.

I’ve read through euro and us forums as well as reddit posts. Issue appears to be centered on Bnet client side permissions. Various posts from Mac and Windows users with the exact same error message. Does not appear to be constrained to Linux/Steamdeck users.

I’ll be breaking out one of my PC’s later today to test if the same issue is effecting older windows versions.

Edit: reviewed others replies on this thread. There is also a big thread over on the Mac forums, multiple instances of the same error code. Its currently top post for Mac bug reporting.

I’ve tried deleting each version of proton, reinstalling through steam, and from allowing steam to change the compatibility value for bnet and wow.exe. Same results.

Went through dolphin and searched for the Agent.8988 mentioned below. Made the suggested edit (i found two instances of the folder) Same result.

Completely manually deleted Agent.8988 and its logs in both directories. Restarted bnet and ran fix tool. Same result.

Completely manually removed all WOW client files, bnet redownloaded base 500mb give or take then proceeded to the same error.

Convinced at this point I will need to do a page 1 reinstall of bnet and wow, if possible; or wait for Blizzard to un-F the situation…

Update: Last night after dnd on a lark I tried loading bnet and another update attempt. Still running through SteamOS, Proton 8.05. Update started normally and ran to approx 50% wow client files. Then failed. Same error.

This morning I installed Lutris, directed it to the battle.net .exe running proton GE 8-26. Running fine so far and downloading client files. Fingers crossed.

Update-Update: Download completed, although slow for client files. Updated correctly after I “toggled” between proton 8.0.5 and GE proton 8-26. Reran scan and fix tool. Downloaded another update, another instance of toggling proton versions. Game ran to TWW opening cutscene. Closed game, updated my addons. Reopened was able to load to game and character in world no issue. Closed game, another update request. Toggled proton, finally stable.

All this nonsense for plunderstorm…

2 Likes
27

So everybody with this problem has to create a new thread, topic, whatever to get attention? I am sorry but morgwai has some valid points and even though I didn´t comment, complain, anything, meanwhile searching for a solution. Furthermore I was “happy” to see, me not being the only one affected by this MAJOR problem. I am also a Mac user, not able to download the Launcher or anything else.

Brand new m4 Pro, technical in house support, nothing helped and I didn´t find any close solution to this problem.

Sorry for me being kinda frustrated, but seeing so many comments and issues around this similar Bug Reports should have made you react days ago.
Even “just” ONE player and “just” ONE complaint should be enough to react …

Hopefully u can give this topics more attention and try to solve this problem.

Thank you very much!

3 Likes
28

Hi. I found this link

www.reddit.com-r-macgaming-comments-1i2aipq-cant_install_battlenet_error_code

and followed SuprBrown’s instructions for a Mac and it worked for me.

(Change - to / in the URL)

29

Just those on different operating systems than the original post in a thread. This one is about Linux.

I mentioned this already: I’m a volunteer and I don’t work at Blizzard. I respond to threads when I have time to visit the forum.

30

Culprit seems to be Agent.8988.

On Ubuntu 24.04. Get Agent location, for me it was; [proton prefix]/pfx/drive_c/ProgramData/Battle.net/Agent.

$ rm -r Agent.8988
$ touch Agent.8988
$ sudo chattr +i Agent.8988

chattr … command makes Agent.8988 file immutable so Battle.net client cant’t mess with it.

Fixed Battle.net client installation (Battle.net-setup.exe) and so far Diablo IV download (previously stopped ~38% with BLZBNTAGT00000840 error. So nuked D4 and Battle.net client installation for nothing :rofl:

7 Likes
31

This worked for me as well!

32

So today Blizzard apparently has blessed us with yet another update and my SC2 stopped to work again with BLZBNTAGT00000840. I tried this fix, but it caused my agent to throw BLZBNTBTS0000005C :frowning: I will try my previous fix again (brute-forcing through a fresh install).

@Blizzard, seriously folks, pls pls put this stuff together…

1 Like
33

From what I’ve just read on Reddit, the key for this recipe to work is to still have an older version of Agent (like 8916) in your folder, so it tricks Bnet to use it. If you don’t have it, it will not work and throw BLZBNTBTS0000005C as described above.

3 Likes
34

ah so basically what Nicole said to do just makes the new agent not work at all and it uses the old agent. Was wondering why deleting a folder and creating an empty file instead fixed the issue.

I was trying all sorts of stuff to fix it because I picked today to prepare my steamdeck for a trip and thought the issue was on my end. Don’t reinstall battle.net btw, because then you only have the new agent and that prevents you from finishing the install.

35

I never type here practically, I just want to say very good detective work here. Good job.

36

Just noting that switching the runner to GE-Proton allowed me to update the games w/o issue as another noted.

37

all credit goes to the brave folks on reddit who figured it out. we are just reposting :wink:

38

$ rm -r Agent.8988
$ touch Agent.8988
$ sudo chattr +i Agent.8988

Worked for me.
Ubuntu 24.04, lutris, runner: wine-ge-8-26. I used locate to find Agent.8988. I noticed it was a directory so didn’t understand why we were making a file. I tried it anyway. At first it didn’t work. Then I remembered that the previous person did it on Diablo IV not Wow. So I shut down lutris and everything, started over, tried D4 and it updated it! Then tried Wow and it also updated. Great find. I don’t know if the order matters but it did for me. Note my file was located in ~/Games/world-of-warcraft/drive_c/ProgramData/Battle.net/Agent/Agent.8988 and I did have an older version of Agent there. Also, I tried so many things including rename folders and reinstall, and updating on a windows box and copying files. Even that didn’t work. Just wanted to comment in case it helps someone else.

1 Like
39

On a fresh Lutris install on PopOS this worked for me:

  • Install Battle.Net with Lutris standard Script
  • Did the Agent.8988 thing mentioned here
  • Copied Agent.8916 from a Windows install
  • Relaunched BattleNet and it wanted an update. Did that.

Am now installing WoW Classic without issues.

40

Worked for me, too! I also have an old Agent.8916 folder.
MX Linux here with Lutris, had the 840 with D3 and SC2. Tried many different things including completely fresh install, nothing helped before that.