Shulou(Shulou.com)11/24 Report--

CTOnews.com Nov 14, Microsoft has confirmed several new Bug in Windows Health Dashboard. For example, login failures and other issues related to Kerberos authentication.

CTOnews.com has learned that this issue affects almost all current versions of Windows 11, Windows 10, Windows8.1, and Windows 7:

Clients: Windows 11 22H 2; Windows 10 22H 2; Windows 11, version 21H 2; Windows 10, version 21H 2; Windows 10, version 21H 1; Windows 10, version 20H 2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1

Server: Windows Server 2022; Windows Server 20119; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

It is reported that users who have installed updates on or after November 8, 2022 on Windows with the domain controller role may encounter problems using Kerberos authentication. This issue may affect any Kerberos authentication operations in the server environment. Microsoft said that some of the scenarios / operations that may be affected include:

Domain user login may fail. This may also affect Active Directory Federation Services (AD FS) authentication.

The Group Management Service account (gMSA) used for services such as Internet Information Services (IIS Web Server) may not be able to authenticate.

Remote Desktop connections using domain users may fail.

You may not be able to access shared folders on your workstation and shared files on your server.

Printing that requires domain user authentication may fail.

Microsoft says you can check to see if it is affected by opening the event log on the domain controller. Devices affected by this Bug will display a Microsoft-Windows-Kerberos-Key-Distribution-Center event ID 14 error and prompt:

When processing an AS request for the target service, the account

There is no appropriate key to generate the Kerberos ticket (the ID of the missing key is 1). Available account types: 23 18 17. Change or reset

Will generate the correct key.

In addition, the text "ID of lost key is 1" is displayed next to the affected event. It is worth noting that this Bug does not appear on home devices that do not belong to the local region.

Microsoft says it is working to fix it and may prepare a patch in the coming weeks.

In addition, Win11 and Win10 also have a network connection problem. After installing KB5019509 or later system updates, if you connect to a network without a network or switch Wi-Fi network hotspots, you may not be able to reconnect to Direct Access.

Of course, home devices or organizational devices that do not use Direct Access to remotely access the organization's network resources are not affected. The affected platforms include:

Clients: Windows 11, version 22H 2; Windows 10, version 22H 2; Windows 11, version 21H 2; Windows 10, version 21H 2; Windows 10, version 21H 1; Windows 10, version 20H 2; Windows 10 Enterprise LTSC 2019

Server: Windows Server 2022; Windows Server 2019

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.