KB5005625

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 KB5005568, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005568 are unaffected and print operations to that printer will succeed as usual.

Note IPP is not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

This issue is resolved in KB5006744.

After installing KB5005102, Windows Server 2019 virtual machines (VMs) employing Software Defined Networks (SDN) or traditional multi-tenant RRAS gateways may lose connectivity with external networks using Gateway connections. Installing the August preview or later update will not affect Windows Server 2019 hosts, Network Controller VMs, and Software Load Balancer VMs.

This issue is resolved in KB5006672.

After installing KB5005568 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only.

This issue results from an improper building of the data file which contains the printer properties. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. Clients who have previously received the settings package prior to the installation of KB5005625 are unaffected. Servers which use default print settings and have no custom settings to provide to clients are unaffected.

Note The printer connection methods described in this issue are not commonly used by devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

This issue is resolved in KB5006672.

After installing this update, you might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.

Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations.

This issue is resolved in KB5006672.

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.