KB5085516

Microsoft has released an out-of-band cumulative update KB5085516 for Windows 11 25H2 (2025 Update), which fixes a critical issue with signing into apps using a Microsoft account, including Teams, Edge, OneDrive, and Copilot. This cumulative package (build 26200.8039) is intended for Windows 11 25H2 (Windows 11 2025 Update) on x64 (amd64) and ARM64 processors and resolves bugs discovered after installing the previous update KB5079473 from March 10, 2026.

• Fixed Microsoft account sign-in. Resolved an issue where after installing updates from March 10, 2026 and later, some users could not sign into apps with a Microsoft account. Even with an active internet connection, an error appeared saying: no internet connection, which blocked access to Microsoft services, including Microsoft Teams (free version) and OneDrive. The issue only affected sign-in using Microsoft accounts — organizations using Microsoft Entra ID for authentication were not affected by this bug.

No known issues are reported for the current KB5085516 release at the time of publication, but Microsoft recommends carefully monitoring the system after installation, as the update is out-of-band and addresses the consequences of the previous patch.

Update KB5085516 is distributed via Windows Update for devices with Windows 11 that already have update KB5079473 installed. If you installed previous updates, only the new updates contained in this package will be downloaded and installed.

For automatic installation via Windows Update, go to Settings > Windows Update and click Check for updates. The package is also available for manual download from the Microsoft Update Catalog for users who prefer offline installation.

Fix for Microsoft account sign-in: The update fixes a bug in the Update Agent Orchestrator that incorrectly handled network connectivity status after previous patches. The system falsely reported no internet access for MSA certificate validation via HTTPS to login.live.com, while the physical network stack worked. The fix restores correct calls to Network List Manager and WinHTTP.

No impact on Microsoft Entra ID: The bug did not affect organizations using Microsoft Entra ID (formerly Azure AD), because their authentication relies on Web Account Manager (WAM) with a separate network status cache and priority checks via DSREG Join. The issue only appeared with classic sign-in using a personal Microsoft account (Consumer MSA), where internet presence was checked via the legacy InternetGetConnectedState call.

The last 10 Windows updates: