Windows 11 Patch KB5079473 Broke 8 Apps Sign-In — Microsoft Emergency Fix KB5085516 Won’t Auto-Download

GigaNectar Team

Windows 11 Hero Bloom logo against a dark blue gradient background, the official identity mark of Microsoft's Windows 11 operating system
Windows 11 Emergency Update KB5085516 – Microsoft Account Sign-In Fix
Windows 11 · Security Update · March 2026

On March 10, 2026, Microsoft’s routine Patch Tuesday update KB5079473 rolled out automatically to Windows 11 devices on versions 24H2 and 25H2. The update patched 79 security vulnerabilities — including two publicly disclosed zero-days — and brought Emoji 16.0 support and a Bing-powered taskbar speed test shortcut. It also unintentionally broke Microsoft account sign-ins across a wide range of apps.

Users began reporting a persistent “You’ll need the Internet for this. It doesn’t look like you’re connected to the Internet” error inside Teams, OneDrive, Edge, Excel, Word, PowerPoint, and Copilot — even on devices with a fully working internet connection. The apps still opened, but any feature requiring a Microsoft account sign-in — cloud sync, templates, fonts, communications — stopped working.

Microsoft officially confirmed the issue on March 20 via its Windows Release Health dashboard and released an emergency out-of-band fix — KB5085516 — on March 21, 2026. The update is available now but does not install automatically unless the “Get latest updates as soon as they’re available” toggle is on in Windows Update settings.

Emergency Out-of-Band Update
By the numbers

A Routine Security Patch That Broke Sign-Ins

Key facts about the bug and its fix, verified against Microsoft’s official KB5085516 support page.

📅
Mar 10
Date KB5079473 installed automatically as Patch Tuesday
🔒
79
Security vulnerabilities patched, including 2 publicly disclosed zero-days
💥
8+
Microsoft apps disrupted by the sign-in bug
11
Days between the problematic patch and the emergency fix
~12
Minutes to fully download and apply KB5085516
Windows 11 laptop screen showing sign-in error related to KB5079473 Microsoft account connectivity bug
Windows 11 · KB5079473 introduced a network connectivity state that broke Microsoft account sign-in — fixed in KB5085516
Affected apps

Which Apps Were Hit — and Which Were Not?

The bug affects any app using a personal Microsoft account for sign-in. Apps still open, but online features, cloud sync, and anything needing account authentication fail with the false “no internet” error.

💬 Teams Free Sign-in broken
📁 OneDrive Sync blocked
📧 Outlook Reported affected
🌐 Edge Account blocked
📊 Excel Cloud blocked
📝 Word Templates broken
🎞 PowerPoint Fonts blocked
🤖 Copilot Sign-in blocked
🏢 Entra ID Not affected
✅ Business accounts are safe. Microsoft confirmed that apps using Microsoft Entra ID (formerly Azure Active Directory) for authentication are not affected. The bug is limited to personal Microsoft account sign-ins only.
What happened & when

Eleven Days From Bug to Fix

The full sequence of events from the March 2026 Patch Tuesday rollout to the emergency KB5085516 release, as documented by Microsoft.

March 10, 2026

KB5079473 rolls out automatically

Microsoft’s March 2026 Patch Tuesday update installs on Windows 11 24H2 and 25H2 devices. It patches 79 vulnerabilities including two publicly disclosed zero-days — CVE-2026-21262 in SQL Server and CVE-2026-26127 in .NET — and adds Emoji 16.0, improved File Explorer search reliability, and a Bing-based taskbar speed test shortcut. The security update installs automatically on most consumer devices.

March 10 onward

Sign-in failures spread across Microsoft apps

Users encounter a persistent error — “You’ll need the Internet for this. It doesn’t look like you’re connected to the Internet” — even on devices with a working connection. The update places the device in a specific network connectivity state that blocks Microsoft account authentication. Changing DNS, using a VPN, or reinstalling apps does not help, as the bug affects the Windows installation itself.

