The security update KB5079473 from March 10, 2026, was supposed to close vulnerabilities, but it left a critical functional gap in numerous Windows 11 environments (versions 24H2 and 25H2). Users are confronted with a "No Internet" error message as soon as they try to log in to Microsoft services such as Teams (Free), OneDrive, or Outlook, even though the network connection is physically flawless.
Since this error massively restricts productivity, Microsoft responded on March 21, 2026, with the Out-of-Band (OOB) update KB5085516.
The cause lies in a faulty logic within the network status query, which was corrupted by the March Patchday update. Windows falsely signals an offline status to the applications, whereby the authentication process for Microsoft accounts (MSA) is immediately aborted.
Interestingly, enterprise environments that rely purely on Microsoft Entra ID are not affected by this specific bug. The problem is isolated to the classic MSA login, which often comes into play in hybrid scenarios or when using free versions of Teams.
Troubleshooting Strategy
First, you should check whether your clients have already installed the faulty update KB5079473. If this is the case and users report login problems, a manual trigger of the OOB patch is required.
Navigate in the Windows settings directly to the update area. As soon as KB5085516 is offered to you as an optional quality update, confirm the process via "Download and install".
This process initiates a targeted replacement of the corrupted system files, whereby the miscommunication between the Network List Manager and the authentication apps is corrected. At the same time, the Servicing Stack Update (SSU) KB5083532 is installed, which secures the structural integrity of future update processes.
In managed environments with Microsoft Intune, you fall back on the "Expedited Updates" function to massively accelerate the distribution. To do this, you create a new policy for quality updates and set the target release to March 21, 2026.
Through this configuration, the usual deferred settings (postponements) are ignored, whereby the patch is enforced immediately after the client's next check-in. This is the most efficient way to make a large workforce operational again without individual interventions.
Installation via PowerShell
If you access an affected device via remote maintenance, you can initiate the installation via the shell.
Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber
Install-Module -Name PSWindowsUpdate
Install-WindowsUpdate -KBArticleID KB5085516 -AcceptAll -AutoRebootConclusion
The appearance of KB5085516 illustrates the complexity of the interlocking of OS core components and cloud identity services. When basic network indicators (NCSI) are incorrectly influenced, the authentication chain for modern apps collapses. From an administrative point of view, this OOB update is to be classified as critical as soon as MSA accounts are used.
In terms of security, you are not taking a risk, as it contains all the fixes of the regular March update. Uninstalling KB5079473 as a workaround is expressly not recommended, as this would also remove security repairs. The correct path is the forward-correction through KB5085516. After the rollout, monitor the telemetry data in Endpoint Manager to ensure that the success rate of log-ins reaches the normal level again.
Sei der Erste und starte die Diskussion mit einem hilfreichen Beitrag.
Kommentar hinterlassen
Dein Beitrag wird vor der Veröffentlichung kurz geprüft — fachlich, respektvoll und auf den Punkt ist hier genau richtig.