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.

Microsoft Windows 10 Language Pack + Lip 10.0.10240 RTM WZT (x86-x64) (2015) [Multi/Rus] скачать торрент бесплатно

Версия программы: 10240 RTM
Официальный сайт: Microsoft
Язык интерфейса: Русский, Английский и другие (LangPack39 + Lip72)

Лечение: не требуется

Системные требования:OS: Windows 10 Home/Pro/Education/Enterprise (build 10240)
HDD: до 500 МБ свободного места (для каждого языкового пакета)

Описание:
Официальные языковые пакеты для Windows 10 RTM (build 10240).
В данном архиве вы найдете такие языковые пакеты и Lip»ы:
Arabic, Belarusian, Bulgarian, Chinese-Hong Kong SAR, Chinese-Simplified, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese-Brazil, Portuguese-Portugal, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Tatar, Thai, Turkish, Ukrainian и многие другие.

Как установить язык:
Способ №1:
Запустите командную строку (cmd) от имени Администратора и выполните lpksetup, появится окно

жмём далее и указать расположение языка

Ждём далее, и ждём завершение

Способ №2
На диске C: создаем папку langpacks в которую бросаем lp.cab из скачанного архива.
Запускаем cmd от администратора
Пишем это:

dism /online /add-package /packagepath:C:\langpacks\lp.cab

Запуск cmd от админа:

— левый нижний угол —> ПКМ (Command Promt (Admin))
— Win+Q —> cmd —> ПКМ (Run as administrator)
— Win—> ПКМ —> All Apps—> ПКМ на cmd (Run as administrator)

Контрольные суммы:
FILE: 10240.16384.150709-1700.TH1_CLIENTLANGPACKDVD1_OEMRET_X86FRE_MULTI.ISO
CRC: 5612A042
MD5: 890ACE8D7D2B8E455A19EE6498748F3C
SHA-1: 0C406F723B21E54E9F1C0EED137114E6D722BF11
FILE: 10240.16384.150709-1700.TH1_CLIENTLANGPACKDVD1_OEM_X64FRE_MULTI.ISO
CRC: AFFDA5FB
MD5: 2F7374CF389B0862D2E0147E3F036A33
SHA-1: 8FFC07D8C6069746C8222DD6F65BAD2F779F735C
FILE: 10240.16384.150709-1700.TH1_CLIENT_LIP_DVD_X86FRE_MULTI.ISO
CRC: 3E66232C
MD5: D4B95310515741EE3225327321E1E358
SHA-1: 957537B9BD42179CC8CFB2597F52561A98466B17
FILE: 10240.16384.150709-1700.TH1_CLIENT_LIP_DVD_X64FRE_MULTI.ISO
CRC: 3A6FEB34
MD5: 14A8FA68718F285CB0DB9F7D5E7F57F3
SHA-1: 73065C579251A722BC8FECF8BE9E91B2FD910757

NOTE:
MICROSOFT.WINDOWS.10.LANGUAGE.PACK.RTM.X86.OEMRET.DVD-WZT
RELEASE DATE: 15/07/09
BUILD: 10240.16384.150709-1700
FILE: 10240.16384.150709-1700.TH1_CLIENTLANGPACKDVD1_OEMRET_X86FRE_MULTI.ISO
SIZE: 963,231,744 byte
SHA-1: 0C406F723B21E54E9F1C0EED137114E6D722BF11
MD5: 890ACE8D7D2B8E455A19EE6498748F3C
CRC: 5612A042
NOTE: this is an original M$ image shared with the partenrs
Client Language Pack»s need to be licensed to be installed and run on a Windows 10 system. Since a complete language pack is required to display the system’s UI, all editions of Windows 10 are licensed to have one complete language pack running. Select editions are also licensed to allow more than one language pack on the system at a time. These editions are known as multilingual editions.
A multilingual edition enables users to change the UI language on a per-user basis. Since the UI language is associated with the user profile, multiple users that share the same system can use it in different languages.
by WZT
15|07|22

MICROSOFT.WINDOWS.10.LANGUAGE.PACK.RTM.X64.OEM.DVD-WZT
RELEASE DATE: 15/07/09
BUILD: 10240.16384.150709-1700
FILE: 10240.16384.150709-1700.TH1_CLIENTLANGPACKDVD1_OEM_X64FRE_MULTI.ISO
SIZE: 1,370,247,168 byte
SHA-1: 8FFC07D8C6069746C8222DD6F65BAD2F779F735C
MD5: 2F7374CF389B0862D2E0147E3F036A33
CRC: AFFDA5FB
NOTE: this is an original M$ image shared with the partenrs
Client Language Pack»s need to be licensed to be installed and run on a Windows 10 system. Since a complete language pack is required to display the system’s UI, all editions of Windows 10 are licensed to have one complete language pack running. Select editions are also licensed to allow more than one language pack on the system at a time. These editions are known as multilingual editions.
A multilingual edition enables users to change the UI language on a per-user basis. Since the UI language is associated with the user profile, multiple users that share the same system can use it in different languages.
by WZT
15|07|22

MICROSOFT.WINDOWS.10.LIP.RTM.10240.X86.DVD-WZT
RELEASE DATE: 15/07/09
BUILD: 10240.16384.150709-1700
FILE: 10240.16384.150709-1700.TH1_CLIENT_LIP_DVD_X86FRE_MULTI.ISO
SIZE: 274,071,552 byte
SHA-1: 957537B9BD42179CC8CFB2597F52561A98466B17
MD5: D4B95310515741EE3225327321E1E358
CRC: 3E66232C
NOTE: this is an original M$ image shared with the partenrs
Windows Language Interface Pack (LIP) Frequently Asked Questions:
https://msdn.microsoft.com/en-us/goglobal/bb688177.aspx
by WZT
15|07|22

MICROSOFT.WINDOWS.10.LIP.RTM.10240.X64.DVD-WZT
RELEASE DATE: 15/07/09
BUILD: 10240.16384.150709-1700
FILE: 10240.16384.150709-1700.TH1_CLIENT_LIP_DVD_X64FRE_MULTI.ISO
SIZE: 393,885,696 byte
SHA-1: 73065C579251A722BC8FECF8BE9E91B2FD910757
MD5: 14A8FA68718F285CB0DB9F7D5E7F57F3
CRC: 3A6FEB34
NOTE: this is an original M$ image shared with the partenrs
Windows Language Interface Pack (LIP) Frequently Asked Questions:
https://msdn.microsoft.com/en-us/goglobal/bb688177.aspx
by WZT
15|07|22

microsoft-windows-10-language-pack-lip-10.0.10240-rtm-wzt-x86-x64-2015-multirus.torrent
На этой странице вы сможете скачать Microsoft Windows 10 Language Pack + Lip 10.0.10240 RTM WZT (x86-x64) (2015) [Multi/Rus] последняя версия, без регистрации

Microsoft Windows 10 Language Pack + Lip 10.0.10240 RTM WZT (x86-x64) (2015) [Multi/Rus] скачать торрент

Год выпуска: 2015 ОС: Windows Категория: Windows 10 Требования: OS: Windows 10 Home/Pro/Education/Enterprise (build 10240)
HDD: до 500 МБ свободного места (для каждого языкового пакета) Язык интерфейса: Русский, Английский и другие (LangPack39 + Lip72) Лекарство: не требуется Рейтинг на сайте:

Описание:
Официальные языковые пакеты для Windows 10 RTM (build 10240).
В данном архиве вы найдете такие языковые пакеты и Lip»ы:
Arabic, Belarusian, Bulgarian, Chinese-Hong Kong SAR, Chinese-Simplified, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese-Brazil, Portuguese-Portugal, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Tatar, Thai, Turkish, Ukrainian и многие другие.

