Battlenet Not Logging In | Fast Fixes That Work

Battlenet not logging in is usually caused by a password or code mismatch, a stuck launcher cache, or a temporary server-side sign-in issue.

If you’re stuck on a spinner, kicked back to the login screen, or seeing an update agent loop, it feels like the app is broken. Most of the time it isn’t. Battle.net sign-in is a chain: your typed details, a short-lived session token, a few background services, and a clean network route to Blizzard’s login servers. One weak link can stop the whole chain.

This article helps you find the weak link without wasting an hour on random fixes. Start with quick checks that take minutes. Then move to targeted resets that clear bad tokens and cached web views. Only touch reinstall steps after you’ve ruled out account entry and outages.

What Login Failures Usually Mean

Credential mismatch — The email, password, or authenticator code doesn’t match what the account system expects.
Session stuck — The launcher keeps an old token or cached sign-in page and fails even with correct details.
Connection blocked — DNS, VPN, proxy, firewall rules, or security apps interrupt the sign-in handshake.
Service disruption — A regional outage or maintenance stops sign-ins for many players at once.

Do a fast split test. If you can sign in on the Battle.net website but not in the launcher, treat it as a device or launcher state problem. If you can’t sign in anywhere, start with account recovery and service status.

Fast Checks That Save The Most Time

These checks fix a big chunk of cases and they’re low risk. They also prevent you from clearing files when the real issue is a typo or an outage.

Check For A Wider Sign-In Issue

Look for signs that this is happening to lots of people. If friends can’t sign in, or outage trackers show a spike in sign-in reports, wait a bit and retry. Third-party monitors like StatusGator and Netzwelt often show this pattern quickly when Blizzard services are under strain.

Type Your Email And Password Manually

Saved fields can paste a hidden space, a previous email, or an old password. Click into both boxes and type them by hand. If you use an authenticator, enter the newest code and don’t reuse a code that just rolled over. Blizzard notes authenticator codes refresh on a short timer, so timing matters.

Try Website Login First

Sign in on the account site. If the website login works, your account is likely fine and the launcher needs a clean session. If the website login fails, jump to the account section below and use Blizzard’s “Can’t log in?” recovery flow.

Power-Cycle Your Router And Device

Short network glitches can break sign-in handshakes. Shut down your PC or Mac. Power off your modem and router. Wait a full minute, then power up the modem/router first and your device second. This clears stale routes and can end a login loop without changing settings.

What You See	Likely Cause	First Try
Endless “Logging In” spinner	Bad session token or cache	Exit app, clear cache, relaunch
Password keeps failing	Email mismatch or reset delay	Type email, reset on web, retry
Update agent stuck	Agent blocked or can’t write files	Run as admin, allow in firewall
Works on hotspot only	DNS or ISP route issue	Swap DNS, flush cache, retest

Battlenet Not Logging In On Windows And Mac

This section clears the launcher’s stored state. You won’t lose games. You’re removing cached web views, tokens, and background agent leftovers that can trap the app in a bad loop.

Fully Quit The Launcher

Quit Battle.net — Exit from the tray (Windows) or menu bar/dock (Mac), not just the window close button.
End background tasks — On Windows, use Task Manager to end Battle.net and Blizzard Update Agent tasks.

Clear Launcher Cache On Windows

Corrupted cache can keep the app stuck on an old sign-in page. Clearing it forces a clean refresh on the next launch.

Close the launcher — Confirm Battle.net and the update agent are not running.
Open ProgramData — Press Windows + R, type %ProgramData%, and press Enter.
Delete cache folders — Remove the Battle.net and Blizzard Entertainment folders found there.
Restart and sign in — Launch Battle.net and enter your details again.

Run Battle.net As Administrator

Permission conflicts can block the agent or stop the launcher from writing fresh session files. Blizzard’s agent error guidance calls out permissions and file conflicts as common causes.

Run as administrator — Right-click the Battle.net shortcut and choose Run as administrator.
Try a clean restart — Reboot the PC, open Battle.net first, then sign in before opening other apps.

Allow The Launcher In Firewall And Security Apps

Security tools can interrupt sign-in traffic. Add Battle.net and Blizzard Update Agent as allowed apps in Windows Firewall and any third-party security suite. If you see sign-in succeed right after allowing the app, keep the rule and move on.

Network Fixes For Login Loops

When Battle.net works on one network and fails on another, your account is fine. The route is the problem. A DNS tweak and a clean network cache solve a lot of these cases.

Switch DNS To A Public Resolver

Set Google DNS — Use 8.8.8.8 and 8.8.4.4, then reboot your router or device.
Set Cloudflare DNS — Use 1.1.1.1 and 1.0.0.1, then retry launcher sign-in.

