Windows 10 1809 Language Pack Issue, Microsoft recommends Reset of PC

[harlan4096]

The three most recent cumulative updates for Windows 10 version 1809, KB4495667, KB4501835 and KB4493509 were not exactly bug free. Windows 10 version 1809 is affected by several issues currently, and Microsoft just added a new issue to the list.

The issue originated in KB4493509 according to the known issues listing on the official support page. The update was released on April 9, 2019 as part of April's Patch Tuesday. It appears that Microsoft did not resolve the issue in the two updates that followed for Windows 10 version 1809 so that KB4495667 and KB4501835 are affected as well.

The issue affects systems with "some" Asian language packs installed.

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

Microsoft notes that systems affected by the issue "may" receive the error "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND". Pretty vague, especially since Microsoft did not even provide a list of language packs with that issue.

Microsoft lists two mitigation options:

1.- Uninstall and reinstall the language pack that were recently added to the system.
2.- Check for Updates to install the "April 2019 Cumulative Update".

The second suggestion is puzzling. Considering that updates are cumulative and that April or May updates are already installed on the system, it is unclear why Windows Update would push an earlier update to the system (again).

Microsoft suggests, under the second option, that users should reset their PC if reinstalling the language pack does not resolve the issue.

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.

It is unclear why Microsoft does not suggest to uninstall the affected updates to resolve the issue. Could it be that the issue persists when that is tried?

Microsoft notes that it is working on a resolution for the issue and that it will include it in future updates.

Continue Reading