Home
Microsoft

Adding Local Experience Packs to your Windows image

With Windows 10, version 1803, we started to deliver language translation improvements via Local Experience Packs, also referred to as LXPs. Local Experience Packs are AppX packages delivered via the Microsoft Store that enable users to experience Windows features like the Start Menu, Settings, and File Explorer in the language of their choice. We also continued to support cabinet file-based language packs (lp.cab) and Language Interface Packs (LIPs) via language pack ISO files distributed with Windows 10.

Beginning with the next major release of Windows 10, we are going to support LIPs as Local Experience Packs only. There will no longer be any lp.cab files for LIP. Local Experience Packs are faster to install and have a smaller operating system (OS) footprint. If you create Windows images with LIP, you will have to add the corresponding LXP for that LIP. For full languages, there is no change and you will continue to use the corresponding lp.cab.

You can start testing Windows image creation using LXPs using Windows 10 Build 17723 or higher EEAP builds. We are providing LXP AppX packages and their corresponding licenses for all 72 LIPs in the language pack ISOs.

The process will work like this. First, you will need to use the Add-ProvisionedAppXPackage cmdlet to add a Local Experience Pack to your Windows 10 image. Once you have added the Local Experience Pack to your image, you should see the following behavior.

  • The LXP will show up on the language selection screen of the out-of-box experience (OOBE).
  • When you select the LXP, all subsequent screens of the OOBE will be in the corresponding language. Since the LXP has only a subset of operating system strings available, some of the content in OOBE may fall back to the base language. This is on parity with current behavior.
  • The first login experience post-OOBE should be in the selected language.

  


Continue the conversation. Find best practices. Bookmark the Windows 10 Tech Community.

Looking for support? Visit the Windows 10 IT pro forums.

21 Comments
Frequent Visitor

How does this work for Enterprise organizations?  Are you going to provide the LXP's in an ISO file or do all of them need to be downloaded from the store?  What if we block the store?  What are our options?

Microsoft

Going forward LXPs will be part of the language pack ISOs. So if you are doing media based update on enterprise machines, you will be able to install LXPs from the ISO similar to how language packs are installed today. You do not need to go to the Microsoft Store. 

Regular Visitor

How does this change tie into MDT driven deployments? Current version supports legacy LPs - does this mean that a PowerShell-based wrapper is now required to install language packs at deployment time or will there be an MDT update to address this change?

Microsoft

We are working on a MDT update to address this change.

Visitor

"You can start testing Windows image creation using LXPs using Windows 10 Build 17723 or higher EEAP builds. We are providing LXP AppX packages and their corresponding licenses for all 72 LIPs in the language pack ISOs."

 

Where can i find the corresponding AppX Packages so i can install a language pack using DISM?

 

The language pack on VLSC is an old one even if it says it has an updated date of 2/10/18.

Microsoft

Please use the Windows 10 October 2018 release Language Pack ISO to access LXPs for LIP.

Visitor

Thanks for your reply.

 

I managed to download the language pack ISO but there's no EN-GB LXP?

 

I require the same one as this - https://www.microsoft.com/en-gb/p/english-united-kingdom-local-experience-pack/9nt52vq39bvn?cid=msft...

Microsoft

For creating Windows 10 October 2018 release image, use LXPs for LIPs only. Language pack ISO will have LXPs for all the LIPs. For full languages such as en-GB continue using lp.cab. If the user selects en-GB in OOBE then we will fetch the corresponding en-GB LXP from the Microsoft Store. The user will then get language improvements via store updates to en-GB LXP.

Regular Visitor

Australia needs its own LXP; - using en-GB base, if input locale has not been properly set - the keyboard will default to en-GB which will cause issues for Australian users due to the standard keyboard layout in available in market is en-US.

 

There are also problems when switching between LP/LXP and the Operating System itself lacks a definitive 'Language Pack' for Australia in the Windows Store - as the United Kingdom Local Experience will be downloaded to enable 'English - Australia' features and display language.

 

en-AU-DisplayLanguage.png

https://i.imgur.com/vTCuywy.png

This example highlights how en-UK is set for the Display Language but is absent in the Settings UI. Only en-AU and en-US appear as installed.

Regular Visitor

DOBLED POST EDIT

Regular Visitor

DOUBLE POST EDIT

Frequent Visitor

Hi,

 

This is a change that is causing some impact to the organizations that are offering images with multi language. In my organization we are creating a image with english + spanish, greek and german. On the past the users could change the language by theirselves using the control panel options and as far as I understood that is not possible anymore. We have the Windows Store blocked and if we install the lp.cab the control panel won't show the additional language as an option. It seems this is a new way to enforce the usage of the Windows Store which I can accept to the home customers but its hard to accept for enterprise users.

 

