The following tables show the supported language packs for Windows 10 and Windows Server, and supported language interface packs (LIPs) for Windows 10. LIPs are available for Windows 10, but are not available for Windows Server. For more information, see Language packs.
Windows 10 and Windows Server: Full language packs are not interchangeable, but some LIPs are. For example, you can add Windows 10, version 1809 LIPs to Windows Server 2019.
The version of the language, LIP, or Feature on Demand must match the version number. For example, you can neither add a Windows 10 version 1809 LIP to Windows 10 version 1803 image, nor to Windows Server 2012.
You cannot add languages to Windows 10 Home Single Language and Windows 10 Home Country Specific editions.
To learn how to add languages to Windows, or where to get them, see Where to get language packs and LIPs.
For a complete list of supported languages and locales, see Locale Identifier Constants and Strings.
Supported Language Packs and Language Interface Packs
The following tables include these settings:
- Language/region— The name of the language that will be displayed in the UI. All 38 language packs are available for Windows 10 and Windows Server 2016. In Windows Server 2012 the user interface (UI) is localized only for the 18 languages listed in bold.
- Language/region tag— The language identifier based on the language tagging conventions of RFC 3066. This setting is used with the Deployment Image Servicing and Management (DISM) tool, or in an unattended answer file.
- Language/region ID— The hexadecimal representation of the language identifier. This setting is used with the keyboard identifier when specifying an input method using DISM.
- Language/region decimal identifier— The decimal representation of the language identifier. This setting is used in Oobe.xml.
|Language/region||Language/region tag||Language/region ID||Language/region decimal ID|
|Arabic (Saudi Arabia)||ar-SA||0x0401||1025|
|Chinese (Hong Kong SAR)||zh-HK|
Note:В No longer used. See zh-TW.
Note: No longer used. See sr-Latn-RS.
Language interface packs (LIPs)
Except where noted, the following LIPs are available for Windows 10. For Windows Server, options to change keyboard and regional settings such as currency, time zones, and time/date format are available but LIPs are not available. For more information, see Language packs.
As of Windows 10, version 1809, LIPs are are distributed as .appx files. To learn how to add an .appx, see Add languages to Windows.
Версия программы: 10.0.17763.1 Version 1809 x86-x64
Официальный сайт: devicepartner.microsoft.com/en-US
Язык интерфейса: Русский, Английский, и другие
Лечение: не требуется
Windows 10 10.0.17763.1 Version 1809
Набор языковых пакетов для Windows 10 10.0.17763.1 Version 1809 для интеграции с помощью утилиты DISM (ADK).
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.
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?