Windows update issues: Login to private Microsoft accounts fails
Microsoft attributes a recently known disruption of apps and services with private accounts to the Windows updates from the March patchday.
(Image: heise online / dmk)
The Windows updates from Microsoft's March Patchday have unwanted side effects. Logging into private Microsoft accounts fails in some cases after installation.
Microsoft now explains this in the Windows Release Health notes. According to this, logging into Microsoft Teams Free or OneDrive, for example, no longer works after installing the Windows updates for Windows 11 25H2 and 24H2. The error messages are essentially: “You'll need the Internet for this. It doesn't look like you're connected to the Internet” (the English error message explains: “You'll need the Internet for this. It doesn't look like you're connected to the Internet”). This also happens even if the device is connected to the internet.
The problem occurs particularly when using Microsoft accounts, which are often used for Teams Free. Other affected apps include Microsoft Edge, Excel, Word, or Microsoft 365 Copilot. If a function in the apps requires logging into the Microsoft account, this error message may occur. Microsoft emphasizes that Entra ID accounts are not impacted by the issue. This means that at least large companies are generally spared.
Reboot does good
As a temporary countermeasure, Microsoft suggests restarting the computer when the issue occurs, keeping the internet connection active. This should repair the device's connection status and prevent the issue from occurring. If the device is restarted without an active internet connection, the device may fall into a connection status where the issue reoccurs.
Microsoft states that it is working on a solution to the issue. It is expected to be available in the next few days.
Videos by heise
Disruption in Microsoft's Cloud Status
The disruptions have also been displayed in Microsoft's Cloud Status since Thursday of this week.
Microsoft initially explained there that it was exclusively an issue in Teams Free, with the affected Windows versions also including Windows 11 23H2 and Windows 10 22H2. Furthermore, the issue is a regression as a result of a recent Windows update. According to the cloud status, Microsoft aims for a solution on March 24, 2026, after previously experimenting with configuration changes to mitigate the impact.
(dmk)
