Battle Net Not Logging In | Fix Login Loops Fast

The Battle.net app sits between your PC and Blizzard’s servers. When anything in that chain misfires, you can get stuck on “Logging In,” “Connecting,” a blank window, or repeated credential prompts. The good news is most login failures come from a short list of causes, and you can test them in a clean order without reinstalling your whole setup.

This guide walks you through fixes that work on Windows and macOS, plus what to do when the problem is on Blizzard’s side or tied to account security. Start with the fastest checks, then move to deeper resets only if you still can’t sign in.

Check For Outages Before You Change Anything

When login breaks for lots of players at once, local fixes won’t stick. Take one minute to rule out an outage so you don’t burn time wiping files that were fine.

• Open a Blizzard status page — If you play World of Warcraft, the official realm status list can confirm downtime and scheduled maintenance for EU realms.
• Try the web login — Sign in on Blizzard’s account site in a browser. If the site can’t sign in either, the issue is rarely your PC.
• Check another network — Hotspot your phone for a single login attempt. If it works there, your home network or ISP path is the bottleneck.

If there’s clear downtime, wait it out and avoid repeated login spam. Too many attempts in a short window can trigger extra security checks.

Battle Net Not Logging In On Windows And Mac

If the service is up, start with local cleanup. The Battle.net app keeps cached data and update-agent files that can get stale or corrupted. Clearing them is faster than reinstalling and often fixes the “stuck on starting” and “can’t connect” style loops.

Close The App Fully First

• Quit the launcher — Exit Battle.net from the system tray (Windows) or menu bar (Mac) so it isn’t still running in the background.
• End leftover processes — In Task Manager or Activity Monitor, close any Battle.net or Agent processes that stay open after you quit.

Clear Battle.net Cache And Tools Data

Blizzard’s own “can’t connect” checklist points to deleting the Battle.net Tools folder so the app rebuilds its local files on the next start. This reset is safe because it recreates what it needs.

• Delete the Tools folder on Windows — Close the app, then remove the Battle.net “Tools” folder from ProgramData so the Agent rebuilds it on launch.
• Clear cache folders — Remove the Battle.net cache folders in ProgramData/AppData (Windows) or the equivalent cache paths on macOS, then restart the app.
• Restart the computer — Reboot after cleanup so no locked files remain in memory.

If you’re not sure where those folders live, use OS search and paste the paths into the location bar. You’re looking for cached web data, not your installed games, so you won’t lose game files.

• Check ProgramData on Windows — Look under C:\ProgramData\Battle.net and C:\ProgramData\Blizzard Entertainment for cache and Agent folders.
• Check AppData on Windows — Look under %AppData% and %LocalAppData% for Battle.net cache folders, then delete the cache, not game folders.
• Check Library on macOS — Look under ~/Library/Caches and ~/Library/Application Data for Battle.net items, then clear the cache entries.

If you’re on a work or school connection, proxies can block the login module even when normal browsing works. Blizzard’s “stuck on starting” steps call out proxy disabling as a first test.

• Turn off proxies on Windows — In Internet Options, disable proxy settings, then restart the Battle.net app.
• Turn off proxies on macOS — In Network settings, clear any proxy boxes, apply changes, then try logging in again.

If the app is stuck on “Starting…” for more than a few minutes, Blizzard’s guidance suggests disabling proxies and trying a direct modem connection for a quick test. That hints at a network layer issue, not a bad password.

Do A Clean Reinstall Only After Cache Steps

• Uninstall Battle.net — Remove the desktop app using your OS uninstall tool.
• Delete leftover folders — Remove remaining Battle.net folders in ProgramData (Windows) or Library (Mac) so you don’t reinstall on top of broken files.
• Install the latest build — Download a fresh installer from Blizzard’s site and install with admin rights on Windows.

Fix The Network Path That Blocks Sign-In

Login can fail even when your password is correct if your network blocks the authentication module. Home routers, VPNs, DNS issues, and security software can all break the handshake. Work through the checks below in order so you change one thing at a time.

Start With Simple Connection Checks

• Reboot modem and router — Power them off for 30 seconds, then bring them back up in that order.
• Use a wired connection — Plug in Ethernet for a single login attempt to rule out Wi-Fi dropouts.
• Pause VPN apps — Turn off any VPN or “secure tunnel” tools and try logging in again.

Reset DNS And Local Network Settings

