In the wake of the National Security Agency’s recent alert regarding a “high-risk of compromise” for Microsoft Exchange server users, and the ongoing exploitation of the CVE-2025-9491 Windows vulnerability, Microsoft has confirmed yet another issue affecting its user base. This time, the focus is on Windows 11 and Windows Server users who are experiencing persistent prompts for authentication credentials, alongside failures of valid credentials and complications with remote desktop connections.
Microsoft Confirms Some Users Might Experience Authentication Failures After Windows 11 And Server Updates
Microsoft’s commitment to enhancing security for its Windows operating systems is evident in its latest updates, which aim to bolster protections against malicious applications and unauthorized access. However, these updates can sometimes lead to unintended issues, as is the case with the recent confirmation from Microsoft regarding authentication failures linked to updates released on or after August 29.
According to a Microsoft Support posting, identified as KB5070568, users may encounter Kerberos and New Technology LAN Manager (NTLM) authentication failures due to duplicate Security IDs (SIDs) present on their devices. This problem predominantly affects users of Windows 11, version 24H2, Windows 11, version 25H2, and Windows Server 2025 following the aforementioned update.
The root of the issue lies in the newly implemented security protections that enforce checks on SIDs. Microsoft clarified that these measures are essential for maintaining the integrity of user accounts and preventing unauthorized access. Duplicate SIDs often arise from unsupported cloning or duplication of a Windows installation without utilizing the Sysprep tool, which is designed to ensure SID uniqueness. With the latest update, this uniqueness has become a mandatory requirement for the affected Windows versions.
Microsoft emphasized that the design change effectively blocks authentication handshakes between devices that possess duplicate SIDs. To resolve this issue, users will need to rebuild their devices using supported methods for cloning or duplicating a Windows installation, ensuring that each device is assigned a unique SID.
