Microsoft acknowledged the Kerberos authentication issues that emerged with its November updates. The software giant accepted the released updates caused more problems than they actually solved.
According to Microsoft the latest path released on Tuesday has a Direct Access connectivity issue in multiple versions of Windows (which it solved by rolling back the update). Now, the company has issued a warning that this month’s updates are causing problems with Kerberos authentication as well.
The latest bug affects virtually every version of Windows, it leads to issues like sign-in problems, failed Remote Desktop connections, and printing not working. The software giant is yet to provide a solution for these issues.
Microsoft has acknowledged that Kerberos authentication issues are caused by a new update
Recently Microsoft posted an emergency update related to Windows domain controllers. After installing this update, any Kerberos authentication in your environment may experience problems.
The software giant has published the numerous issues in Windows Release Health, that users may have to experience.
- Domain user sign in might fail. This also might affect Active Directory Federation Services (AD FS) authentication.
- Group Managed Service Accounts (gMSA) used for services such as Internet Information Services (IIS Web Server) might fail to authenticate.
- Remote Desktop connections using domain users might fail to connect.
- You might be unable to access shared folders on workstations and file shares on servers.
- Printing that requires domain user authentication might fail.
According to Microsoft if you encounter this issue, your computer might show a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error in the System section of Event Log on the Domain Controller. You’ll see an event with ID 14 and the text “The missing key has an ID of 1.”
In November 2022, Microsoft is expected to fix the problem with Netlogon and Kerberos. For now, you need to follow the guidance in these articles to stay safe from this issue. This issue doesn’t affect consumer devices or mobile devices where there are no onsite Active Directory servers.
If you’re using a Windows device at home that’s not connected to a corporate network and have no connection to an on-premises Active Directory, then you are not affected by this vulnerability. However, those with a device on a network with an Azure Active Directory Connect server are.
Windows 11- Why Should you Clean Up After Installing the New Windows Update
Microsoft releases KB5019311 update for Windows 11
NVIDIA Releases Fixes for Poor Gaming Performance in Windows 11 2022 Update