Unable to update games with error BLZBNTAGT00000840

Desktop App Bug Report
1

As of today (1/14/25) I am no longer able to complete game updates on the Battle.net Launcher, with the update terminating with a BLZBNTAGT00000840 error. This seems to be exclusively impacting Linux/Steam Deck users judging by reports in a thread on the WoW Customer Support forum (which I can’t link to due to posting permissions, unfortunately) and on external forums like Reddit. This problem doesn’t seem to be exclusive to WoW as any game update will generate this error.

For what it’s worth, I run Battle.net under Bottles with the caffe-9.7 runner, but I’ve also seen reports of it failing under Lutris and various other runners as well.

Here are the generated Agent.exe log files:

Agent-20250115T025105.log

[I 2025-01-15 05:14:21.0567] Duplicate POST /update completed in 0.3790 ms
[I 2025-01-15 05:14:22.0167] Request GET /update/wow
Response 200 (0.3080 ms): {
“active_config_key”: “645739ee4e372d3ac47291ca1b7fb31a”,
“background_download_available”: false,
“background_download_complete”: true,
“branch”: “”,
“current_version”: 58630,
“download_complete”: false,
“download_rate”: 0,
“download_remaining”: 0,
“estimated_time_in_sec”: 0,
“extended_status”: {
“current”: 0,
“rate”: 0.0,
“remaining”: 0,
“state”: 0,
“total”: 0,
“unit_type”: “bytes”
},
“ignore_disc”: false,
“installed”: true,
“local_version”: “11.0.7.58608”,
“needs_rebase”: false,
“patch_application_complete”: false,
“paused”: false,
“playable”: false,
“playable_progress”: 0.0,
“product_family”: “wow”,
“progress”: 0.0,
“region”: “us”,
“regional_version_info”: {
“cn”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“eu”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“kr”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“sg”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“tw”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“us”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false,
“selected”: true
},
“xx”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
}
},
“shared_container_info”: {
“subpath”: “retail”,
“uids”: [
“wow”,
“wow_classic_era”,
“wow_classic”
]
},
“state”: 1000,
“using_media”: false,
“write_rate”: 0
}
[I 2025-01-15 05:14:23.0743] Executing operation: create_folder folderPath=“Z:/home/feythaline/Games/Multiplayer/Battle.net/World of Warcraft/Data/”
[I 2025-01-15 05:14:23.0744] Executing operation: create_folder folderPath=“Z:/home/feythaline/Games/Multiplayer/Battle.net/World of Warcraft/retail”
[I 2025-01-15 05:14:24.0186] Request GET /update/wow
Response 200 (0.2440 ms): {
“active_config_key”: “645739ee4e372d3ac47291ca1b7fb31a”,
“background_download_available”: false,
“background_download_complete”: true,
“branch”: “”,
“current_version”: 58630,
“download_complete”: false,
“download_rate”: 0,
“download_remaining”: 0,
“estimated_time_in_sec”: 0,
“extended_status”: {
“current”: 0,
“rate”: 0.0,
“remaining”: 0,
“state”: 0,
“total”: 0,
“unit_type”: “bytes”
},
“ignore_disc”: false,
“installed”: true,
“local_version”: “11.0.7.58608”,
“needs_rebase”: false,
“patch_application_complete”: false,
“paused”: false,
“playable”: false,
“playable_progress”: 0.0,
“product_family”: “wow”,
“progress”: 0.0,
“region”: “us”,
“regional_version_info”: {
“cn”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“eu”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“kr”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“sg”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“tw”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“us”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false,
“selected”: true
},
“xx”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
}
},
“shared_container_info”: {
“subpath”: “retail”,
“uids”: [
“wow”,
“wow_classic_era”,
“wow_classic”
]
},
“state”: 1003,
“using_media”: false,
“write_rate”: 0
}
[I 2025-01-15 05:14:25.0192] Request GET /update/wow
Response 200 (0.3160 ms): {
“active_config_key”: “645739ee4e372d3ac47291ca1b7fb31a”,
“background_download_available”: false,
“background_download_complete”: true,
“branch”: “”,
“current_version”: 58630,
“download_complete”: false,
“download_rate”: 0,
“download_remaining”: 0,
“error”: 5016,
“error_details”: {
“message”: “Failed to initialize the tact instance”
},
“error_message”: “Failed to initialize the tact instance”,
“estimated_time_in_sec”: 0,
“extended_status”: {
“current”: 0,
“rate”: 0.0,
“remaining”: 0,
“state”: 0,
“total”: 0,
“unit_type”: “bytes”
},
“ignore_disc”: false,
“installed”: true,
“local_version”: “11.0.7.58608”,
“needs_rebase”: false,
“patch_application_complete”: false,
“paused”: false,
“playable”: false,
“playable_progress”: 0.0,
“product_family”: “wow”,
“progress”: 0.0,
“region”: “us”,
“regional_version_info”: {
“cn”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“eu”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“kr”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“sg”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“tw”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
},
“us”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false,
“selected”: true
},
“xx”: {
“config_key”: “63f2f80bbaabd19b6c945b9a289d5ca4”,
“display_version”: “11.0.7.58630”,
“playable”: false
}
},
“shared_container_info”: {
“subpath”: “retail”,
“uids”: [
“wow”,
“wow_classic_era”,
“wow_classic”
]
},
“state”: 1200,
“using_media”: false,
“write_rate”: 0
}