March 20, 2026 — Friday

Microsoft officially acknowledges the bug

Microsoft documents the issue on its Windows Release Health dashboard and issues a temporary workaround: restart the affected device while connected to the internet. Microsoft warns the device may return to the broken state if restarted offline. Entra ID sign-ins are confirmed unaffected.

March 21, 2026

Emergency update KB5085516 released

Microsoft releases a cumulative out-of-band fix for Windows 11 25H2 and 24H2. OS builds advance to 26200.8039 (25H2) and 26100.8039 (24H2). Available via Windows Update under Optional Updates and the Microsoft Update Catalog. Devices with “Get the latest updates as soon as they’re available” enabled receive it automatically; others must install manually.

Windows Update settings screen where KB5085516 can be found and installed under Optional Updates
Go to Settings → Windows Update → Optional Updates to find and install KB5085516
Find your action step

Do You Need to Install KB5085516?

Not every Windows 11 user is affected. Answer two quick questions to find out whether you need to act — and get your exact next steps if you do.

🔍 Quick Status Checker
Two questions. A personalised answer based on what Microsoft has officially confirmed about KB5085516.
Step 1 of 2 — Are you running Windows 11 version 24H2 or 25H2?
Step-by-step fix

How to Install the Fix Manually

Stay connected to the internet throughout. Restarting offline can return the device to the broken state. The full process takes approximately 12 minutes.

⚠️ Critical: Microsoft confirmed that restarting without an active internet connection after installation may revert the device to the broken connectivity state. Always restart while connected.
1
Open Settings from the Start menu — or press Win + I
2
Click Windows Update in the left sidebar
3
Click Check for updates, then click Advanced options → Optional updates
4
Find KB5085516 in the list and click Download & install
5
Allow ~5 minutes to download and 5–7 minutes to apply
6
Restart your device while staying connected to the internet
Enterprise administrators: Use the expedited update workflows in Microsoft Intune or Windows Autopatch. The standalone installer is also available on the Microsoft Update Catalog — search KB5085516.
Wider context

The Third Emergency Patch in March 2026

KB5085516 is not March’s only out-of-band update. Two earlier emergency patches preceded it for Windows 11 Enterprise environments.

KB5084597 · March 13

RRAS Security Hotpatch

Fixed three critical remote code execution vulnerabilities — CVE-2026-25172, CVE-2026-25173, CVE-2026-26111 — in the Routing and Remote Access Service (RRAS). Targeted at hotpatch-enabled Windows 11 Enterprise and LTSC 2024 devices only. Standard consumer devices were already covered by the March Patch Tuesday.

KB5084897

Bluetooth Connectivity Fix

Addressed Bluetooth device visibility issues on hotpatch-enabled Windows 11 Enterprise LTSC 2024 devices only. This fix does not apply to standard consumer Windows 11 installs.

Samsung Laptop Issue

C:\ Drive Access Failure

Microsoft published separate guidance for Windows 11 users on select Samsung laptops unable to access their C:\ drive. The cause was a faulty version of the Samsung Galaxy Connect (Samsung Continuity Service) app — unrelated to KB5079473 or the sign-in bug.

What Was Covered

The update KB5085516 was discussed as Microsoft’s out-of-band response to a sign-in failure introduced by the March 2026 Patch Tuesday release KB5079473. The bug was documented as affecting personal Microsoft account authentication across Teams Free, OneDrive, Edge, Excel, Word, PowerPoint, and Copilot on Windows 11 versions 24H2 and 25H2.

The fix was covered as an optional update released on March 21, 2026 — eleven days after the problematic patch. It was noted as available via Windows Update’s Optional Updates section and the Microsoft Update Catalog. Entra ID-based business sign-ins were confirmed as unaffected throughout.

The March 2026 Patch Tuesday cycle, the sign-in disruption, the temporary workaround, and the KB5085516 emergency fix were covered as documented in Microsoft’s official Windows Release Health dashboard.

Leave a comment