Microsoft confirms authorization issues after patch day updates

Windows users are reporting increasing problems with apps and services after the latest patch day updates. Microsoft has now confirmed an authorization issue and is collecting reports to determine the cause. That reports that Neowin online magazine Specifically, concerns the latest Patch Day updates for Windows 10 and Windows 11. Microsoft is currently collecting reports that after the updates of Windows 10 and 11 PCs, authorization with the NPS, RRAS, EAP, and PEAP protocols is no longer possible used to be.

The problem is related to the way the domain controller handles the assignment of certificates to computer accounts. However, this confirmed bug does not affect client Windows devices and non-domain Windows servers.

Systems that are affected

This is said to be a common problem so the group is investigating the cause but has not yet had an update that fixes it. According to current knowledge, all versions of Windows 10 and Windows 11, including the server variants and the long-term service channel, are affected.

So it seems once again that the last cumulative update for Windows 11 and 10 didn’t go as smoothly as Microsoft wanted. In addition to these authorization issues, there have already been reports of increased app crashes (we reported). Microsoft has further corrected the error in the Windows Health Dashboard for Windows 10 and 11 with a new note and promised an update. There is:

Windows Health Dashboard

After installing updates released on May 10, 2022, on your domain controllers, you may experience authentication errors on the server or client for services such as Network Policy Server (NPS), Routing and Remote Access Service (RRAS), Radius, Extensible Authentication Protocol ( EAP) and Protected Extensible Authentication Protocol (PEAP). A problem has been found in the way the domain controller handles the assignment of certificates to computer accounts.

• Note: Installing updates released on May 10, 2022, on client Windows devices and Windows servers without a domain controller will not cause this issue. This issue only affects the installation of May 10, 2022 updates that are installed on servers used as domain controllers.
• Workaround: The preferred solution to this issue is to manually associate certificates with a computer account in Active Directory. See Certificate Assignment for instructions.
• Next steps: We are currently investigating and will provide an update in a future release.
• Affected platforms:
• Customer: Windows 11, version 21H2; Windows 10 version 21H2; Windows 10 version 21H1; Windows 10 version 20H2; Windows 10 version 1909; Windows 10 version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
• Server: Windows Server 2022; Windows Server, version 20H2; Windows Server version 1909; Windows Server version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Microsoft is investigating the issue and is working to fix it in future releases. In the meantime, IT administrators can work around the issue by manually mapping certificates to a computer account in Active Directory. The necessary instructions are available in the certificate assignment documentation.