Hi,
I purchased Diablo 4 yesterday and an update was required after the game install. However, I got error code BLZBNTAGT00001389 - “The Battle.net desktop app is unable to download a file required for installation or patching”
I have tried uninstalled and reinstalled Battlenet app; remove my antiviral program; restart the computer. None of these help at all.
Hope someone can help me solved the issue.
Thanks
Thomas
same problem here… any solutions to this???
Same issue, and though it started with Diablo IV during the pre-order early access, it’s now also affecting Overwatch since the new season update and WoW also seems to be affected.
I’ve run through everything on the support page for the error multiple times and tried many other things (as suggested by scouring Google for other people with this error code or similar symptoms). The only “fix” that’s kinda worked for me is to uninstall the individual game, reinstall it (if it lets you; sometimes I get the same error when trying to install and am then stuck), and then it’s playable… but only until there’s another update required and the cycle starts all over again.
I submitted a ticket with a bunch of info that will hopefully help. 
Super frustrating issue and it’s using up all my bandwidth (and patience, tbh) to keep downloading each game over and over. Hopefully someone has a solution for us soon.
Me too i just purchased diablo 4 yesterday and it is stuck in 65% its been 13hrs and its still 65%…can someone help me pls
Really starting to hate these companies they’re trying to produce games as fast as they can to make people happy and stuff like that when they really need to take their time because it’s frustrating to get a half-made game and then have all these error codes every single time you’re trying to play or enjoy it go back to taking your time with games so people can actually be happy with your product
I also get this. Battle.net launcher says there’s update and fails to apply it. Tried fixing installation but it fails too with same message. I had same problem with beta. It allows me to log in normal when I have done fresh installation while game is still not 100% downloaded. But after installation has finished or i restart computer same message appears. I use same programs etc for security on my laptop and all works some I don’t think its becaause of them. If i uninstall and reinstall i can play while game is downloading, But if try to play after full install or computer restart i doesn’t work anymore.
Hey there,
So the error BLZBNTAGT00001389 is a Blizzard BattleNet Agent Error, and it pretty much mean what it says in that the update agent is unable to obtain data or apply data to itself or the affected client. This points to either a local network issue or something on the system interfering with the desktop application itself. The following steps should help.
Try doing a power cycle on your system. Turn off all devices including the modem. Wait 60 seconds, turn on the modem, wait 5 minutes, turn on any network devices, wait 2 minutes, turn on your computer and try the game.
You can try switching your DNS settings to use a free public DNS servers instead of your ISPs Servers:
We do not have individual steps for specific modems or routers so if you need assistance accessing or updating the devices, contact the device maker/provider.
In some cases there is a corrupt or misconfigured setting within the router or modem. We cannot say what that might be offhand but the easiest way to resolve these conflicts would be to factory reset the router and/or modem.
You may need to look up your specific model for the steps on how to do this and in some rare cases you may need to have this done by the ISP. Feel free to reach out to them for assistance if necessary.
Let’s manually clear the Battlenet Desktop Application and all supporting data from the system. This will not remove existing game clients.
Try running your system in selective startup mode: https://battle.net/support/article/200483
Create a new administrator account: Blizzard Support - Creating a New Administrator Account
Once the account is created, shut down the computer, wait 60 seconds, restart, log into the new profile and try the app/client.
If that doesn’t solve the issue, then I recommend submitting a ticket with an msinfo attached for further investigation. (instructions for collecting that msinfo report will be on the form.)
Click your name at the top right of this page, click support, click contact support.
Hey. I was having this same error code and the advice above did not help me. However, deleting my “Data” folder inside of my Diablo 4 folder finally cleared the error code.
Had the same error code with Call of Duty Vanguard. Did what BigBeebus suggested and fixed the problem. Specifically, I deleted the “Data” folder inside Vanguard folder, updated the game which restored the Data folder and now the game works fine. Thanks BigBeebus!!
what fixed my battlenet log in issues was going to firewall.cpl and disabling firewall for both public and private then launching battlenet, signing in, then reenabling firewall once I was logged in to battlenet
Hope this helps
Unfortunately, nothing suggested so far has fixed the issue for me over the past month. The only help has been reinstalling/deleting data, but that’s only temporary. The error returns the next time there’s an update and I have to reinstall again.
But I may have finally found the culprit: Backblaze (cloud backup software). It seems to be preventing Bnet from accessing files during the update process and Bnet responds by throwing this error. I’m still testing—it’s tough to verify because I have to wait for one of the installed games to have an update before I can test and then I only get one shot at it until another update rolls around—but it seems promising so far.
So I’m posting the info anyway in case anyone else is at their wits’ end like I am and wants something else to try while waiting for updates to test with.
TL;DR steps to try if you have a cloud backup application installed:
Here’s detailed info on what I’ve tested with Backblaze specifically, for anyone who’s curious. The support response to my open ticket heavily favours this being a networking issue (so I’m sure that’s what the majority of these cases are!), but I wasn’t feeling that at all in my case. So this info may be useful for anyone else who’s also grokking this as a file system/permissions issue in their case as well…
I started by completely killing all Backblaze processes, which isn’t easy outside of Safe Mode and why previous attempts to have “nothing else running in the background” while attempting to update weren’t fruitful. (It really likes to hide processes and even removing it from startup doesn’t prevent it all from running. I had to use 3rd party software to figure some of them out. For Backblaze, you can search the Task Manager for anything that starts with ‘bz’ and killing all those should be enough from what I’ve seen in testing.) When I did this, I was finally able to at least run a Scan and Repair on Diablo IV, which hadn’t been possible before and kept throwing this error. So that was promising. The Scan and Repair basically “reinstalled” Diablo IV, which always temporarily fixes the issue for me so I had to wait for another update to try again.
WoW had an update a few days later. Backblaze was running again after an unrelated reboot but was NOT currently in the process of backing anything up according to the Control Panel. So the processes were running but the backup itself was idle. Still, attempting the WoW update threw the error as usual. 
I killed all of Backblaze and Bnet still threw the error. I killed and restarted Bnet (Backblaze still not running) and WoW updated without throwing the error. So it seemed like Backblaze was indeed the conflict, whether it was backing up or not. I didn’t relaunch it and planned to wait for another update to test again.
Except I need Backblaze to always be running or it defeats the entire purpose, and killing it every time I need to update is annoying, so I was trying to figure out a solution in the meantime. In my case, all my games are installed on a separate (internal) drive partition that’s just for games, G:\ . So, since I don’t care about Backblaze actually backing up that drive at all, I told it to ignore G:\ completely to see if maybe that would solve it. The next game with an update was Overwatch but it was still throwing the error even with G:\ ignored. I killed Backblaze and restarted Bnet and the update worked just fine again. Tried this same method again, with Backblaze running but ignoring G:\ , when I noticed Diablo III also had an update. That also still threw the error but worked just fine with Backblaze completely killed. So yeah, it’s probably Backblaze and I was super annoyed that I couldn’t run Backblaze and update Bnet games at the same time.
Last ditch effort: I usually have Bnet on G:\ but remembered I’d actually reinstalled it to C:\ when trying other things to fix this error. Backblaze was still backing C:\ up (and you can’t tell it not to) so I figured what the hell and moved Bnet back to G:\ and left G:\ ignored. There was an Overwatch update earlier today and Backblaze was running. It was even in the process of backing up some files on C:\ . I pressed the update button anyway to see what would happen. No error. Overwatch appears to have successfully updated just fine with Backblaze running but ignoring the drive Bnet is installed on.
So, yeah. Backblaze is most likely conflicting with Bnet itself (data/cache files in the installed Bnet folder during an update maybe?). But like I said, testing is hard to replicate with the waiting so I want to see if having Backblaze running but ignoring the drive will continue to work on a couple more updates before I call it solved heh. Also, to be fair, the Overwatch update that worked was a very small, nano-second one. The updates in the past that threw the error were much larger.
Oh, I’ll also note that this isn’t an issue on Windows 10. This is a new machine running Windows 11 but is set up exactly the same as my Windows 10 machine, down to the drive letters and installation locations of all the software involved (though the hardware is different). Backblaze and Bnet don’t have this conflict on the Windows 10 machine. So maybe this is just a coincidence and the cause is something else, or maybe there’s something specific about how Backblaze and/or Bnet run on Win11 that causes the conflict.
In any case, I’m leaving Bnet and the games installed on G:\ with Backblaze ignoring G:\ to see what happens. Hopefully I’ll be able to run multiple updates with no error and this has finally solved the issue for me. Please, for the love of Yogg, let that be true.
I was able to update Overwatch again the other day and Diablo IV just now with no errors so I’m calling this solved in my case. The cause was indeed Bnet and Backblaze conflicting on Windows 11.
Putting Bnet on a drive that’s permanently excluded from the Backblaze backup (via Backblaze > Settings > Select Hard Drives to Backup) prevents the conflict and lets you update/Scan and Repair with no issues. If that’s not possible for you and you need to back up the drive with Bnet on it, you’ll need to kill all Backblaze processes any time you want to update a game via Bnet (kill Backblaze, close Bnet and wait or kill the leftover processes, relaunch Bnet, update).
Im having this problem for call of duty mww2 and I tried deleting it and installing it and also deleting the whole blizzard app and a lot of more ways that I could find on youtube and nothing has changed and its nothing wrong with my computer because I am playing other call of duties on the steam app and I don’t see this issue, can you guys please fix this as soon as possible.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.