Could you please clarify how can we create a reference image with additional languages which will be available to be selected by the end-users through the modern control panel?

 

Thank you!

Occasional Visitor

It has been said: "Where can i find the corresponding AppX Packages so i can install a language pack using DISM? The language pack on VLSC is an old one even if it says it has an updated date of 2/10/18."

 

This is still unchanged, the VLSC does not offer new language pack ISOs that have an LPX folder. Could  Pankaj Mathur tell me if MS has forgotten to upload those or where I can find them.

Microsoft

Hi,

This is a change that is causing some impact to the organizations that are offering images with multi language. In my organization we are creating a image with english + spanish, greek and german. On the past the users could change the language by theirselves using the control panel options and as far as I understood that is not possible anymore. We have the Windows Store blocked and if we install the lp.cab the control panel won't show the additional language as an option. It seems this is a new way to enforce the usage of the Windows Store which I can accept to the home customers but its hard to accept for enterprise users.

Could you please clarify how can we create a reference image with additional languages which will be available to be selected by the end-users through the modern control panel?

Thank you!

Setting a language has moved from Control Panel to Settings app. Your users can now change the language by going to Settings app - Time & Language - Language. They do not need access to Microsoft Store to add any of the languages that you have pre-installed for them.

Frequent Visitor

Hi,

 

I would like to get the steps to get those options available. As I have stated the language packs were installed but on Settings app - Time & Language - Language the only option that I have is English when I have installed the German, Spanish and Greek LP. The only way to change the language is using the powershell cmdlets.

 

Please advise the right steps to achieve the configuration that you mentioned.

 

Thanks!

 

Regards,

 

Valter Anjos

Microsoft

It has been said: "Where can i find the corresponding AppX Packages so i can install a language pack using DISM? The language pack on VLSC is an old one even if it says it has an updated date of 2/10/18."

 

This is still unchanged, the VLSC does not offer new language pack ISOs that have an LPX folder. Could  Pankaj Mathur tell me if MS has forgotten to upload those or where I can find them.

 

In Microsoft Volume Licensing Center (VLSC) please look for Windows 10 Language Packs (Released Sep'18) 32/64 Bit Multilanguage ISO. ISO has LocalExperiencePack folder that contains 72 sub folders - one each for 72 LIP languages. For SKU languages, the ISO contains lp.cab as before.

Frequent Visitor

Hi Pankaj,

 

I think you are not understanding the behavior that we are seeing. We already got that ISO and I cannot find LXP for the languages mentioned (en-gb; es-es; el-gr). I already installed the lp.cabs but I can't see that options available on the UI Settings app - Time & Language - Language.

 

I don't know if you already tried to replicate the issue but the I think you are not following the same steps. This issue is not happehing only in our organization. I have seen some comments reporting the same. Probably we are missing something but there is no information about the steps which makes everything hard.

 

Please find the screenshots attached where you can see the lp installed and the only option available on the settings UI is English (United States).

 

Thank you!

 

Regards,

 

Valter Anjos

1809-language-2.jpg1809-language.jpg

 

 

 

 

Occasional Visitor
Hi Valter, In order to see the display Language, you must first add it the Preferred language list. Then you close the whole window and open the Language settings again and will be available. Best regards, Milen
Frequent Visitor

Hi Milen,

 

The languages that I have deployed with the lp.cab are not available on preferred language list. The only option seems to download the LXP from the Windows Store, which is blocked. Nevertheless that should not be an option even if it worked since the main goal is the automation for the reference image creation.

 

Thank you!

 

Regards,

 

Valter Anjos

 

1809-language-3.jpg

Microsoft

Valter,

As Milen recommended, in 1809 you will have to add the language to the preferred list as it will not show up in the Windows display language drop down. We are working on making the pre-installed languages show up in the Windows display language dropdown so expect to see that in future releases. 

For now, please click on Install after you see offline error message. That should add the language to user preferred language list as well as make it available in the Display Language dropdown. 

 

For SKU languages, you do not need to get the LXP or connect to the Microsoft Store. All 3 of the languages that you are installing - en-gb; es-es; el-gr - are SKU languages. You can read more about LXPs here: Local Experience Packs: What are they and when should you use them?

 

 

 

Frequent Visitor

Hi Pankaj,

 

Following the steps mentioned I can see the languages available on Windows Display Language drop down. Is there any automation that can be done in this case or is this will require manual steps?

 

Is this bug/feature/behavior documented somewhere?

 

Thank you!

 

Regards,

 

Valter Anjos