WMI Fix For Many Battle Net Agent Errors - BLZBNTAGT0000138F

After troubleshooting and attempting many of the recommended solutions and none working from Blizzard Tech Support and not finding this posted elsewhere on the forums, this method resolved many of the endless Agent.exe not installing after being uninstalled, Update Agent Loops and unhelpful “BLZBNTAGT0000138F - Whoops! Looks like something broke. Give it another shot.” errors, etc. I was having and allowed the Battle Net Agent to be installed and work correctly again.

Rebuild your WMI Repository:
While Blizzard’s recommend method for resetting the WMI Repository (hxxps://us.battle[.]net/support/en/article/257703) may work in some cases, a better more comprehensive solution is rebuilding the WMI repository using this method (hxxps://techcommunity.microsoft[.]com/t5/ask-the-performance-team/wmi-rebuilding-the-wmi-repository/ba-p/373846) which works on Windows 10 and below:

You should also note to make a save point/back up before you rebuild the WMI repository.

Re-register all of the dlls and recompile the .mofs in the wbem folder and re-registering WMI Service and Provider. You can use the following script by saving to txt file then renaming to .bat and running from command prompt or powershell prompt with admin rights and changing focus to following directory: C:\Windows\System
Create batch file using this script:

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in (‘dir /b *.dll’) do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s

To run this script:

  1. Open Notepad.
  2. Copy and paste the above code into Notepad.
  3. Save the file with a .bat extension (for example, wmi-rebuild.bat).
  4. Right-click on the saved file and select “Run as Administrator”.
  5. Reboot the machine and test WMI

Next, check the repository for consistencies:

For Windows 7 and above, you can run from an elevated command or powershell prompt.
winmgmt /verifyrepository

If repository is found to be inconsistent:

a. For Windows 7 and newer, run from elevated command or powershell prompt:

Winmgmt /salvagerepository

Note this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable

If the above doesn’t work, then run:

Winmgmt /resetrepository

Note this will reset the repository to the initial state when the OS was first installed

Again, it’s important to note that this script makes changes to system-level settings and should be used carefully. Running such scripts can potentially cause system instability if not used correctly. Always ensure you have a backup of any important data before running such scripts.

1 Like

Hi, and what to do if you don’t have damned Windows…?

@GoldWight

There can be a number of potential causes for the error mentioned and most of them come down to access restrictions/blocks/corruption

While the above mentioned solution can help, a corrupted WMI repository isn’t the only thing that can contribute to this particular error.

Broken/corrupted admin permissions, firewall/security blocks on the system or network, corrupt client data, interference from other programs on the system, to using a Case Sensitive file format or drive encryption software like file vault.

I cannot say what might be the cause for your particular issue. I do know we have seen a few reports of this error recently and are investigating but for the most part localized troubleshooting has helped. So with that in mind here are some system agnostic or mac specific steps you can try:

Try doing an extended power cycle on your system. Turn off all devices including the modem. Wait 30 minutes, 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.

Perform the steps listed on this article to remove the Blizzard Desktop Application from the system: Blizzard Support - Uninstalling the Battle.net Desktop App (For mac there will be some specific files listed that need to be manually removed)

Try running your system in selective startup mode: https://battle.net/support/article/200483

Our clients do not support installation on encrypted drives using programs such as File Vault. There can be issues installing, updating, launching or connection issues due to the encryption. If drive encryption has been enabled, please disable it and allow the drive to decrypt: Blizzard Support - Checking for FileVault

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.

Hi Kershew,

I am on Mac and I have this exact error. I went through each article, and did a complete uninstall and delete of Battle net client, including all the folders in Mac Library and other places listed in the articles.

I downloaded newest bnet client off website, logged in with account and selected World of Warcraft Classic. It just stalled on initializing forever, and then gave the same error BLZBNTAGT0000138F saying something went wrong. I installed WoW Dragonflight on this same Macbook before without an issue. It installs Warcraft 3 just fine, and recognized Warcraft 3 when I reinstalled battlenet client. For whatever reason it will not download WoW Classic client.

I tried making a support ticket but ironically I got an error trying to submit that as well. I am out of options here - any further ideas?

1 Like

I’m having the same problem on Macbook pro 16" 2021. Can`t install Word of Warcraft. Every time error. Diablo III can be installed without any problems. :frowning:

1 Like

Same problem here. Any ideas?

Same issue here. On Mac.

So if the steps I provided above are not helping, I recommend submitting a ticket with some system files and connection data so our agents can work with you directly.

Right click your name at the top right of this page, click support, then click contact support.

Include the following along with your description of the issue and what steps you have done already so they don’t repeat them unless necessary.

System Reports: Blizzard Support - Obtaining System Files

Ping Plotter: Blizzard Support - Running PingPlotter

1 Like

Same problem here on Mac

1 Like

I dong want Dita bundel

Posts such as this, make me feel as if they some how got agitated by your repair and needed to add their own attempts at it.

Have mac, and problems started happening about 3-4 weeks ago and in the last week I upgraded to Ventura and now I get this error and because now I can’t update the game, i got kicked out as everything is incompatible because i can’t update. Yay… bye bye sub.

Hi, I met this stupid issue too and I googled a lot. Here I can share you my thought and solution.

We all know that Blizzard shut down their service in China. However, their app is still trying to get the patch from the server that was located in China, and here is why battle.net can’t get the patch.

To solve this problem. you just need to edit your host file which is located at “C:\Windows\System32\drivers\etc”. Before you start, use cmd to ping a non-Chinese Battle.net v2 Patch Service, like US server. And you will get an IP address. Link this IP with cn.pat ch. batt lenet .co m.c n(remove space), and try to launch your application again.

Hope this can help you. Good luck.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.