Localize

Configure your image with the right set of languages, settings, and keyboards or other input devices for customers in different regions.

Localizing Windows

You can add languages and regional support to Windows 10, Windows 11 (except for Home Single Language and 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: Fully-localized Windows UI text for the dialog boxes, menu items, and help files that you see in Windows. Delivered as .cab files, for example, Microsoft-Windows-Client-Language-Pack_x64_es-es.cab.
  • Language Interface Packs (LIP): Partially-localized languages. LIPs require a base language pack. For UI that's not localized in the LIP, Windows shows UI from the base language pack. Delivered as .appx files, for example, LanguageExperiencePack.am-et.neutral.appx.
  • 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 lower-cost devices with small storage, it does lead to an incomplete language experience. Delivered as .cab files, for example, Microsoft-Windows-LanguageFeatures-Basic-fr-fr-Package.
  • Recovery languages: UI text for the Windows Recovery Environment (WinRE). Delivered as .cab files. Example: lp.cab, WinPE-Rejuv_fr-fr.cab, and more.
  • International settings: Specify the default language, locale, and keyboard values during deployment or after Windows is installed.
  • Out of Box Experience (OOBE): Create localized versions of 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.

You can add languages and regional support to Windows 10, Windows 11 (except for Home Single Language and 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: Fully-localized Windows UI text for the dialog boxes, menu items, and help files that you see in Windows. Delivered as .cab files, for example, Microsoft-Windows-Client-Language-Pack_x64_es-es.cab.
  • Language Interface Packs (LIP): Partially-localized languages. LIPs require a base language pack. For UI that's not localized in the LIP, Windows shows UI from the base language pack. Windows 11 has five LIP languages, available as .cabs, available for preinstall.
  • 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 lower-cost devices with small storage, it does lead to an incomplete language experience. Delivered as .cab files, for example, Microsoft-Windows-LanguageFeatures-Basic-fr-fr-Package.
  • Recovery languages: UI text for the Windows Recovery Environment (WinRE). Delivered as .cab files. Example: lp.cab, WinPE-Rejuv_fr-fr.cab, and more.
  • International settings: Specify the default language, locale, and keyboard values during deployment or after Windows is installed.
  • Out of Box Experience (OOBE): Create localized versions of 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.

Localizing the installation process