AgentNGDP-20250115T025105.log

[I 2025-01-15 05:14:23.0743] Start Update of wow w/ tags (Windows x86_64 US? acct-USA? geoip-US? enUS speech?:Windows x86_64 US? acct-USA? geoip-US? enUS text?)
[I 2025-01-15 05:14:24.0984] Keyring initialized successfully with 1 keys.
[E 2025-01-15 05:14:25.0012] Failed to initialize the tact instance

bc-20250115T025105.log

[I 2025-01-15 05:14:24.0991] [tact] Adding server node 0. Server ‘blzddist1-a.akamaihd .net’ | Address ‘23.55.241.169’
[I 2025-01-15 05:14:24.0991] [tact] Adding server node 1. Server ‘blzddist1-a.akamaihd .net’ | Address ‘23.55.241.163’
[I 2025-01-15 05:14:24.0992] [tact] Adding server node 2. Server ‘level3.blizzard .com’ | Address ‘23.55.241.163’
[I 2025-01-15 05:14:24.0992] [tact] Adding server node 3. Server ‘level3.blizzard .com’ | Address ‘23.55.241.169’
[I 2025-01-15 05:14:24.0993] [tact] Adding server node 4. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.5’
[I 2025-01-15 05:14:24.0993] [tact] Adding server node 5. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.3’
[I 2025-01-15 05:14:24.0993] [tact] Adding server node 6. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.7’
[I 2025-01-15 05:14:24.0993] [tact] Adding server node 7. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.2’
[I 2025-01-15 05:14:24.0994] [tact] Adding server node 8. Server ‘blzddist1-a.akamaihd .net’ | Address ‘23.55.241.163’
[I 2025-01-15 05:14:24.0994] [tact] Adding server node 9. Server ‘blzddist1-a.akamaihd .net’ | Address ‘23.55.241.169’
[I 2025-01-15 05:14:25.0008] [tact] Adding server node 10. Server ‘level3.ssl.blizzard .com’ | Address ‘23.55.241.169’
[I 2025-01-15 05:14:25.0008] [tact] Adding server node 11. Server ‘level3.ssl.blizzard .com’ | Address ‘23.55.241.163’
[I 2025-01-15 05:14:25.0009] [tact] Adding server node 12. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.6’
[I 2025-01-15 05:14:25.0009] [tact] Adding server node 13. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.5’
[I 2025-01-15 05:14:25.0009] [tact] Adding server node 14. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.3’
[I 2025-01-15 05:14:25.0009] [tact] Adding server node 15. Server ‘us.cdn.blizzard .com’ | Address ‘137.221.64.7’
[I 2025-01-15 05:14:25.0009] [tact] DNS resolution completed in 18ms.
[E 2025-01-15 05:14:25.0011] [casc] Failed to get exclusive access since we are not first to bind. Mode(5)
[E 2025-01-15 05:14:25.0011] [casc] failed to bind Container index at ‘z:/home/feythaline/Games/Multiplayer/Battle.net/World of Warcraft/Data/data’: 11 (CascLocked)
[E 2025-01-15 05:14:25.0011] [tact] Failed to open dynamic container at ‘z:/home/feythaline/Games/Multiplayer/Battle.net/World of Warcraft/Data/data’. Error (11): CascLocked
[E 2025-01-15 05:14:25.0011] [tact] Failed to initialize dynamic container. Error(16): container locked

