This topic captures known issues that affect language provisioning in Windows 10.
Adding Local Experience Packs (LXPs) in Windows 10 version 2004 and later versions: Known issue
When servicing a Windows image that contains LXPs with a cumulative monthly security update or public preview, the corresponding LXP ISO for that update needs to be downloaded and installed to the system image prior to launching OOBE. If this step is skipped, then the user may experience unexpected language fallback (e.g., see text in a language that they cannot understand) until they are able to update their LXP via the Microsoft Store. Note that LXPs cannot be updated via the Microsoft Store until OOBE is completed (i.e., device has reached the Desktop) and the device has established internet connectivity.
To find the correct LXP ISO for your associated monthly quality update, look for the abbreviation of your update in the LXP ISO filename (e.g., 9B). If a quality update doesn’t have a corresponding LXP ISO, use the LXP ISO from the previous release.
Monthly quality update
Servicing update file name and KB article
LXP ISO part numbers and/or filenames
*9B
2020-09 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4571756)
Windows 10, version 2004 or 20H2 3C Local Experience Packs (LXPs) (released Apr 2021)
*The number aligns to the month (e.g., 9 = September), and the letter aligns to the quality update type. See this blog post for more information on the monthly update terminology and servicing cadence.
Adding language packs in Windows 10, version 1803 and later versions: Known issue
In Windows 10, version 1803 (build 17134) and later versions, you use Lpksetup.exe or Deployment Image Servicing and Management (DISM.exe) to add language packs to an image. However, the language does not automatically appear in the list of Windows display languages under Settings > Time & Language > Language.
Cause
Beginning in Windows 10, version 1803, a background cleanup task removes language packs that are not actively used. The list of Windows display languages shows only the languages of the language packs that have been used. It is possible for the cleanup task to remove a language pack before the language pack can be used.
Resolution
The specific steps to resolve this issue depend on the version of Windows 10 that you are using.
Windows 10, version 1903(build 18362) and later
After you install the language pack, change the Group Policy that governs the affected computer. To do this, set the BlockCleanupOfUnusedPreinstalledLangPacks Group Policy Object (GPO) to Yes.
After you make this change, the added language remains visible under Settings > Time & Language > Language > Windows display language.
Windows 10, versions 1803 and 1809
When you run the commands that are described in this section, you must use the security context of the user who will use the language pack. If more than one user will be using the system, you have to run these commands under the security context of each user in turn.
After you install the language pack, add the language pack to the user language list. To do this, open a Windows PowerShell window, and run the following commands:
In these commands, represents the language code of the language pack that you want to add.
To verify that the language pack was added to the user language list, run the Get-WinUserLanguageList cmdlet.
Example
This example adds the Spanish language pack (“es-es») to the list of Windows display languages. To add other language packs, replace all instances of “es-es” with the language code of the desired language pack.
Install a language pack by using Lpksetup.exe or DISM.exe. To do this, open an elevated Command Prompt window, and run one of the following commands:
Verify that the language pack is installed. To do this, type the following command at an elevated command prompt:
Depending on the version of Windows 10, do one of the following:
Windows 10, version 1903(build 18362) and later: Change the Group Policy that governs the affected computer. Set the BlockCleanupOfUnusedPreinstalledLangPacks Group Policy Object (GPO) to Yes.
Windows 10, versions 1803 and 1809: Open a PowerShell window and run the following commands:
To verify that the language is now available, do one of the following:
In a PowerShell window, run Get-WinUserLanguageList.
Select Settings >Time & Language >Language >Windows display language, and verify that EspaГ±ol (EspaГ±a) appears.
—>
Available languages for Windows
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.
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 add a Windows Server 2019 language pack to Windows Server 2016.
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 Packs
Language/region
Language/region tag
Language/region ID
Language/region decimal ID
Arabic (Saudi Arabia)
ar-SA
0x0401
1025
Bulgarian (Bulgaria)
bg-BG
0x0402
1026
Chinese (Hong Kong SAR)
zh-HK
Note:В No longer used. See zh-TW.
0x0c04
3076
Chinese (PRC)
zh-CN
0x0804
2052
Chinese (Taiwan)
zh-TW
0x0404
1028
Croatian (Croatia)
hr-HR
0x041a
1050
Czech (Czech Republic)
cs-CZ
0x0405
1029
Danish (Denmark)
da-DK
0x0406
1030
Dutch (Netherlands)
nl-NL
0x0413
1043
English (United States)
en-US
0x0409
1033
English (United Kingdom)
en-GB
0x0809
2057
Estonian (Estonia)
et-EE
0x0425
1061
Finnish (Finland)
fi-FI
0x040b
1035
French (Canada)
fr-CA
0x0c0c
3084
French (France)
fr-FR
0x040c
1036
German (Germany)
de-DE
0x0407
1031
Greek (Greece)
el-GR
0x0408
1032
Hebrew (Israel)
he-IL
0x040d
1037
Hungarian (Hungary)
hu-HU
0x040e
1038
Italian (Italy)
it-IT
0x0410
1040
Japanese (Japan)
ja-JP
0x0411
1041
Korean (Korea)
ko-KR
0x0412
1042
Latvian (Latvia)
lv-LV
0x0426
1062
Lithuanian (Lithuania)
lt-LT
0x0427
1063
Norwegian, BokmГҐl (Norway)
nb-NO
0x0414
1044
Polish (Poland)
pl-PL
0x0415
1045
Portuguese (Brazil)
pt-BR
0x0416
1046
Portuguese (Portugal)
pt-PT
0x0816
2070
Romanian (Romania)
ro-RO
0x0418
1048
Russian (Russia)
ru-RU
0x0419
1049
Serbian (Latin, Serbia)
sr-Latn-CS
Note: No longer used. See sr-Latn-RS.
0x081a
2074
Serbian (Latin, Serbia)
sr-Latn-RS
0x241A
9242
Slovak (Slovakia)
sk-SK
0x041b
1051
Slovenian (Slovenia)
sl-SI
0x0424
1060
Spanish (Mexico)
es-MX
0x080a
2058
Spanish (Spain)
es-ES
0x0c0a
3082
Swedish (Sweden)
sv-SE
0x041d
1053
Thai (Thailand)
th-TH
0x041e
1054
Turkish (Turkey)
tr-TR
0x041f
1055
Ukrainian (Ukraine)
uk-UA
0x0422
1058
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.
Установка
Официальные прямые ссылки на языковые пакеты для Windows 7 и Windows 7 SP1.
По указанным ниже ссылкам Вы сможете скачать языковые пакеты для Windows 7 и языковые пакеты для Windows 7 с установленным сервисным Пакетом обновлений 1 (SP1) напрямую с сайта Microsoft.
Чтобы скачать необходимый Вам языковой пакет нажмите на прямую ссылку напротив выбранного Вами языка. Также Вы можете самостоятельно вручную сделать полную ссылку. Для этого добавьте к имени файла языкового пакета (независимо от разрядности) указанному в колонке Прямая ссылка место расположения файла:
http://download.windowsupdate.com/msdownload/update/software/updt/2009/08/ Например, если имя файла языкового пакета латышского языка для 64-битной версии Windows 7: windows6.1-kb972813-x64-lv-lv_70c1f8bda213f20aea07e46a6c9ed976f0d151ce.exe , то ссылка будет:
Для Windows 7 SP1:
http://download.windowsupdate.com/msdownload/update/software/updt/2011/02/ Например, если имя файла языкового пакета латышского языка для 32-битной версии Windows 7 SP1: windows6.1-kb2483139-x86-lv-lv_97b58149699a2e8b02bd7cac720ac0795b51c98b.exe , то ссылка будет:
Официальные языковые пакеты (language packs) для 32-bit (x86) Windows 7
