Windows 10 1809 Language Pack Issue, Microsoft recommends Reset of PC
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:
- Uninstall and reinstall the language pack that were recently added to the system.
- 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:
- Go to the Settings app > Recovery.
- Select Get Started under the Reset this PC recovery option.
- 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.
Closing Words
The documentation leaves lot to be desired: it does not list language packs that are known to cause the issue, does not reveal how the error manifests itself, and makes a suggestion -- to check for updates to install an earlier cumulative update -- that makes little sense.
I'd try the language pack deinstallation and installation first, then the removal of updates affected by this. Depending on how serious the issue is, you might consider resetting the PC as a last resort unless you have a backup that you can restore.
If you have not installed the latest cumulative updates yet and have Asian language packs installed, you may want to wait with the installation just a bit longer (until the issue is resolved).
As far as Windows 10 version 1809 is concerned, could this become the buggiest version of Windows ever?
Microsoft has never figured out how to do updates and never will. End of story.
Linux does relatively small updates quietly in the background on your schedule and only kernel updates require a reboot (at your convenience, not when you’re trying to get work done.)
@Richard Steven Hack: “only kernel updates require a reboot”
And you can even reduce the need for that reboot to nearly “never” if you’re able and willing to do some system configuration beyond what your distro does.
Also, if I haven’t had GTX 1660Ti, i7 9700, 16GB DDR4 RAM and 4 Samsung 860, I might have stayed on Windows 7, too. No, there not a chance.
I can’t be more serious. Each 6 months, gives the feature upgrade. The other 6 months focus on bug fixing only. One feature upgrade per year and one bug fixing. Wouldn’t be great my idea?
If you are using Windows 10, stay build 1803 and DISABLE all windows update and prevent any update until build 20xx release.
To put this problem in perspective, Windows 7-10 supports about 107 language packs per https://support.microsoft.com/en-us/help/14236/language-packs . I imagine that is a complicated thing to manage.
Doesn’t reset annihilate any non-MS competitor programs installed such as unedge browsers? Can’t remember how much each one of MS’s standard fixes wrecks your system.
1803 still works fine but I’ve always installed updates from the catalog manually and only security updates. Windows update stays disabled.
Recommend upgrading to Pro, it’s definitely worth the cost, which isn’t much, to get group policy editor. Most of the garbage Home users put up with can be disabled.
Tried getting Server or LTSB for similar benefits but not legally available in my locale.
@ ULBoom
Since it is practically insane for anyone to run Win 10 Home, Pro or Ent, what with M$’s forced auto-updates/upgrades and forced Telemetry & Data collection, I think it is justified for everyone to force himself/herself to get Win 10 Ent LTSC through “unofficial” means, by hook or by CROOK.
Personally, I got Win 10 Ent LTSC 2016 installed in a virtual machine on my Win 7 laptop.
best solution to win 10 is to remove it and install win7 with NO updates. Works great.
I had win 8, total sh!t. Removed it and put win7 on my laptop with NO updates. That was several years ago. works good.
I’m still on Win7 x64 Pro, and viewing the smorgasborg of problems Win10 brings along, I vow to never “downgrade” to Win10…
I got suspicious of Windows at, I believe it was, Win 2000 when what I called the Dr. Seuss interface was introduced. A friend tried to dis me by claiming it was just like a Mac. I laughed “I’m not 6; can I run NASTRAN on a Mac?” Dweeb.
Been up and down and accelerating since then, XP was OK; Vista was not OK; Seven was OK; Eight was not OK, then OK(8.1); Ten was not OK, then OK, now not OK. And so on…
If software works, it needs more features.
The incompetence at Microsoft is amazing…..
Why don’t they get the quality testers back – those they fired a few years ago ?
I would never accept any reset, re-install or similar if i used Windows 10 Retarded Edition.
Can’t be windows ‘updates’ without some sort of f**kery from ms. It’s actually amazing how they manage to be consistently bad at this.
Microsoft is mismanaged and tries to do too much in too many markets. It can’t keep up with the update schedule because of how interdependent MS products and services are on each other. A bug in one thing breaks another thing, then the dev teams blame each other. On top of that MS management keeps changing plans because of failures like Windows mobile, Cortana, and Edge. They worked on Edge for years and now had to dump the whole thing and try to retrofit Google’s code with their MS bloatware.
Some day in the near future Microsoft will reccomend installing a different os, one that works.
I just did a fresh installation of 1809 LTSC x64, used the second release ISO. Installed NET 4,8, installed the latest SSU and then the latest update pack, the one ending in 667. The original ISO is the EN_US version, and I have added the Russian and Ukrainian languages. Everything seems to work fine here:
imgur.com/nsfMlFU
I did the updates manually though. I installed the language packs from Settings, after doing the updates.