Как установить язык:
Способ №1:
Запустите командную строку (cmd) от имени Администратора и выполните lpksetup, появится окно

жмём далее и указать расположение языка

Ждём далее, и ждём завершение

Способ №2
На диске C: создаем папку langpacks в которую бросаем lp.cab из скачанного архива.
Запускаем cmd от администратора
Пишем это:

dism /online /add-package /packagepath:C:\langpacks\lp.cab

Запуск cmd от админа:

— левый нижний угол —> ПКМ (Command Promt (Admin))
— Win+Q —> cmd —> ПКМ (Run as administrator)
— Win—> ПКМ —> All Apps—> ПКМ на cmd (Run as administrator)

Add languages to Windows images

To add a language to your personal PC, go to Settings > Time & Language > Language, and choose a language to install. Learn more.

You can add languages and regional support to Windows 10 (except for Windows 10 Home Single Language and Windows 10 Home Country Specific editions), and Windows Server.

Windows installations start with at least one language pack and its language components. You can add:

• Language packs: Localization packages for Windows, delivered as a .cab file, for example, Microsoft-Windows-Client-Language-Pack_x64_es-es.cab. Includes UI elements like text for dialog boxes, menu items, and help files.
• Language Interface Packs (LIPs): Partially-localized language pack. Requires a base language pack. In Windows 10, version 1809, LIPs are delivered as Local Experience Packs (LXPs) .appx files, for example, LanguageExperiencePack.am-et.neutral.appx. For previous versions of Windows 10, LIPs are delivered as .cab files, for example, C:\Languages\es-ES\lp.cab.
• Language features: Language features include language basics (like spell checking), fonts, optical character recognition, handwriting, text-to-speech, and speech recognition. You can save disk space by choosing not to include some language components in your image. While this reduction in image size can be helpful when creating images for devices with limited storage, it does lead to an incomplete language experience. Delivered as .cab files, for example, Microsoft-Windows-LanguageFeatures-Basic-fr-fr-Package.cab.
• Recovery languages: UI text for the Windows Recovery Environment (WinRE). Delivered as .cab files. Example: lp.cab, WinPE-Rejuv_fr-fr.cab, and more.

Get language resources: Language Pack ISO and Feature on Demand ISO

OEMs and System Builders with Microsoft Software License Terms can download the Language Pack ISO and Feature on Demand ISO from the Microsoft OEM site or the Device Partner Center.

• For Windows 10, version 1809, LIP .appx files and their associated license files are in the LocalExperiencePack folder on the Language Pack ISO.
• For previous versions of Windows, Language Interface Packs are available as a separate download.
• WinRE language packs are distributed on the Language Pack ISO. Don’t use the WinPE language packs that ship with the ADK.

IT Professionals can download language packs from the Microsoft Next Generation Volume Licensing Site.

After Windows is installed, users can download and install more languages by selecting Settings > Time & language > Language > Add a language.

• Language components must match the version of Windows. For example, you can’t add a WindowsВ 10, version 1809 language pack to Windows 10, version 1803.
• Windows Server: Full language packs are not interchangeable with Windows 10.

Considerations

