Battle Net Not Connecting | Fix It Fast On Windows

You click Log In, the spinner turns, and then nothing. Or you get stuck on “Connecting” while your games sit there, ready to go. This guide walks you through a clean, no-drama path to get Battle.net online again, starting with the checks that save the most time.

Work top to bottom. Stop as soon as it connects. Each step has a clear “why,” so you’re not tossing random fixes at your PC.

Fast Checks Before You Change Anything

If the launcher can’t reach Blizzard’s login services, no local tweak will help. So start with quick reality checks, then move into device-side fixes.

• Check Blizzard service status — Open the official status page and look for Battle.net or game service incidents. If there’s an incident, wait it out and retry later. Blizzard service status
• Try a web login — Sign in on the account site in a browser. If the site won’t load or sign-in fails, the issue is wider than the desktop app. Battle.net account sign-in
• Reboot your network gear — Power off your modem and router, wait 30 seconds, power them back on, then retry after Wi-Fi settles.
• Switch to a different connection — Test wired Ethernet, a phone hotspot, or a second Wi-Fi network. If it works elsewhere, your main network path is the culprit.

When the status page is green and a different network works, you’ve already narrowed the problem to your PC, router, or ISP routing.

Battle Net Not Connecting On PC After An Update

Updates can change two things at once: the launcher files and the way your security tools see the launcher. That’s why “it worked yesterday” is common right after a patch.

Start with the launcher process

• Exit Battle.net fully — Right-click the Battle.net icon in the system tray and choose Exit, then wait a few seconds.
• End stuck tasks — Open Task Manager and end Battle.net.exe and Agent.exe if they’re hanging.
• Run as admin once — Right-click the Battle.net shortcut and choose Run as administrator, then try logging in.

Check your system clock

Bad time sync can break secure connections. It’s a small thing that causes big headaches.

• Sync time automatically — In Windows Settings, turn on Set time automatically, then click Sync now.

Confirm you are not in offline mode

The launcher can enter offline mode after a failed sign-in. Switching modes can clear a stuck login screen.

• Toggle offline and back — If you see an Offline option in the launcher menu, switch to Offline, then back to Online and retry.

If you still see endless “Connecting,” move on to the network steps. Most persistent cases come down to DNS, proxy settings, or filtering software.

Network Fixes That Clear Login Blocks

Battle.net uses normal web traffic plus game traffic. When DNS records go stale or your IP lease gets messy, login can fail even while other sites load.

Remove VPNs and proxies

• Turn off VPN apps — Close the VPN and stop it from auto-starting, then retry sign-in.
• Disable proxy settings — In Windows Network & Internet settings, make sure Use a proxy server is off.

Refresh IP and DNS on Windows

Blizzard’s own connection steps include renewing your IP and flushing DNS to clear conflicts. Blizzard connection troubleshooting

1. Open Command Prompt — Search for cmd, right-click it, then choose Run as administrator.
2. Release your IP — Type ipconfig /release and press Enter.
3. Renew your IP — Type ipconfig /renew and press Enter.
4. Flush DNS — Type ipconfig /flushdns and press Enter.
5. Restart the PC — Reboot to clear any leftover network locks.

Swap to a clean DNS resolver

If your ISP DNS is slow or returns bad routes, Battle.net may time out. Switching DNS is reversible and safe.

• Set DNS to Google — Use 8.8.8.8 and 8.8.4.4 on your adapter, then reboot and test.
• Set DNS to Cloudflare — Use 1.1.1.1 and 1.0.0.1, then reboot and test.

Test for ISP routing trouble

If a hotspot works but your home line fails, the route from your ISP to Blizzard can be the issue. In that case, the best move is to keep playing on the hotspot for a short session, or try later on the home line.

Firewall And Port Rules That Break Battle.net

Security tools can block the login module, the update agent, or the game ports. Blizzard’s guidance calls out firewalls, router settings, and security apps as common blockers. Connection troubleshooting steps

Allow the launcher and agent through Windows Firewall

1. Open firewall settings — Search for Windows Defender Firewall, then open “Allow an app through firewall.”
2. Allow Battle.net files — Check Battle.net Launcher and Blizzard Update Agent for Private networks, then retry.
3. Add missing entries — If they’re not listed, use Allow another app and browse to the install folder.

Ports you may need on strict networks

Most home networks do fine with default rules. Schools, workplaces, and locked-down routers may need ports opened. The list below matches common Battle.net platform ports seen across documentation and network references. Use it only when you control the router or firewall.

Port numbers vary by title and mode. If you’re troubleshooting one game, check that game’s own network article too. If opening ports fixes it, keep the rule as tight as you can: only the ports you need, only to your gaming PC.