• Flush DNS on Windows — Run ipconfig /flushdns in an admin Command Prompt, then retry the login.
• Renew your IP lease — Run ipconfig /release, then ipconfig /renew, then try again.
• Switch DNS servers — Set your adapter to a public DNS resolver, then restart the Battle.net app.

Check Firewall, Security Tools, And The Hosts File

Blizzard’s troubleshooting list calls out firewalls, routers, and the Windows Hosts file as common blockers. A single bad entry can redirect Blizzard domains to nowhere.

• Allow Battle.net through firewall — Add Battle.net and Agent as allowed apps in Windows Firewall or your third-party firewall.
• Temporarily disable web filtering — Turn off “HTTPS scanning” or web shields for one test login, then turn them back on.
• Reset the Hosts file — Remove nonstandard entries that point Blizzard domains to custom IPs.
• Update router firmware — Old firmware can glitch on long-lived connections, so update if you’re behind.

Handle Account Security, Locks, And Authenticators

If you can sign in on the web but the app rejects your login, check the account-side items next. A device prompt, SMS check, or authenticator issue can block the desktop app until you confirm the login on your account page.

Confirm You’re Using The Right Region And Account

• Select the correct region — Use the region selector on the login screen, then enter your credentials again.
• Try email, not BattleTag — Sign in with your account email to avoid typos in your BattleTag.
• Reset the saved login — Clear saved credentials in the launcher settings, then type them fresh.

Fix Authenticator And Phone-Check Problems

Blizzard’s authenticator removal page notes that you can manage security options when you still have access, and that account restore is the path when you can’t log in. If your authenticator is out of sync, a single step can get it back on track.

• Sync your phone time — Set your phone to automatic date and time so one-time codes match server time.
• Use backup login options — If you enabled phone notifications, approve the prompt instead of typing a code.
• Start account restore — Use Blizzard’s restore flow if you lost the authenticator device or codes.
• Request authenticator removal — Use the Blizzard help portal option to remove an authenticator that blocks access.

Watch For Temporary Locks

Too many failed attempts can trigger a short lock window. If your password is correct but you just tried it ten times, take a break, reset the password once, then sign in once.

• Wait 15–30 minutes — Stop attempts for a short window so the lock timer can clear.
• Change your password — Update it on the account site, then sign in on the desktop app with the new one.
• Check email alerts — Look for security emails that ask you to confirm a new login or location.

Tackle Error Codes And Stuck Modules The Smart Way

Some login failures show a code like BLZBNTBNA00000005 or a “sleeping Update Agent” message. The code text can change, yet the fix pattern stays similar: clear local Agent data, fix network blocking, then retry.

When Battle Net Not Logging In Follows An Update

Updates can leave half-written files if your PC sleeps mid-download or your antivirus interrupts a patch. Start by clearing the Tools data and then relaunching so the Agent pulls a clean set of files.

• Run the app as admin — On Windows, right-click Battle.net and run it with admin rights for one launch.
• Disable sleep during updates — Keep the PC awake until the launcher finishes its patch check.
• Change installation folder only if needed — If your drive has permissions issues, reinstall to a simple path like C:\Games.

When The Login Screen Loads But Won’t Submit

If you can type credentials but the button does nothing, the embedded web view is often blocked by security software, ad blockers, or a restricted network profile. Try a clean boot style test with fewer background tools.

• Disable overlays — Turn off GPU overlays and screen recorders for one test login.
• Pause browser extensions — If you use a system-wide blocker, pause it for the launcher test.
• Try a new Windows user — Create a fresh user profile and try the app there to rule out profile corruption.

Prevent The Next Login Failure With Quick Habits

Once you’re back in, a few habits can reduce repeat loops. These steps don’t add chores. They just keep the launcher and your account from drifting into a bad state again.

• Keep device time automatic — Correct time prevents authenticator code mismatch and certificate errors.
• Update router firmware quarterly — One update can clear odd connection drops that show up only in games.
• Limit password retries — If it fails twice, reset once and stop spam attempts.
• Use a password manager — It cuts typos and makes resets clean.
• Sign out on shared PCs — It prevents saved login confusion when multiple accounts use one machine.

If battle net not logging in returns after you’ve cleared cache, tested a different network, and confirmed the account works again on the web, it’s time to gather details and contact Blizzard’s customer service team through the help portal. Bring your error code, OS version, and a quick note on what you tried so the agent can skip the basics.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback