[German]Microsoft has already released a hotfix update on March 23, 2026, for users of Windows 11 Enterprise LTSC 2024. This update is intended to resolve sign-in issues with Microsoft accounts caused by update KB5079473 from March 10, 2026. It is likely the hotfix counterpart to the out-of-band update KB5085516.
A Look Back at the Sign-In Issue
After installing Windows Update KB5079473 for Windows 11 24H2-25H2, released on March 10, 2026, there were reports that signing in to Microsoft accounts in some Microsoft applications (Excel, Word, OneDrive, Teams Free, etc.) might fail.
I addressed this issue here on the German blog post Anmeldung in Microsoft Teams Free und anderen Apps scheitert (19.3.2026) on March 19, 2026, following a reader's tip, citing Microsoft's confirmation (seeMicrosoft account sign ins might fail for Microsoft Teams Free and other apps).
Fix via Windows 11 Out-of-Band Update KB5085518
The out-of-band update KB5085516 for Windows 11 24H2-25H2 was released as early as March 21, 2026, and is intended to resolve the login issue described above. I reported on this in the blog postWindows 11: Out-of-band update KB5085516 fixes login issues.
Now I read here that Microsoft released the hotfix update KB5085518 for Windows 11 Enterprise LTSC 2024 on March 23, 2025. The support article states:
Microsoft account sign in] Fixed: After you install the Windows update released on or after March 10, 2026, some users might experience an issue signing in to apps with a Microsoft account. Even when the device has a working Internet connection, a "no Internet" error appears during sign in and prevents access to Microsoft services and apps such as Microsoft Teams Free and OneDrive.
However, this is the exact same information as in the out-of-band update KB5085516 for Windows 11 24H2–25H2. The hotfix update for Windows 11 Enterprise LTSC 2024 is now being released. The hotfix takes effect immediately after installation without requiring a reboot. Microsoft notes that the issue described above affects only Microsoft accounts (not Microsoft Entra IDs). The sign-in issue should therefore be resolved on the LTSC platform.
