Fix “You Don’t Look Connected to the Internet” Microsoft Account Sign-In (2026)

Chrome loads the news fine. Teams, OneDrive, Copilot, and the Microsoft Store insist you are offline or show You don’t look connected to the internet when signing into a Microsoft account. That mismatch is the tell: the network works; MSA authentication does not.

This guide reflects the widely reported March 2026 consumer Microsoft account sign-in break on Windows 11 (24H2/25H2) and the cleanup steps that still help afterward. Related: 25H2 problems, Windows Update stuck, Teams join, flush DNS, WiFi disconnects.

Confirm the pattern

Works	Fails	Likely
Chrome/Firefox websites	MSA sign-in, Store, OneDrive	Token / KB issue
Nothing loads	Same	Real network — fix WiFi first
Work Entra apps OK, personal MSA fails	Personal MSA bug class	Patch + re-auth personal account
Only on VPN	VPN/proxy	Disconnect; reset WinHTTP

1. Install the fix updates first

1. Settings → Windows Update → Check for updates
2. Install updates that include KB5085516 or any later cumulative that superseded it through 2026
3. If Update is stuck, use the Update stuck reset before blaming the account
4. Restart while connected to the internet

Avoid staying on the early March 2026 packages known to break MSA sign-in. Optional: Microsoft Update Catalog for the KB if Windows Update will not offer it.

2. Restart hygiene

After patching:

1. Sign out of Windows once (or full Restart)
2. Sign in online — not airplane mode
3. Open account.microsoft.com in Edge to force a fresh web auth
4. Relaunch OneDrive / Teams / Copilot

Disable Fast Startup if you keep booting into a stale half-state (Control Panel power options).

3. Sign out of Microsoft apps and Windows account glue

• OneDrive tray → Settings → Account → Unlink this PC (know your files are cloud-safe) → sign in again
• Teams → profile → Sign out → sign in
• Edge → Profile → sign out of Microsoft account → sign in
• Settings → Accounts → Email & accounts — remove stale Microsoft entries you can safely re-add
• Access work or school — do not remove corporate Entra joins without IT

If Copilot is optional for you, you can also hide it: disable Copilot/Recall — that does not replace installing the KB.

4. Reset WinHTTP proxy and clear VPN leftovers

Elevated Command Prompt:

netsh winhttp show proxy
netsh winhttp reset proxy
ipconfig /flushdns

Quit consumer VPNs completely (VPN guide). Broken kill switches can make Microsoft endpoints look offline.

Credential Manager: remove obsolete MicrosoftAccount / Office tokens that refuse to refresh, then sign in again.

5. Date, time, and TLS basics

Settings → Time & language → Date & time → Set time automatically On.

Wrong time breaks token validation and looks identical to “offline.”

6. Repair Office and Store

• Apps → Microsoft 365 → Modify → Quick Repair
• wsreset.exe for Store
• Optional: reputable account/network repair tool (affiliate card) if tokens still will not stick after KBs — official vendor only

Outlook send issues after auth glitches: Outlook not sending.

7. Network stack if still broken

netsh winsock reset
netsh int ip reset

Reboot. Rejoin WiFi. If the radio itself flaps, fix WiFi disconnects first.

DISM/SFC if corruption is broader:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

8. Workarounds that are not cures

Workaround	Notes
Local account	Sidesteps MSA apps; loses convenience
Web versions of Outlook/Teams	Good temporary access
Another user profile	Tests profile corruption
Skipping the KB	Will keep biting you

Secure the account itself with 2FA once you can sign in — phishing spikes when people panic-click “fix account” emails (phishing guide).

Checklist

1. Latest cumulative (≥ KB5085516 lineage)
2. Online restart
3. Re-auth OneDrive/Teams/Edge
4. netsh winhttp reset proxy + DNS flush
5. VPN off test
6. Office/Store repair
7. Winsock/IP reset only if needed

When Chrome works and Microsoft apps do not, think tokens and KBs, not “buy a new router.” Patch, re-auth, clear proxy leftovers — then your Microsoft stack remembers the internet exists.

Extra diagnostics when the KB is already installed

If winver shows a build that should include the March 21, 2026 fix (or later cumulatives) and Microsoft apps still lie about connectivity, dig into local identity state:

1. Settings → Accounts → Email & accounts — remove stale personal Microsoft entries you can re-add
2. Sign out of Edge’s Microsoft profile completely, restart Edge, sign in again from a bookmarked URL
3. OneDrive → Pause syncing → Quit OneDrive → relaunch from the Start menu
4. Check whether a third-party firewall is filtering login.live.com / login.microsoftonline.com

Distinguish real offline from fake offline

Open a Command Prompt and run ping login.live.com and ping www.google.com. If both reply but Store/Teams fail, you are in token/proxy territory. If neither replies, fix WiFi or DNS first (WiFi disconnects, flush DNS). Captive portal WiFi (hotels) often lets Chrome through a portal page while MSA HTTPS auth fails — complete the portal, then retry Microsoft apps.

Security hygiene after repeated failed prompts

Repeated failed Microsoft sign-ins are a favourite moment for phishing emails that say “unusual activity.” Change nothing from those messages. Open account.microsoft.com/security from a bookmark, review recent activity, and confirm 2FA is on. If you already typed a password into a fake page, rotate it and scan for malware (malware removal).

Store, Xbox, and Copilot after tokens recover

When sign-in works again, open Microsoft Store and install pending app updates, then verify Xbox app / Game Pass sign-in if you use them. Copilot and OneDrive should stop showing offline badges after a clean restart online. If only one app remains broken, repair or reset that app under Settings → Apps rather than repeating the whole KB dance. Keep Windows Update healthy so the next cumulative does not reintroduce an old package.