January 11, 2022—KB5009557 (OS Build 17763.2452)

Symptom

Workaround

After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."

1. Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10.

2. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10.

Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows:

1. Go to the Settings app > Recovery.

2. Select Get Started under the Reset this PC recovery option.

3. Select Keep my Files.

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

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 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.

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.

This issue is resolved in KB5010791.

After installing this update on domain controllers (DCs), affected versions of Windows Servers might restart unexpectedly after receiving an Lsass.exe error.

Note: On Windows Server 2016 and later, you are more likely to be affected when DCs are using Shadow Principals in Enhanced Security Admin Environment (ESAE) or environments with Privileged Identity Management (PIM).

This issue is resolved in KB5010791.

After installing the November 22, 2021 or later updates, recent emails might not appear in search results in the Microsoft Outlook desktop app. This issue is related to emails that have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as accounts hosted on Microsoft Exchange and Microsoft 365. If the default search in the Microsoft Outlook app is set to server search, the issue will only affect the advanced search.

This issue is resolved in KB5010351.

Alternate resolution if you have not installed updates dated February 8, 2022 or later

This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, you can resolve this by installing and configuring a special Group Policy (preferred).

Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy: Windows 10, version 1809, Windows 10 Enterprise LTSC 2019, and Windows Server 2019

After installing updates released January 11, 2022 or later, apps that use the Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might have issues. The apps might fail or close or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error.

Note for developers Affected apps use the System.DirectoryServices API.

To resolve this issue manually, apply the out-of-band updates for the version of the .NET Framework used by the app.

Note These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. 

For instructions on how to install this update for your operating system, see the KB articles listed below:

• Windows Server 2022: 

  • .NET Framework 4.8 KB5011258

• Windows Server 2019: 

  • .NET Framework 4.8 KB5011257

  • .NET Framework 4.7.2 KB5011259

• Windows Server 2016: 

  • .NET Framework 4.8 KB5011264

  • .NET Framework 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011329

• Windows Server 2012 R2: 

  • .NET Framework 4.8 KB5011266

  • .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011263

  • .NET Framework 4.5.2 KB5011261

• Windows Server 2012:

  • .NET Framework 4.8 KB5011265

  • .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 or 4.7.2 KB5011262

  • .NET Framework 4.5.2 KB5011260

After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start.

Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected.

Note No third-party backup or recovery apps are currently known to be affected by this issue

This issue is addressed in KB5014022.

Windows server computers might log Event ID 40 in the System event log each time a Group Policy is updated or refreshed on a server or client. The error is found with the Description, ”The event logging service encountered an error when attempting to apply one or more policy settings.” This issue occurs after installing Windows updates released on or after January 11, 2022.

The gpupdate and Group Policy Object (GPO) refresh tasks will trigger this error when they run (default run times for these tasks is every 90-120 minutes on member servers or 5 minutes on domain controllers).

This issue occurs specifically after you configure any setting under Computer Configuration > Windows Components > Event Log Service > Security. Settings under Computer Configuration > Policies > WindowsSettings > Security Settings > Event Log do not trigger this error and can be used.

IMPORTANT The errors described in this issue do not prevent Security log changes from being applied.

This issue is addressed in KB5014022.