Flush DNS And Reset Network Stack On Windows

Open Command Prompt as admin — Search cmd, right-click, then choose Run as administrator.
Flush DNS cache — Run ipconfig /flushdns, then close the window.
Reset Winsock — Run netsh winsock reset, then restart the PC.

Disable VPN, Proxy, And Traffic Filters

Turn off VPN — Quit your VPN app fully, then try signing in again.
Disable proxy — In Windows proxy settings, set manual proxy to off.
Pause filter tools — Temporarily disable packet filters or ad-blocking VPN features that hook into network drivers.

If you suspect your ISP route is acting up, do a quick hotspot test. Connect your PC to a phone hotspot and try the launcher for two minutes. If sign-in works there, keep working on DNS and router settings at home instead of reinstalling the app. Next, check whether your router has a “security” feature that blocks game services, like DNS filtering, parental controls, or a built-in VPN. Turn that feature off for a test, then retry the launcher. If you’re on a shared network, test a direct Ethernet cable, since flaky Wi-Fi can drop the short login handshake even when browsing feels fine.

Mac Fixes For Keychain And Permissions

On macOS, the launcher can get stuck because saved credentials, cached web views, or permissions don’t line up after an update. These steps keep your games intact while clearing the pieces most likely to break sign-in.

Remove Old Saved Login Entries

Open Keychain Access — Use Spotlight search and launch Keychain Access.
Search for Blizzard — Look for saved items tied to Battle.net or Blizzard.
Delete only the relevant items — Remove entries that match the launcher, then restart the Mac.

Clear Cached Web Views

Quit Battle.net — Make sure the launcher is closed and not running in the background.
Open the Library folder — In Finder, use Go while holding Option, then choose Library.
Remove Battle.net cache — Delete Battle.net-related cache folders inside Caches, then relaunch.

Check macOS Firewall And Network Filters

Review firewall rules — In System Settings, ensure Battle.net is allowed for incoming connections.
Disable content filters — Turn off network filter profiles or security VPN features, then test sign-in.

Account Steps When You Can’t Sign In Anywhere

If battlenet not logging in happens on the website and in the launcher, treat it as an account entry or security gate issue. This is where you reset access cleanly, then test on the web before going back to the app.

Reset Password And Retest

Use Blizzard’s official password reset flow. Then wait a few minutes before you try again, since session tokens can lag behind a brand-new password. Blizzard’s login articles also mention auto-fill can keep inserting the wrong email, so type it yourself during testing.

Start password recovery — Use the “Can’t log in?” page and choose Forgot password.
Type the email manually — Don’t trust saved fields until sign-in works again.
Test on the web first — Confirm the new password works on the account site before using the launcher.

Fix Authenticator Code Rejection

Authenticator codes refresh on a tight timer. If your phone time is off, the code can be rejected. Sync your device clock, then enter a fresh code right after it updates.

Set automatic time — Turn on automatic Date & Time on the phone.
Use the newest code — Wait for the code to refresh, then enter it right away.
Recover access if needed — Use the account recovery option to remove the authenticator only if you no longer have the device.

Check For Email Mix-Ups And Account Locks

If you changed your Battle.net email recently, make sure you’re using the new one. Blizzard notes that typing the wrong email is a common reason people can’t log in after a reset. Also scan your inbox for security notices that ask you to verify ownership before signing in again.

Repair Or Reinstall Without Losing Your Games

If you’ve cleared cache, tested DNS, and verified the account works on the web, a repair or clean reinstall can fix rare launcher corruption. Blizzard’s agent guidance lists reinstalling the Battle.net app as a fix when the launcher itself is damaged.

Repair Game Files When Only One Game Fails

Open game options — Select the game in Battle.net, open Options, then choose Scan and Repair.
Finish the scan — Let it complete, then try launching again.

Reinstall The Launcher Cleanly

Uninstall Battle.net — Remove the app from Windows Apps or drag it to Trash on macOS.
Delete leftover folders — On Windows, remove remaining Battle.net folders in ProgramData. On Mac, remove Battle.net folders in your user Library caches.
Install the newest version — Download the installer from Blizzard’s official Battle.net download page and install fresh.

Need official pages? Use Blizzard’s Can’t Log In recovery page for password, email, or authenticator resets. The login troubleshooting articles also list agent error steps and safe reinstall notes. Keep those pages open while testing so you can reverse changes fast if a step doesn’t apply today.

If you still can’t sign in after a clean install, test on a second device or a second network. If the failure follows the account across devices and networks, use the account recovery page and Blizzard’s login help articles to escalate through the official help portal.