[Windows Update一覧]

KB5008602

詳細情報

KB番号	KB5008602 Out-of-band
リリース日	2021/11/14
Windowsバージョン	Windows 10 1809
ビルド番号	17763.2305
URL	https://support.microsoft.com/en-us/help/5008602
ダウンロード	Microsoft Update Catalog

ハイライト

Updates a known issue that might cause authentication failures on domain controllers that run Windows Server after you install the November 9, 2021 security updates.

改良点

Addresses a known issue that might cause authentication failures related to Kerberos tickets you acquired from Service for User to Self (S4U2self). This update also addresses failures of the S4U2Proxy with Protocol Transition option that occur because the authenticating service cannot obtain an evidence ticket. This issue occurs after you install the November 9, 2021 security updates on domain controllers (DC) that are running Windows Server.

既知の不具合

Symptom	Workaround
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."	This issue is addressed by updates released June 11, 2019 and later. We recommend you install the latest security updates for your device. Customers installing Windows Server 2019 using media should install the latest Servicing Stack Update (SSU) before installing the language pack or other optional components. If using the Volume Licensing Service Center (VLSC), acquire the latest Windows Server 2019 media available. The proper order of installation is as follows: Install the latest prerequisite SSU, currently KB5005112 Install optional components or language packs Install latest cumulative update Note Updating your device will prevent this issue, but will have no effect on devices already affected by this issue. If this issue is present in your device, you will need to use the workaround steps to repair it. Workaround: Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Click Check for Updates and install the April 2019 Cumulative Update or later. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, use the In-Place-Upgrade feature. For guidance, see How to do an in-place upgrade on Windows, and Perform an in-place upgrade of Windows Server.
After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found.	This issue occurs because of an update to the PnP class drivers used by this service. After about 20 minutes, you should be able to restart your device and not encounter this issue. For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.
After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.	This issue is resolved in KB5007266.
After installing this update, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted.	This issue is resolved in KB5007266.
After installing this or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. Note This issue does not affect Microsoft Defender for Endpoint on Windows 10.	This issue is resolved in KB5008218.
After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices that are attempting to activate and are affected by this issue might receive the error, "Error: 0xC004F074. The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information." Event Log entries related to activation are another way to tell that you might be affected by this issue. Open Event Viewer on the client device that failed activation and go to Windows Logs > Application. If you see only event ID 12288 without a corresponding event ID 12289, this means one of the following: The KMS client could not reach the KMS host. The KMS host did not respond. The client did not receive the response. For more information on these event IDs, see Useful KMS client events - Event ID 12288 and Event ID 12289.	This issue is resolved in KB5009616.