Install languages, then updates and apps. If you’re adding languages to an image that already contains apps or updates (for example, servicing stack updates (SSU) or cumulative updates (CU), reinstall the apps and updates.

After you install a language pack, you have to reinstall the latest cumulative update (LCU). If you do not reinstall the LCU, you may encounter errors. If the LCU is already installed, Windows Update does not offer it again. You have to manually install the LCU.

Care is required when installing languages to an image that includes FODs with satellite packages. When FODs have satellite packages, the localized text for the feature may be carried in a satellite package rather than the language pack or primary FOD package. Specific steps must be followed when adding languages to an image that includes these FODs.

• Starting with Windows 10, version 2004, the default Windows 10 image includes several FODs with language resources in satellite packages. Before adding languages, you must first build a custom FOD and language repository to ensure that the appropriate satellite packages are pulled in when the language is added.
• For versions of Windows 10 earlier than 2004, this is typically only a concern when you have added a FOD with satellite packages. A best practice here is to add languages first, then FODs.

Size and performance

• You can install multiple languages and components onto the same Windows image. Having too many affects disk space, and can affect performance, especially while updating and servicing Windows.
• LXP-backed language packs are smaller than their Lp.cab-backed counterparts.
• When creating Windows images, you can remove English language components when deploying to non-English regions to save space. You’ll need to uninstall them in the reverse order from how you add them.
• After the Out-Of-Box-Experience (OOBE) is complete, the default language cannot be removed. The default UI language is selected either during the Out-Of-Box-Experience (OOBE), or can be preselected in the image using DISM or an unattended answer file.
• Some time after OOBE, any pre-installed languages that haven’t been used are removed automatically. The language-pack removal task does not remove LIPs.

Cross-language upgrades are not supported. This means that during upgrades or migrations, if you upgrade or migrate an operating system that has multiple language packs installed, you can upgrade or migrate to the system default UI language only. For example, if English is the default language, you can upgrade or migrate only to English.

Add language packs, LIPs, and Features on Demand

We’ll check to see if the image includes FODs with language resources in satellite packages, build a custom and local FOD repository, add languages, and verify all language resources were pulled in for each FOD. Then we’ll add a LIP language and the language Feature on Demand packages.

To save space, you can remove English language components when deploying to non-English regions by uninstalling the language components in the reverse order from how you add them.

Mount an image (install.wim) that you plan to deploy using Windows PE or Windows Setup

Mount the Windows image:

Check to see if the image includes FODs with language resources in satellite packages

First, check to see if the image includes FODs with language resources in satellite packages:

Look for Feature on Demand packages, other than the Language Features, that include a language code in their name. For example, MSPaint:

The two packages here with the en-us language code embedded in the name are satellite packages with language specific resources. If any such package is present in your image, you must build a custom FOD and language pack repository to add languages from. This custom repository needs to include all FODs with satellite packages in your image and all language packs you wish to add. This enables DISM to automatically pull in the right FOD satellite packages when a language is added.

Build a custom FOD and language pack repository

If your image contains FODs with language resources in satellite packages you must build a custom FOD and language pack repository before adding language packs to ensure the language resources for each FOD are pulled in. If you fail to do this correctly, these features will not be localized. Starting with Windows 10, version 2004, this includes features such as Notepad, WordPad, MsPaint, and PowerShell ISE included in the image by default. If your image doesn’t include any FODs with language resources in satellite packages you can skip this section and add the FODs and language packs directly from the respective ISOs.

The following methods are recommended for building a custom FOD and language pack repository:

• If the size of the repository is not a concern, simply copy the contents of the FOD ISO and all language packs into the same directory.
• For a minimally sized repository, use the /export-source switch with DISM to export just the FODs included in your image that have satellite packages and any other FODs you’d like to add. Copy all language packs of interest into the same directory.

In the following example, we’ll build a minimally sized FOD and language pack repository. First, mount the Language Pack ISO and the Features on Demand ISO with File Explorer. This will assign them drive letters.

Next, export all FODs included in your image that have satellite packages, from the FOD ISO. If you know which languages you intend to add, you can include the associated language features too:

Where D:\ is the mount location for the Feature on Demand ISO

Next, copy the language packs of interest into the local repository. In this example, all language packs are copied.

Where E:\ is the mount location for the Language Pack ISO

Add language packs, LIPs (LXPs), and language features

Pre-install languages by adding the language packs and their corresponding Feature on Demand packages, including the base languages if you’re adding a LIP language.

Add a language pack:

Add the language pack(s) of interest. Note how the language pack is sourced from the custom repository:

Check to see that both the language pack(s) and FOD satellite packages containing language resources were added:

You should see something like this in the output:

In addition to the fr-fr language pack now appearing in the image, note how the MSPaint Feature on Demand has satellite packages containing both the en-us and fr-fr language codes present. Make sure this is the case for every FOD with language specific satellite packages, for each language you added.

Satellite FOD packages cannot be added manually, you must allow DISM to automatically pull them in.

If satellite FOD packages are not correctly included during image customization, they won’t be automatically pulled in immediately after the image boots.

Add LIP languages. In this example, we add Luxembourgish, which requires the fr-FR base language:

For Windows 10, version 1809 and later, LIP languages are delivered as LXPs:

Where E:\ is the Language Pack ISO

Verify that it’s in the image:

For earlier versions of Windows 10, LIP languages are delivered as .cab files:

Add language and region Features on Demand to support your language packs and LIPs. We recommend including the Basic, Fonts, OCR, Text-to-speech, and Speech recognition FODs if they’re available for the languages you’re pre-installing. Additionally, include the handwriting language component FOD if you’re shipping a device with a pen.

Not all LIP languages have all language components. Luxembourgish (lb-LU), for example, only has basic and handwriting FODs. You can learn which FODs are available for languages in the LP to FOD mapping spreadsheet

Example: adding Basic, OCR, Text-to-Speech, and Speech Recognition to fr-fr:

Example: adding Basic and Handwriting to lb-LU:

Verify that these packages are in the image:

Remove languages, LIPs, LXPs, and Features on Demand.

You cannot remove a language pack from an offline Windows image if there are pending online actions. The Windows image should be a recently installed and captured image. This will guarantee that the Windows image does not have any pending online actions that require a reboot.

Get a list of packages and features installed in your image:

Remove languages, .cab-based LIPs, and Features On Demand:

Remove LIPs added through LXPs:

Verify that they’re no longer in your image:

Change your default language, locale, and other international settings:

As of Windows 10, version 2004, if a .appx-based Language Experience Pack (LXP) backed language is passed as an argument then the language will be set as the System Preferred UI language and its parent language will be set as the Default System UI language. In prior versions only .cab based language packs were supported.

See which language settings are available:

For online images, use Control Panel, or the International Settings PowerShell cmdlets: Get-WinSystemLocale and Set-WinSystemLocale . This works with languages delivered as LXPs.

For more options, see

Add languages to the recovery environment (Windows RE)

For any language you add to Windows, add the language to the Windows Recovery Environment (WinRE), whenever possible.

Not all languages or LIPs have localized recovery images.

Use languages from the Language Pack ISO, not from the Windows 10 ADK, to localize WinRE.

Known issue: Windows RE included with Windows 10 October 2018 Update Thai language image (en-US base language + th-th language pack) shipped with an issue in which an end user will only see UI components (or English) without Thai language text in the Windows Recovery Environment, the text displayed during recovery (Push-button reset), and/or certain screens during the reboot process of feature updates. To fix this issue pre-install the 2018.11D Quality Update.

Mount the recovery image.

Offline: the recovery image is inside the Windows image:

Online:

Note, Windows RE is inside the Windows image until the Out of Box Experience, after which it is moved to a separate recovery partition.

Where D:\ is the Language Pack ISO.

Verify that they’re in the image:

Example output from /Get-Packages:

Commit changes to the recovery image:

For online images, also remove the mount folder:

Capture the changes

Offline: For Windows images (install.wim)

Commit changes to the Windows image:

Online: Modify a running Windows installation

Generalize and capture the image:

To learn more, see generalize.

Next steps

Localize more of Windows:

• Out of Box Experience (OOBE): Create localized end user license agreements (EULA), registration pages, and instructions for pairing keyboards and mice.
• Retail demo experience: Showcase your new devices on the retail sales floor with localized content.

Localize the installation process:

Add languages to Windows Setup: Now that you’ve added languages to your Windows image, make sure they appear in Windows Setup. You can also create Windows installation media that works in the user’s preferred language.

Add languages to WinPE to help your technicians install Windows in their preferred language.

Add languages to a Windows distribution share to help users on a corporate network select Windows in their preferred language