These problems can also have an impact on the software that rely on these two features for authentication, including, but without limiting themselves, the single authentication solutions (SSO) third -party, identity management systems and chip card authentication products. This is now a real problem with this bug for many companies. According to Microsoft, these problems are linked to safety mitigation measures designed to mitigate a vulnerability known as CVE-2025-26647, which allows authenticated attackers to raise their privileges remotely by exploiting a vulnerability of entry validation in Windows Kerberos. Kerberos has replaced NTLM as a new default authentication protocol for peripherals attached to a field in all Windows versions from Windows 2000. To get around this problem, the persons concerned are advised to modify the value of the register of “2” to “1” as described in an assistance document.
-
-
Microsoft has now declared in the status dashboard of the Windows version that April updates for Windows Server (KB50555523) cause generalized problems with Windows Server authentication. The list of platforms concerned includes Windows Server 2016, Windows Server 2019, Windows Server 2022 and the latest version, Windows Server 2025. “This can”, explains the medium, “cause authentication problems in Windows Hello Entreprise Kindows Confidence (WHFB) or the environments that have implemented (also known as Machine Pkinit). Microsoft is aware of this problem and confirms that he is working on a solution and will provide an update as soon as possible. However, as the company explained, it is unlikely that home users will be affected by this problem, as domain controllers are generally used for authentication in businesses and organizations. End users who encounter connection problems using Windows Hello are affected by a different bug that has similar effects.
--