After any firewall or router change, reboot the PC and the router, then test once. Multiple rapid retries can trigger temporary rate limits that look like another network failure.

Fix a broken Hosts file entry

A modified Windows Hosts file can misroute Blizzard domains. Blizzard flags this as a cause for connection failure and recommends checking for bad entries. Can’t connect to Battle.net app

• Reset Hosts to default — Use Microsoft’s documented reset method, then reboot and retry.

Repair The Battle.net App And Its Cache

When the network is fine, the launcher itself is often the problem. Corrupted cache files can trap the app in a login loop. Blizzard’s fix list includes deleting the Battle.net Tools folder so the app rebuilds fresh files. Battle.net Tools folder steps

Clear the Tools folder safely

1. Exit the launcher — Close Battle.net from the system tray so Agent stops.
2. Open the ProgramData path — In File Explorer, go to C:\ProgramData\Battle.net\.
3. Delete the Tools folder — Remove Battle.net\Tools, then restart the launcher and sign in.

Remove cached login data

If your login screen loads but keeps failing, cached tokens may be stale.

• Clear Battle.net cache — Delete the Battle.net cache folders listed in Blizzard’s desktop app troubleshooting article, then reboot. Desktop app troubleshooting

Reinstall without leaving junk behind

Reinstalling works best when you remove the leftover cache, then install the newest installer.

1. Uninstall Battle.net — Use Windows Apps, then reboot.
2. Delete leftovers — Remove any remaining Battle.net folders in ProgramData and AppData, then reboot again.
3. Install the latest client — Download the installer from Blizzard’s official download page and install.

At this point, most “battle net not connecting” cases are solved. If yours still fails, it’s time to check for edge cases like account limits, regional routing, or third-party overlays.

Less Common Causes That Still Happen

Some failures look like network trouble but come from a local conflict. These checks are quick and safe.

Background apps that hook network traffic

• Close overlay tools — Shut down screen recorders, FPS overlays, and packet filters, then retry.
• Pause security scans — Temporarily pause real-time scanning while you test sign-in, then turn it back on.

Old router firmware

Blizzard notes that outdated modem or router firmware can break complex game connections. If you control the hardware, check the maker’s update page and apply the latest firmware, then reboot the device. Router firmware note

Wi-Fi quirks

• Move closer to the router — Weak signal can cause retries that look like a login hang.
• Swap bands — Try 5 GHz if you’re on 2.4 GHz, or switch the other way if 5 GHz is unstable.
• Turn off power saving — In Device Manager, disable “Allow the computer to turn off this device” for your Wi-Fi adapter.

Account and authentication issues

If the app launches but login fails with account errors, test sign-in on the web and check for account security prompts. A browser sign-in that works while the app fails points back to the desktop cache steps above.

Common error codes and what they usually mean

Error codes are clues, not mysteries. Write the full code down, then match it to the simplest fix first.

• BLZBNTBGS7 — A network timeout. Try the DNS flush and a different network before you reinstall.
• BLZBNTAGT00000 — The update agent can’t reach servers. Check proxy settings, then firewall rules for Agent.exe.
• BN-564 — Downloads are blocked or throttled. Reboot the router, then try wired Ethernet for one test run.

If you need proof for a help ticket, the launcher keeps logs on your PC. Open the Battle.net settings, go to App, then use the option that reveals the log folder, and attach the newest file.

A One-Page Checklist You Can Run Every Time

This is the flow that keeps you from bouncing between random fixes. Print it, save it, or keep it in a notes app.

1. Check status first — If Blizzard services show an incident, wait and retry later. Status page
2. Swap networks — Test a hotspot or a second Wi-Fi to separate ISP trouble from PC trouble.
3. Kill stuck tasks — End Battle.net.exe and Agent.exe in Task Manager, then relaunch as admin once.
4. Flush DNS and renew IP — Run the three ipconfig commands, reboot, then test. Blizzard connection steps
5. Disable VPN and proxy — Turn them off, then test sign-in again.
6. Allow through firewall — Confirm Battle.net Launcher and Update Agent are allowed on Private networks.
7. Delete Tools cache — Remove the Tools folder so the launcher rebuilds clean files. Tools folder fix
8. Reinstall cleanly — Uninstall, delete leftovers, reboot, then install the latest client.

If you’ve run the list and the launcher still won’t connect on two different networks, collect details before reaching Blizzard’s help team: your region, your ISP, the exact error code, and the time it happened. That short note speeds up the next step.

One last tip: after you fix it, leave your network settings alone for a day. When a change works, you want a stable baseline, not a fresh set of variables today.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback