Impacted Products:

Please note the following information regarding the security updates:

Known Issues:

KB5009557: Applies to: Windows 10 Enterprise 2019 LTSC Windows 10 IoT Enterprise 2019 LTSC Windows 10 IoT Core 2019 LTSC

https://support.microsoft.com/en-au/topic/january-11-2022-kb5009557-os-build-17763-2452-c3ee4073-1e7f-488b-86c9-d050672437ae

Improvements and fixes

This security update includes quality improvements. Key changes include:

This update contains miscellaneous security improvements to internal OS functionality. No additional issues were documented for this release.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

KB5009546: Applies to: Windows 10, version 1607, all editions Windows Server 2016, all editions

https://support.microsoft.com/en-us/topic/january-11-2022-kb5009546-os-build-14393-4886-0c2cac57-13b6-42e6-b318-41ca32428f91

Symptom

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.

After installing this update, IP Security (IPSEC) connections that contain a Vendor ID might fail. VPN connections using Layer 2 Tunneling Protocol (L2TP) or IP security Internet Key Exchange (IPSEC IKE) might also be affected.

Workaround

We are working on a resolution and will provide an update in an upcoming release.

To mitigate the issue for some VPNs, you can disable Vendor ID within the server-side settings.

Note Not all VPN servers have the option to disable Vendor ID from being used.

We are presently investigating and will provide an update in an upcoming release.

We are presently investigating and will provide an update in an upcoming release.

KB5009624: Applies to: Windows Server 2012 Windows Embedded 8 Standard

https://support.microsoft.com/en-us/topic/january-11-2022-kb5009624-monthly-rollup-23f4910b-6bdd-475c-bb4d-c0e961aff0bc

Windows 8.1 and Windows Server 2012 R2 have reached the end of mainstream support and are now in extended support. Starting in July 2020, there will no longer be optional, non-security releases (known as “C” releases) for this operating system. Operating systems in extended support have only cumulative monthly security updates (known as the “B” or Update Tuesday release).

For information about the various types of Windows updates, such as critical, security, driver, service packs, and so on, please see the following article. To view other notes and messages, see the Windows 8.1 and Windows Server 2012 R2

Improvements and fixes

This security update includes improvements and fixes that were a part of update KB5007260 (released previous November 9, 2021) and addresses the following issue:

Update to support the cancellation of daylight savings time (DST) for 2021 for the Republic of Fiji.

Addresses a known issue that causes error codes 0x000006e4, 0x0000007c, or 0x00000709 when connecting to a remote printer that is shared on a Windows print server.

Addresses a known issue that might prevent apps, such as Kaspersky apps, from opening after you attempt to repair or update the apps using the Microsoft Installer (MSI).

After installing this update on domain controllers (DCs), affected versions of Windows Server might restart unexpectedly.

Symptom

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

After installing this update on a device by using Unified Extensible Firmware Interface (UEFI), virtual machines (VMs) in Hyper-V might not start.

Workaround

Do one of the following:

Perform the operation from a process that has administrator privilege.

Perform the operation from a node that doesn’t have CSV ownership.

Microsoft is working on a resolution and will provide an update in an upcoming release.

We are currently investigating and will provide an update in an upcoming release.

KB5009586: Applies to: Windows 8.1 Windows Server 2012 R2 Windows Embedded 8.1 Industry Enterprise Windows Embedded 8.1 Industry Pro

https://support.microsoft.com/en-us/topic/january-11-2022-kb5009586-monthly-rollup-9541f57c-89b0-48d6-ade2-31609678ce9b

Improvements and fixes

This security update includes improvements and fixes that were a part of update KB5009586 (released previous December 14, 2021) and addresses the following issue:

Addresses a Windows Server issue in which Active Directory attributes are not written correctly during a Lightweight Directory Access Protocol (LDAP) modify operation with multiple specific attribute changes.

Symptom

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Workaround

Do one of the following:

Perform the operation from a process that has administrator privilege.

Perform the operation from a node that doesn’t have CSV ownership.

Microsoft is working on a resolution and will provide an update in an upcoming release.