Windows Display Language Download

Posted on by admin

Article Summary

  • Microsoft Windows Language Pack Types. Some Windows users may find that some parts of their operating system interface do not display in desired language after installing language pack. That’s because Microsoft provides 3 types of language pack: Fully localized language pack: It contains 100 percent of the resources for a language and locale.
  • Below is the list of language pack downloads (Windows 10 x64) that we have found with download links for each one: Title. Windows 10 Language Pack – Spanish. 1 file (s) 4711 downloads.

This article provides steps to localize a language on Windows Server 2019.

Im trying to install and use a new language in Windows 10 1809 with powershell. I'm installing the language pack using: Add-WindowsPackage -Online -PackagePath. Lpde.cab After the installation is done, i'm try to set the language of the whole windows 10 using: Set-Culture de-DE Set-WinUILanguageOverride -Language de-DE.

Change the Language of Windows Server 2019


  1. Open the Start menu and click the gear icon.

  2. Click Time & Language.

  3. Click Language in the left pane.

  4. On the Language screen on the right, click Add a language.

    NOTE: If your language is displayed under the 'Preferred languages' section, click it and click the upper arrow to move it top, and go to step 8.
  5. On the Choose a language to install screen, select your language from the list and click Next. In this step, the Japanese is selected as an example.

  6. On the Install language features screen, check if all items are selected and click Install.

  7. If your system can connect to the internet, downloading and installation of a language pack start.

    If your system in the offline environment where cannot connect to the internet, please download and install the language pack ISO by using method 2 in the Microsoft Technical Information.
    After the installation, return to step 5 and select your language, and click Next. If the following message is displayed, ignore it and click Install.
    You’re currently offline. When you’re connected, go to Language settings, select the language in the list, select Options, and finish downloading.
  8. Click Options of the added language.

  9. On the Language options: screen, check if 'Language pack installed' is displayed in the 'Language Pack' section and click left arrow icon at the top left corner.

  10. On the Language screen, select your language from the Windows display language pull-down menu and click Date & time from the left pane.

  11. On the Date & time screen, select your time zone from the Time zone pull-down menu.

  12. Select Region from the left pane and select your region from the Country or region pull-down menu.

  13. Scroll down on the Region screen and click Additional date, time, & regional settings under 'Related settings'.

  14. On the Clock and Region window, click Region.

  15. On the Region window, open the Administrative tab and click Copy settings in the 'Welcome screen and new user accounts' section.

  16. On the Welcome screen and new user accounts settings screen, select all items under the 'Copy your current setting to' section and click OK.

    If the dialog box requests restart is displayed, click Cancel in this step.
  17. On the Administrative tab screen, click Change system locale in the 'Language for non-Unicode programs' section.

  18. On the Region Settings screen, select your region from the Current system locale pull-down menu and click OK.

  19. On the dialog box requests restart, click Restart now to restart the system.

  20. After restart completed, check if the language of interfaces such as logon screen is changed to the selected language.


Starting with Windows 10 1803, Microsoft has begun to replace language packs (LPs) in .cab format with Local Experience Packs (LXPs). You can also add these AppX packages via the store. They will change language management fundamentally for admins. Only Windows Server 2019 will keep .cab files for the time being.
  • Turn off web search in Windows 11 using Group Policy - Tue, Dec 28 2021
  • Set default web browser in Windows 11 using Group Policy - Thu, Dec 23 2021
  • Configure iSCSI connections with PowerShell - Tue, Dec 14 2021

Microsoft traditionally differentiates between LPs and language interface packs (LIPs) when it comes to multilingual operating systems. The former are complete LPs for important markets, such as the US, Germany, France, China, and Spain.

These also have features on demand, such as handwriting recognition, spell checking, and text-to-speech.

Selection of language features in the settings app

Windows Display Language Download

On the other hand, LIPs only contain a partially translated interface for less widely used languages or smaller markets, and they require a regular LP as a basis (see this overview).

All LPs for Windows 10 1903 as LXPs ^