curl-20250115T025105.log

[W 2025-01-15 05:14:24.0018] Validation Failure downloading “http ://blzddist1-a.akamaihd.net/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0018] Changing Request for handle 1E418DF8 to http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0092] Validation Failure downloading “http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0092] Changing Request for handle 1E418DF8 to http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0231] Validation Failure downloading “http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0231] Changing Request for handle 1E418DF8 to http ://blzddist1-a.akamaihd.net/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0361] Validation Failure downloading “http ://blzddist1-a.akamaihd.net/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0361] Changing Request for handle 1E418DF8 to http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0488] Validation Failure downloading “http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0488] Changing Request for handle 1E418DF8 to http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0607] Validation Failure downloading “http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0607] Changing Request for handle 1E418DF8 to http ://blzddist1-a.akamaihd.net/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0735] Validation Failure downloading “http ://blzddist1-a.akamaihd.net/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0735] Changing Request for handle 1E418DF8 to http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0863] Validation Failure downloading “http ://level3.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[I 2025-01-15 05:14:24.0864] Changing Request for handle 1E418DF8 to http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd
[W 2025-01-15 05:14:24.0983] Validation Failure downloading “http ://us.cdn.blizzard.com/tpr/wow/config/3c/a5/3ca57fe7319a297346440e4d2a03a0cd” - Expected: 3ca57fe7319a297346440e4d2a03a0cd, Actual: 00000000000000000000000000000000
[W 2025-01-15 05:14:24.0983] Attempts exhausted (10 total) for handle 1E418DF8

Operations-20250115T025105.log

[I 2025-01-15 05:14:21.0567] Reservation Created for wow:OP_UPDATE
[I 2025-01-15 05:14:21.0790] Queue operation - OP_UPDATE for ‘wow’
[I 2025-01-15 05:14:21.0790] Active operation nullptr replaced by OP_UPDATE for ‘wow’
[I 2025-01-15 05:14:25.0023] Process finished OP_UPDATE for ‘wow’
[I 2025-01-15 05:14:25.0023] OP_UPDATE for ‘wow’ completed

9 Likes
2

Edit: Post was relocated, but is now miscategorized.

This forum is a P2P troubleshooting area and feedback is not collected here. Plus, Blizzard doesn’t support Linux for any of its game titles.

1 Like
3

I’m well aware Linux is not officially supported but Blizzard has historically been one of the best developers in the industry for providing unofficial support. They clearly have developers who are passionate about it and whenever an issue arises they are usually quick to fix it.

I posted it here because the team behind the desktop client is more likely to frequent this forum than the others that I mentioned and thus there is a better chance it may catch their eyeballs.

5 Likes
4

