To fix this problem, you’ll need to delete the Reselog.txt file. Blizzard’s install agent will check this log and might decide to terminate the connection with your computer under certain conditions. TCP or IP log contains inconsistent data – Every network connection will auto-generate a log in regards to the incoming and outgoing connections.(and Blizzard products in general) don’t play well with these types of products. Interference caused by Proxy or VPN client – If you’re using a Proxy or VPN client to block servers from detecting your location, you might want to disable these (at least while you carry out the installation of ).Several affected users have confirmed that they were able to fix the problem by creating a new Administrator account for their Windows installation and doing the installation from the new account. Corrupted administrator account – According to some affected users, this problem can be related to an inconsistency resulting from a corrupted administrator account.In this case, a quick power cycle procedure performed on your router should resolve the majority of issues. Network inconsistency – If you’re experiencing other issues aside from the fact that you’re unable to install Blizzard’s launcher, the problem can also result from a network inconsistency.If this occurs, you should be able to allow the installation to happen regardless by temporarily disabling the Antivirus suite and/or the firewall component. Overprotective AV suite – If you’re trying to install an older build of, the installation might be flagged as a false positive by certain AV suites because of an expired publisher certificate.To fix this issue, you’ll need to reset the WMI component from an elevated CMD prompt. Conflicting meta-information – As it turns out, a corrupted WMI (Windows Management Instrumentation) repository can also cause installation problems with, especially if you had the client installed in the past.In this case, you should delete the and Blizzard Entertainment folder (from the %ProgramData% folder). The conflict is caused by remnant files – If you get this problem while attempting to update your current app or you’re trying to re-install the launcher after having it installed in the past, chances are some remnant files are blocking the installation.If this scenario is applicable, you should be able to avoid the error by doing the installation from a clean boot state. Conflicting process or startup service – According to some affected users, you can expect to deal with this issue in situations where a non-Microsoft service or process is running in the background and conflicting with the installer.Once the account is created, shut down the computer, wait 60 seconds, restart, log into the new profile and try the game. Ok, if all else fails let us try this one last thing.

Try running your system in selective startup mode. Now reinstall the app to the C: Drive and have it relocate your games. Repeat steps 2 and 3 with %LOCALAPPDATA% and %TEMP% Delete the Bnet and blizzard folders inside the appdata folder if they exist.Ĥ. Type the following into the address bar (not the search bar): %APPDATA%ģ. 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.ĭo not reinstall yet but follow these additional steps:Ģ. Turn off all devices including the modem. Make Sure your OS and Video Drivers are up to date: I have a few things you can try that may help you out here but if the issue persists, I would ask that you submit a direct ticket for further assistance. This can be caused by a corrupt client, a bad security permission, interference from another program on the system or a permission issue with windows itself. The app is trying to apply data to the game client and it can't. So what you are describing is generally caused due to a permission/access issue.

Battle.net will not open