Here’s how to fix Battle.net launcher not opening in 6 steps
Blizzard’s Battle.net client is a sturdy and reliable piece of software. It’s there for ages and it’s the best indicator of a remarkable approach Blizzard takes when it comes to a game distribution.
However, even the top-notch game launcher/desktop client runs into problems occasionally. Some users reported that Battle.net launcher won’t even start or crashes unexpectedly while initializing.
Since there’s a variety of possible culprits for this occurrence, we made sure to cover all of them. So, if Battle.net launcher won’t open after several tries, don’t worry — you’re at the right place. The enlisted solutions can be found below.
How to fix Battle.net launcher not opening in Windows 10
- Run Battle.net launcher as admin
- Clear launcher’s cache
- Check the antivirus and firewall
- Disable background programs
- Enable the Secondary Logon service
- Reinstall the Battle.net launcher
Solution 1 – Run Battle.net launcher as admin
The Battle.net desktop app is mostly stable and it integrates easily with the Windows 10 platform. Nonetheless, this one part of the client is there to run the related games and that’s where it can collapse.
Without the proper administrative permissions, Battle.net launcher won’t work as intended or won’t even start. So, what you’ll need to do is to grant it the administrative permission and make sure that it can connect freely to dedicated servers.
Here’s how to give Battle.net launcher the administrative permission:
- Navigate to C:\Program Files (or Program Files x86)\Battle.net.
- Right-click on the Battle.net Launcher.exe and open Properties.
- Choose the Compatibility tab.
- Check the ”Run this program as an administrator” box and confirm changes.
Additionally, since the stuck mostly occurs while updating the client, we advise you to check your connection settings. Here are some steps you can take to troubleshoot the connection issues:
- Flush DNS.
- Use wired connection.
- Restart your router or modem.
- Reset router and/or modem to factory settings.
- Run Windows Internet Connection Troubleshooter.
If you’re positive that everything is just fine with your connection, we can safely move to the next step.
Solution 2 – Clear launcher’s cache and delete Tools folder
Just like any other application, the Battle.net launcher stores a lot of secondary data responsible for its seamless processing and configuration.
Now, every given file can get corrupted or incomplete and thus the related program will fail. Sometimes you can repair those files, but, more times than not, you’ll need to delete them and let the application rebuild them from a scratch.
That’s just what you’ll need to do with the Battle.net launcher in order to address this issue.
Now, follow these steps to delete Cache and Tools folder in Program Data:
- Right-click on the Taskbar and open Task Manager.
- Kill these processes:
- Game process
- Agent.exe or Blizzard Update Agent.exe
- Blizzard Battle.net
- Close Task Manager and press Windows key + R to open the Run command line.
- In the command line, type C:\ProgramData and press Enter.
- Find Battle.net folder and delete it.
- Start Battle.net again and look for changes.
- READ ALSO: How to fix Battle.net startup crashes
Solution 3 – Check the antivirus and firewall
We already stressed the fact that the Battle.net launcher tends to fail to start if there’s no connection. But, most of the time the problem isn’t connection-related.
Sometimes the third-party antivirus or firewall are preventing the Battle.net launcher to reach the dedicated servers and update.
This isn’t exactly a rare occurrence so it’s well advised to either disable the antivirus or to create an exception (exclude the Battle.net folder). Either way, we don’t recommend to completely remove the antivirus due to obvious security risks.
Furthermore, there’s also a Windows Firewall as a possible reason for Battle.net’s inability to start. If you’re not sure how to allow the Battle.net launcher to communicate through Windows Firewall, follow the steps below:
- Type firewall in the Windows Search bar, and open Windows Firewall.
- Click on the ”Allow an app or feature through Windows Firewall” in the left pane.
- Choose to Change settings.
- Click on the ”Allow another app” button.
- Click on Browse and navigate to C:\Program Files (or Program Files x86)\Battle.net.
- Add Battle.net Launcher.exe and confirm changes.
After that, Battle.net launcher halt should be resolved. If that’s not the case, then, by all means, check the last two steps.
Solution 4 – Disable background programs
Some background programs might prevent the Battle.net launcher to start. There’s a large variety of applications that can affect this desktop client, and it’s often stressed out by Blizzard support to try and disable them before everything else. Now, even though you’re aware of this, it can take a lot of time to individually disable programs and look for improvements.
So, the best way to find out is some other third-party program preventing the Battle.net launcher is to try the selective startup mode.
Here’s how to do it:
- In the Windows Search bar, type and open System Configuration.
- Select the Selective startup.
- Uncheck the ”Load startup items” box.
- Now, navigate to the Services tab.
- Check the ”Hide all Microsoft services” box.
- Click on the Disable all and then OK to confirm changes.
- Finally, restart your PC and start the Blizzard again.
With this, you’ll at least be in the clear in regard to the negative impact of third-party programs. If the client starts — good, if not — move to additional steps.
Solution 5 – Enable the Secondary Logon service
Another rarely used service and another possible solution for your problem. Namely, Secondary Logon service is there to avoid multiple logon-logoff actions, so you can basically run a certain program with administrative permissions from the non-administrator account. And, for some peculiar reason, the Battle.net launcher heavily depends on this service so you’ll need to enable it.
In order to do so, follow the steps below:
- Type services in the Search bar and open Services.
- Navigate to the Secondary Logon service, right-click on it, and open Properties.
- Change the Startup type to Automatic.
- Start the service and confirm changes.
- Restart your PC in order to apply changes.
Solution 6 – Reinstall the Battle.net launcher
Finally, if all of the previous solutions were futile, the reinstallation is our last resort. A lot of users plagued by this problem tried to resolve it by reinstalling the desktop application right away. However, even though you remove the installation files from the Program Files folder, there are still files residing in the Program Data folder.
So, basically, everything stayed the same once the app is reinstalled. Therefore, in order to completely uninstall the Battle.net desktop app and resolve the problem, follow these instructions:
- In the Search bar, type control and open Control Panel.
- Choose Category view and open Uninstall a program.
- Uninstall a Battle.net desktop client from your PC.
- Now, press Windows key + R to open the Run dialog box.
- Type C:\ProgramData in the command line and press Enter.
- Delete the Battle.net folder.
- Restart your PC.
- Download the Battle.net installer here and install it.
That should resolve your issues and you should be able to run the Battle.net launcher and its respective games without trouble. In case you’re still stuck with the problem, the only thing we can suggest is to reinstall the system. The whole procedure is explained in this article so make sure to check it out.
That’s the closure. If you have questions regarding the Battle.net launcher or alternative solutions, feel free to tell us in the comments section below.
RELATED STORIES YOU SHOULD CHECK OUT:
- Fix: Battle.net Payment Authorization error
- Overwatch players want a stormy weather map: Will Blizzard add it to the game?
- How to repair Blizzard games: Here’s a quick tip
- Is your Blizzard app stuck initializing? Here’s how to address it
Microsoft is all set to launch its next big update, Windows 10 version 1809 in October. While that should be a nice piece of news […]
The Windows 10 October 2018 Update (otherwise 18H2) rollout might now be two to three weeks away. For the last few months, new build previews […]