Forum blues are long gone (as of March '24), save for a few thread locks and spam removals. And I haven’t seen a Bnet dev since last August. You might get more traction on Reddit.

2 Likes
5

Bugfix devs may be gone, period. You can now get the Underlight Angler almost immediately if any of your toons have it, just fish Legion pools until you get the big pearl.
What was somewhat bugged before, and is not near-hopelessly broken, is the UI to upgrade the pole.
Prior, one console command to activate the first ability unlocked the UI and showed all the nodes for you to click on.
Now, nothing shows the nodes, all you get is a blank UI with a backdrop image. You have to upgrade by text commands in the console.

1 Like
6

Well, this would not be the forum to report that issue. Head to WoW’s Bug Report forum, not Bnet.

1 Like
7

Same here. I even tried a nuclear option of rm-rf’ing .wine folder and installing everything from scratch: installer started and reported error ‘BLZBNTAGT00000854’ which literally has ONE hit in google: a reddit thread started 11h ago full of linux gamers crying…

Pretty please Blizzard fix it ;(

3 Likes
8

I am using windows 11 and I am experiencing the same.
I’ve done every common troubleshooting steps.I even uninstalled both bnet and wow and now it won’t even start installing.

4 Likes
9

Same, and this is the only game its happening with. Seems completely related to Plunderstorm update. If WoW is unplayable while the event is active and magically playabale once the event is over, we’ll know better or not.

2 Likes
10

Anyone who has installed Bnet or Bnet games on Linux must already know this. Never understood the need for this to be stated to someone playing wow on a Steamdeck. It comes off as admonishing for even having the gall to try it.

Not really the players fault that an industry giant once know for support on more than just windows, has whittled itself down to something that seems unrecognizable. :disappointed_relieved:

4 Likes
11

I am on a legitimately brand new laptop, Windows 11. I just got it today. Battlenet is the first thing I installed on it, started installing WoW, ran into BLZBNTAGT00000840, and haven’t been able to get any further. I spent $1k on a new computer, and I still can’t even play my game. I am beyond frustrated right now!

4 Likes
12

Your issue would not be related since it’s an entirely different operating system than the OP is discussing.

Okay, then this information isn’t for you. Instead, it’s for someone who will google this type of question and only part of the results will show information. It’s nice to have the complete answer so they know they may be wasting their time troubleshooting a platform the company doesn’t support.

I will continue to provide this information on all threads using an unsupported operating system.

13

I’m using Lutris. I fixed it by changing Wine version to ge-proton in Runner Options.

4 Likes
14

Das selbe Problem habe ich auch gestern kam mein neuer Rechner mit Windows 11 pro konnte wow einmal starten als ich abends wieder ran wollte ging das mit dem aktualisieren los und zack immer nur diese Fehlermeldung das nervt total ehrlich

1 Like
15

Same issue. My new iMac just arrived which gave me a deep illusion that I could play all night hearthstone. When are they gonna fix this? I have played hearthstone on my Mac Pro 2015 for 9 years without any issue. I am so upset rightnow.

2 Likes
16

Have you done any debugging to conclude so? If so, please share more info.

How about using your time in a more productive way, like for example making sure that appropriate technical folks are aware of the issue?

I think I will stop wasting my time (and money) on Blizzard games…

3 Likes
17

This IS NOT limited to just Linux and steamdeck. I have now seen it reported under Windows 11, and also on MAC with WINE. Someone updated something in the afternoon of the 14th and it broke A LOT of installations,. months of playing diablo iv to build a character to end game status, and NOW I AM LOCKED OUT OF THE GAME due to this error. This is BS. supported on mac or not, Blizzard sure took my money when i bought the game originally, AND for the expansion on season of hatred. This is ridiculous that a dev is allowed to update something on the sly like this and break so maby installs.

Instead of worrying about where a post is posted, get the attention of someone in charge to look at this and fix it! we gave you guys the EXACT date and a round about time it happened so tracking it down to a specific patch should NOT be that hard.

PLEASE FIX THIS ASAP.

6 Likes
18

U are right its on them on Bnet side

2 Likes
19

I’m happy it’s not just me. Thought I broke everything. Although I’m also on the steam deck, hopefully since it’s happening in Windows & Mac, they’ll be likely to fix it?

20

That’s unrelated to what I am saying. If a player is on Windows and experiencing this issue, they should make a new thread outside the one about Linux.

Trolling a volunteer won’t move your issue up the list of issues to fix. If their forum team finds (through data collection) that more people on supported platforms are affected, I’m sure they’ll look into it when possible. As it stands, there are very few reports in all Blizzard game title forums about this issue happening on Windows/Mac.