In the past, Microsoft made the language files available in .cab format. If required, they can be integrated offline into a Windows image using DISM. With Windows 10 1803, however, the migration to LXPs began. These files are available in AppX format, and you can therefore obtain them also from the store.

You can add LXPs to the OS via the store

Since version 1809, LIPs are no longer available as .cab files but only as LXPs. Users can download the .iso images containing all languages supported by Windows 10 from the Volume Licensing Service Center (VLSC) or from My Visual Studio (formerly MSDN). For version 1903 it also ships several regular LPs as LXPs, and all of them are available in the store too. But for the time being, they are additionally available as .cab files on the .iso.

The .iso file with the LPs now contains all languages as LXPs

Integrating LPs into a Windows image ^

This juxtaposition of formats, installation sources, and separate versions for each release of Windows 10 makes the situation confusing. Admins who want to add additional LPs to a Windows image before deployment can choose between .cab files and LXPs for the May update.

Each release of Windows 10 requires its own version of the LPs

An installation of LPs by the admin is mainly for companies that do not want their users to get apps from the Microsoft Store themselves. For integrating the .cab version into an image, you can still use DISM with this pattern:

Similarly, you would install the LXP for Italian with PowerShell as follows:

Windows Display Language Download

This provisions the AppX in the system, and it should appear in the language selection during the out-of-box experience (OOBE) phase.

See Full List On Support.microsoft.com

Adding an LXP online ^

It gets more complicated if you install the LXP into a running Windows system by using the Online switch instead of the Path parameter:

The LP then becomes available in the system and installed for the user currently logged in.

You can easily verify this with PowerShell in an administrative session:

Viewing the installed LXP with PowerShell

However, Microsoft's move to AppX means you must add each LXP separately for each additional user.

You could do this with PowerShell like this:

With these two commands, you would install the Italian LXP for the current user. If you now expect the Settings app to reflect the newly added language in its list, you'll be disappointed. PowerShell can fix this with:

Now since you have explicitly activated Italian as the new display language, it also appears in the Settings app.

If in this example you want to use Italian not only for the display but also as your preferred language, proceed as follows:

Display

Only after activating a language with PowerShell does it appear in the Settings app

Adding an LP using the GUI ^

Language

To be able to add LPs including optional features via the Settings app, you have to log on to the system as an administrator. As you know, running the app with elevated rights via runas is not possible. Standard users can only add a new display language themselves.

The redesigned language configuration page offers two options for interactive installation. First, you can download an LP from the store by clicking on the corresponding link. Secondly, you can reach this goal by clicking on the plus symbol under Add a language.

Both options for adding languages in the app settings lead to the same result

The result for both methods is obviously the same. Only the language you place at the top of the list is the preferred language and will determine the appearance of applications. All others are just additional languages. Thus, early builds for Windows 10 20H1 will only show one language in this list.

Add Windows Display Language Windows 10

In addition, since Windows 10 1809, it is possible to set the display language separately from the default language for applications and websites. Current previews of Windows 10 20H1 divide the language configuration even further and allow you to select the language for voice input independently.

Previews of Windows 10 20H1 allow a separate configuration of different language settings

Windows Server 2019 ^

Windows Server 2019 got stuck halfway during the transition from .cab to LXP. While you could still add an LP in the Settings app with version 2016, this procedure does not work anymore. Downloading an LP from the store is not possible because the store app is missing here.

After adding a language, it is missing for the GUI localization

If you want to install an LP this way, you will get the optional features, but the corresponding display language is missing. Even if you see a Download button for the LP on the options page, it won't work. Instead, you should add an LP as a .cab file before the interactive installation in the Settings app.

Subscribe to 4sysops newsletter!

Add an LP under Windows Server 2019 with lpksetup.exe

Windows 10 Display Language Russian Download

Since the LPs for Windows 10 are not compatible with the server OS, the required .iso is a separate download. It is generally available and not bound to a volume license as it is on the client. The installation then occurs via lpksetup.exe as usual for .cab LPs.