Adding Local Experience Packs to your Windows image

[Pankaj Mathur]

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.

[Chris Fritzsche]

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?

[Pankaj Mathur]

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. 

[Anton Romanyuk]

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?

[Pankaj Mathur]

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

[Mark Lawler]

"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.

[Pankaj Mathur]

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

[Mark Lawler]

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...

[Pankaj Mathur]

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.

[Neo Beum]

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.

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.

[Neo Beum]

DOBLED POST EDIT

[Neo Beum]

DOUBLE POST EDIT

[Valter Anjos]

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!

[MTG_1]

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.

[Pankaj Mathur]

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.

[Valter Anjos]

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

[Pankaj Mathur]

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.

[Valter Anjos]

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

[Deleted]

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

[Valter Anjos]

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

[Pankaj Mathur]

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?

[Valter Anjos]

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

[Kevin_Vlasselaer]

Hi everyone,

Big thanks to Valter that's just describe the situation where i'm and could get an answer from Microsoft.

I'm a consultant and i'm currently implementing MDT and a multilanguage  Windows Enterprise 1809 for one of our customer.

After testing and spending hours to by-pass this problem, I need an official statement for this issue/feature/change to document and justify the time spended.

Could you please provide a link to an official statement on that?

Regards,

Kevin Vlasselaer

[Mika Määttä]

Hi, I must add Windows 10 Enterprise Version 1809 (en-us) install.wim other language packs and language packs interface (LIPs or LXPs) finnish and swedish. I try to find out from LanguagePack ISO and there Local Experience Packs but there is not fi-FI and sv-SE folders, why? How I can add these languages to my OSD install.wim, that finnish user can select Finnish and swedish user can select Swedish and other users use English? I read that it must add by Windows Store but how is possible to Reference image? I dont know what i must do, please can anybody help me?

Regards, Mika

[Brent Carteaux]

This is interesting, and I am continuing to follow this thread as I have many of the same issues, tasks to complete the 1809 install (with Language Packs) in my organization.

It is not as easy as it once was.

[Pankaj Mathur]

Hi, I must add Windows 10 Enterprise Version 1809 (en-us) install.wim other language packs and language packs interface (LIPs or LXPs) finnish and swedish. I try to find out from LanguagePack ISO and there Local Experience Packs but there is not fi-FI and sv-SE folders, why? How I can add these languages to my OSD install.wim, that finnish user can select Finnish and swedish user can select Swedish and other users use English? I read that it must add by Windows Store but how is possible to Reference image? I dont know what i must do, please can anybody help me?

Regards, Mika

Hi Mika,

Both Finnish and Swedish are SKU languages and therefore for both of them you will be installing lp.cab just like in the past. The lp.cab for both of these languages are available in the language pack ISO.

This switch to LXP only apply to LIP languages for now. You can learn more about the change here: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Local-Experience-Packs-What-are-they-and-...

Thanks,

Pankaj

[Mika Määttä]

Hi Pankaj, thanks your answer about this My problem, I will be test this tomorrow and I hope that it works, because I think that I was try this before and I get error messages when I ran DISM command. I will be back If it works or If not and attach screenshot about errors.

Regards,

Mika

[snruebes]

This is the biggest mess I have ever seen. Microsoft. Are you kidding us? Are you still considering and developing for enterprises or only for end users?

We are an English global company with more then 90 offices worldwide which is using 99 percent English only Windows 10 image to simplify support but of course we need localized keyboard layout and language features like basic typing (e.g. for Japanese users with IME support)  handwriting recognition (for tablets), text-to-speech, speech or ocr which are not in the normal LP.iso but in the FOD Disc1.iso as they are "Microsoft Windows Language Features" but if you select e.g. the Japanese LPX from the store it also includes these components.

When I look into the "LocalExperiencePack" folder of the SW_DVD9_NTRL_Win_10_1809_32_64_ARM64_MultiLang_LangPackAll_LIP_X21-91305.iso I cannot see the LPX for Japanese and many other limportant languages like German etc. but they is available in the MS Store as LPX files!!!! Why are you doing this? Why is the "LocalExperiencePack" subfolder of the LP.iso incomplete? How should an enterprise automate this configuration for a Japanese user? Especially as our users do not have Admin rights on their machines because of Security reasons and cannot go to the store and add these components by themself.

Why does a simply language addition via the Settings app or MS store requires admin rights and the UAC pops in? Especially as such a Langage addition is a not a machine but a user only (profile setting).

Again - a complete mess! You developing for end users only and change things which are use less for enterprise or even worse create unsolvable trouble for them.

I can not see any stringent strategy in the topic at Microsoft. Especially as MS discontinued  the option to offer LP and FOD is WSUS since Windows 10, version 1709. Now you can only download directly from Microsoft store servers.

But to ensure that Windows 10 clients with version 1709 or later also automatically download these optional components if the user installs an additional language when a WSUS server is configured, this WSUS bypass must be explicitly allowed via a corresponding GPO setting:
1. Go to Computer Configuration => Policies => Administrative Templates and then System.
2. Double click or open “Specify settings for optional component installation and component repair”
3. Make sure “Never attempt to download payload from Windows Update” is NOT checked
4. Make sure “Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)” is checked.

Source: https://www.stephenwagner.com/2018/10/08/enable-windows-update-features-on-demand-and-turn-windows-f...

Besides you need to consider, that the auto-download of FOD components only works if your user has admin rights - otherwise you see the LP sub components like "Basic typing", "Handwriting" or "Speech" in the Language Options window of the Settings apps but they are not downloaded - even if you click the "Download" buttons you don't get any error message or feedback - very poor UI design Microsoft!

Again very annoying the whole topic - especially as they is more or less no consistent documentation or communication except this insufficient blog here....

[snruebes]

This is the biggest mess I have ever seen. Microsoft. Are you kidding us? Are you still considering and developing for enterprises or only for end users?

We are an English global company with more then 90 offices worldwide which is using 99 percent English only Windows 10 image to simplify support but of course we need localized keyboard layout and language features like basic typing (e.g. for Japanese users with IME support)  handwriting recognition (for tablets), text-to-speech, speech or ocr which are not in the normal LP.iso but in the FOD Disc1.iso as they are "Microsoft Windows Language Features" but if you select e.g. the Japanese LPX from the store it also includes these components.

When I look into the "LocalExperiencePack" folder of the SW_DVD9_NTRL_Win_10_1809_32_64_ARM64_MultiLang_LangPackAll_LIP_X21-91305.iso I cannot see the LPX for Japanese and many other limportant languages like German etc. but they is available in the MS Store as LPX files!!!! Why are you doing this? Why is the "LocalExperiencePack" subfolder of the LP.iso incomplete? How should an enterprise automate this configuration for a Japanese user? Especially as our users do not have Admin rights on their machines because of Security reasons and cannot go to the store and add these components by themself.

Why does a simply language addition via the Settings app or MS store requires admin rights and the UAC pops in? Especially as such a Langage addition is a not a machine but a user only (profile setting).

Again - a complete mess! You are developing for end users only and change things which are useless for enterprise or even worse create unsolvable trouble for them.

I can not see any stringent strategy in the topic at Microsoft. Especially as MS discontinued  the option to offer LP and FOD is WSUS since Windows 10, version 1709. Now you can only download directly from Microsoft store servers.

But to ensure that Windows 10 clients with version 1709 or later also automatically download these optional components if the user installs an additional language when a WSUS server is configured, this WSUS bypass must be explicitly allowed via a corresponding GPO setting:
1. Go to Computer Configuration => Policies => Administrative Templates and then System.
2. Double click or open “Specify settings for optional component installation and component repair”
3. Make sure “Never attempt to download payload from Windows Update” is NOT checked
4. Make sure “Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)” is checked.

Source: https://www.stephenwagner.com/2018/10/08/enable-windows-update-features-on-demand-and-turn-windows-f...

Besides you need to consider, that the auto-download of FOD components only works if your user has admin rights - otherwise you see the LP sub components like "Basic typing", "Handwriting" or "Speech" in the Language Options window of the Settings apps but they are not downloaded - even if you click the "Download" buttons you don't get any error message or feedback - very poor UI design Microsoft!

Again very annoying the whole topic - especially as they is more or less no consistent documentation or communication except this insufficient blog here....

[Pankaj Mathur]

@snruebes : Thanks for providing your feedback and explaining your scenario. Please see response to your concerns.

1. LXP for Japanese and other languages is missing in ISO: We are on the journey to replace lp.cab with LXPs. Starting in 1809, for all LIP languages lp.cab has been retired and LXP is the only way to install them. For SKU languages or full languages such as Japanese, you still need lp.cab. Therefore the ISO contains LXPs for LIP and lp.cab for SKU languages. In 1809, for SKU languages we are using LXPs to provide translation improvements but the base translations are always in lp.cab. So in 1809 continue using lp.cab for SKU languages that are provided with the ISO.

2. Adding language requires admin account: Starting in 1809 we are removing this restriction and non-admins can add Windows display language via Settings app.

3. Language FOD UX design and workflow: Thank you for your feedback on that. Our product teams are looking into making this experience better.

[Kollenbach]

Hi all, 

I had the same Problem, creating a multilanguage Image for WIn10 1809.
On the VLC there is no Windows 10 Language Pack for 1809 available. (Full UI), BUT

there is a "VDA Language Pack" available.

Within the ISO there is the e.g.: .\x64\langpacks Folder where the complete language packs reside.

With this language packs you are able to create a Multilanguage "all-in-one" Image with all the FOD's and languages you want.

regards,

Christoph

[CarstenP]

Hi Pankaj,

I´m trying to add a language via settings in 1809 but I´m still prompted for admin rights. When can we expect a change in this behaviour, it is extremely inconveniant.

regards

Carsten

[Adrian Bishop]

Valter Anjos

 

Senior Member

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

Did you ever sort this out, we have english us and english Autralian listed, but would like to set english Australian as the default for all users

is this not possible anymore

---

[Adrian Bishop]

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

Did you ever sort this out, we have english us and english Autralian listed, but would like to set english Australian as the default for all users

is this not possible anymore

---

[Mr_Sam]

Pankaj,

Like others have posted, I am trying to deploy a multi-language Win10 1809 image. I have a worldwide customer base and frequently need to deploy an image that can be quickly converted between 8 UI languages. Prior to v1809 I would install the supporting files via Control Panel once on the VM used to create the image. During deployment of the image all languages would be available to select from any profile without having to redownload the files.

Currently I must select the language from the settings menu, then re-download the language files. This is not efficient.

Are you saying that Microsoft is working on allowing the "machine-wide" use of language support files to occur once again? If so, your post was dated many months ago - is there any progress to report?

[DonL_KEM]

Pankaj,

Like everyone else here, I am trying to create a multi-language image. Is there any solution for this yet? We have tried the same things everyone in this thread has tried with the same results, naturally. Is there any timeline on when this will be fixed? This is extremely inconvenient in an enterprise environment.

[Pankaj Mathur]

@Mr_Sam : You can create an image using and then adding 8 language packs to it via DISM. You can then select the default UI language from one of the 8 languages via Unattend workflow. Is there a reason this will not work for you? If so, what steps are you using to generate the multilingual images? What steps / process were working for you pre 1809 that don't work with 1809? 

If you have already added the language packs in the image then you wouldn't have to re-download them again - so trying to understand your workflow a better.

Thank you!

Pankaj

[Pankaj Mathur]

@DonL_KEM : Thank you for your feedback. Can you please provide the following additional information so that I can better assist you?

1. What steps are you using to create multi lingual image?

2. What languages are you adding to the image?

3. Which version of the OS are you trying to create the image on (1803, 1809 etc.)?

4. What steps in the workflow are not working / are inconvenient? 

5. Are you trying to create image for new machines or upgrading the OS on existing machines?

You can send this information to me in a private message.

[Pankaj Mathur]

Hi Pankaj,

I´m trying to add a language via settings in 1809 but I´m still prompted for admin rights. When can we expect a change in this behaviour, it is extremely inconveniant.

regards

Carsten

@CarstenP : This is fixed in the following https://support.microsoft.com/en-us/help/4490481/windows-10-update-kb4490481

You can now add a language pack via settings without requiring to be an admin. 

[DonL_KEM]

@Pankaj Mathur : 

1. What steps are you using to create multi lingual image?

Setup clean 1809 to test adding the languages on a VM.

2. What languages are you adding to the image?

We're trying to add de-de, it-it, ja-jp, sv-se, and zh-cn. Using the cab files from the most recent Windows 10 Language Pack ISO. All of these should be SKU languages.

3. Which version of the OS are you trying to create the image on (1803, 1809 etc.)?

1809

4. What steps in the workflow are not working / are inconvenient?

Adding the languages from language settings, within Windows, causes sysprep to fail. Injecting the languages with DISM, online and offline, doesn't seem to do anything, as they still seem to have to download. They inject successfully but when tested on a machine the languages are not there. We also need the, "Basic Typing", keyboard layouts that are associated with the languages which also causes sysprep to fail.

5. Are you trying to create image for new machines or upgrading the OS on existing machines?

Image for new machines

[EDubs]

 @Pankaj Mathur I'm attempting to do the same thing. I'm integrating language packs into 1809. They show up in DISM when I mount the WIM offline, but when I deploy the WIM, they dont show up as being installed. Also, despite the information presented here, if I try to add the language packs in 1809 from a user account without admin rights, I get prompted for admin credentials. I've tried to work around this by installing the language packs within windows during deployment, but that's not working either, because, while the languages show up under the admin account, any domain account added must download and install them. It's a bit of a mess. Is it too much to ask that if I integrate language packs into the wim (for both Windows and WinRe) that they actually be present when the system is deployed?

Also, as far as setting languages through the unattend file, my understanding of it is that if you set a language as default in the unattend file, that will effectively make that the default language and change the SKU, requiring you to deploy different ISO's for upgrade per region? Cant we simply have en-US as the default, and pre-install additional languages that actually show up in the OS when it's deployed?

[Kollenbach]

Hi all

There are some differences in W10 1903 and W10 Before.
The LP.cabs are avail in the VLC NOT in the OS-Selections (Left side:"Windows", they are in "Software Assurance".)
It is clear that you have the correct license for your Company.

Download the LP's and integrate the LP's (and "Features on Demand") for your languages.

e.g: en-US and de-DE

We use always a en-US OS as a Base OS.
Take the en-US-install-wim and integrate the LP's anf FOD's with DSIM.
Mount the Image
    Enable the Netfx3 and IE with DSIM: (c:\temp\1903_sxs is the sxs folder from the 1903 ISO)
       dism ... /enable-feature /featurename:NetFx3 /source:C:\Temp\1903_sxs

       dsim ... /enable-feature /featurename:Internet-Explorer-Optional-amd64 /source:C:\Temp\1903_sxs

   Add the LP's (C:\Temp\1903_LP have a copy of the needed FULL UI's)
      dsim .... /add-package /packagepath:C:\Temp\1903_LP\Microsoft-Windows-Client-Language-Pack_x64_en-us.cab

      dsim ... /add-package /packagepath:C:\Temp\1903_LP\Microsoft-Windows-Client-Language-Pack_x64_de-de.cab

   Add the Features on Demand: (C:\Temp\1903_FODs has the all the FOD's from the FOD-ISO)

       dism ....  /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~.cab

      dism .... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~.cab

       dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Basic-de-de-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Basic-de-ch-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Handwriting-de-de-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-OCR-de-de-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-Speech-de-de-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-TextToSpeech-de-de-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-TextToSpeech-de-ch-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-LanguageFeatures-TextToSpeech-de-at-Package~31bf3856ad364e35~amd64~~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
       dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~de-DE~.cab

      dism ... /add-package /packagepath:C:\Temp\1903_FODs\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~de-DE~.cab

   Add the Local Experience Packs: (C:\Temp\1903_LocExpPack are from the LP-ISO)

      dism... /Add-ProvisionedAppxPackage /PackagePath="C:\Temp\1903_LocExpPack\en-us\LanguageExperiencePack.en-US.Neutral.appx" /LicensePath:"C:\Temp\1903_LocExpPack\en-us\License.xml"

      dism .... /Add-ProvisionedAppxPackage /PackagePath="C:\Temp\1903_LocExpPack\de-de\LanguageExperiencePack.de-DE.Neutral.appx" /LicensePath:"C:\Temp\1903_LocExpPack\de-de\License.xml"

unmount the Image.

Use the "System Image Manager" and create a new unattend.xml ( for each language), in my case there are 2 xml's (de and en.
   Add all the packages you inseted to the Image and configure them as "permanent"
   Hide the Wireless Setup in oobe

   Config the languages with "Microsoft-Windows-International-Core"

   Here some parts of the XML for de-AT (German UI and Locale AT)

       :
    :
    <servicing>
        <package action="configure" permanence="permanent">
            <assemblyIdentity name="Microsoft-Windows-Client-LanguagePack-Package" .......
        </package>
        <package action="configure" permanence="permanent">
            <assemblyIdentity name="Microsoft-Windows-Client-LanguagePack-Package" .....
        </package>
        <package action="configure" permanence="permanent">
            <assemblyIdentity name="Microsoft-Windows-InternetExplorer-Optional-Package" ....
        </package>
        <package action="configure" permanence="permanent">
            <assemblyIdentity name="Microsoft-Windows-InternetExplorer-Optional-Package" .....
        </package>
 :
 :
    </servicing>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" .....
            <OOBE>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" ...
            <InputLocale>de-AT</InputLocale>
            <SystemLocale>de-AT</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>de-AT</UserLocale>
        </component>
    </settings>

This ist he example for the Win10 1809, in W10 1903 you have to add the Keybd for all needed langs !!

  e.g: .... the XML for de-AT:

             <InputLocale>de-AT;en-US</InputLocale>
            <SystemLocale>de-AT</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>de-AT</UserLocale>

In 1903: if you do NOT add the 2nd KeyBD (en-US), the User has to download the "Local Experience Pack" even if the pack is added to the Image...(the LocalExperiencePack will be DOWNLOADED, so the USer has to have an Internet Connection) 

Add a Collection variable to the EN and the DE ComputerCollections and query them in the Taskseq.
You can use a priority for this variable if a computer is in both collections

in each "Apply OS" set the correct unattend.xml.

don't Forget to adjust the Timezone Settings for each language

To be sure that the FOD's and LP's are inserted i added the FOD's and LP' in the Taskseq. additionally.
I did not test it if i don't do it. (no query of Collection variable).

After the Installation a Computer which is in the Collection of the DE-Clients, the UI is in DE, a "User" can Change to EN UI if he wants (no admin creds necessary)

regards

Christoph

[EDubs]

 @Kollenbach Christoph, What language packs are you downloading? I'm downloading (sept for 1809)

This pack does not contain the traditional lp.cab files, it instead contains Microsodt-Windows-client-language-packs so I'm not sure if I'm using the wrong packs or you are

When I use dism to merge the language packs, the commands are successful, and a subsequent /get-intl command confirms that the language packs are present in the wim and also within WinRe (after mounting and adding them there as well). However, when I deploy the Wim, the language packs are no longer present in either, and I do not see why.

 I would rather not specify a locale using an unattend file, because as I understand it, that effectively changes the default UI of the Windows install, and because cross-language upgrades are not supported, a region-specific ISO would have to be used in order to upgrade the devices in the future, and that doesn't scale when managing several different countries. I may be incorrect in my understanding, but I've seen that referenced in multiple places.

My goal is to integrate a few languages into a standard default en-us .wim, and deploy it with English out of the box, but allow the users to toggle between desired language at the login prompt. Is that no longer possible?

[EDubs]

@Pankaj Mathur  Has there been any update on how to make this work properly and integrate multiple languages into a wim without having to use an unattend file and deal with cross-language upgrade issues?

[oJHPqptYugMPIJwf]

Dear Microsoft TechCommunity, I cannot find the global LP ISO file in our portal containing "Microsoft-Windows-Client-Language-Pack_x64_en-us.cab" nor "LanguageExperiencePack.en-US.Neutral.appx" but only the ISO v1903 containing FOD_PT1 & FOD_PT2 with "*LanguageFeatures*.cab". Could you please advise ? I really need to download those files for an offline integration. Thanks in advance

[Dale_W]

After Weeks of banging my head it's sooo nice to see I'm not the only person struggling with this issue.

I am trying to create a 1903 build, via MDT, that is based on en-gb, but that a user can select to switch to either en-us, zh-cn or zh-hk.

Like others before me I can inject the LP's and LXP's but can't get the GUI to show an easy and visible option for the users to switch without having to download.

MS - C'mon this used to be easy - why have you over complicated it?

Thanks, btw, to all those who have contributed to this forum - it has certainly put my (almost mental) mind at rest. I can now see (and, after many weeks of head banging,  produce evidence) that this is a wider problem.

If anyone does come to a sensible method of doing this via mdt with little user interaction - please step forward and share your knowledge (other wise we appear to be in the hands of, what so far has been an incompetent) Microsoft :(

[Kollenbach]

Dear EDubs, 

These files ARE the traditional LP's.

You have to config the unattend.xml to config the LP's as "Permanent".

Dear oJHPqptYugMPIJwf ,

Here the way to the LP's:

regards

Christoph

[Benjamin Dudley]

I have the same problem as EDubs. I can successfully add language packs online using DISM, but the language never shows up in the Settings to select. I even followed this article from Microsoft on how to deploy these with SCCM.

https://support.microsoft.com/en-us/help/4468362/deploy-language-pack-as-application-in-configuratio...

After it's installed, I verified that the language pack is installed via Dism /online /get-intl. But it's still not in the language settings.

I've even tried to use the FOD commands (add-windowscapability) to add the languages and it's still the same... the just don't show up for the user to select.

[Benjamin Dudley]

It seems that after installing the CAB file using DISM on Windows 10 1809, you still have to do more to add the language to the list in the language settings. There are a couple powershell commands you can run to do this... but they have to be run AS THE USER that needs to select the language. In my case (and maybe others), there does not appear to be a way to add languages to a machine during build time and have those languages available for any user to select.

For reference, here is what works for me:

Installing ALL language CAB files (client language pack plus ALL FOD CAB files) via DISM:

Get-ChildItem -filter *.cab | % {Add-WindowsPackage -Online -PackagePath $($_.name)}

After they are all added, run these commands (Japanese for example):

$LangCode = "ja-JP"
$langs = Get-WinUserLanguageList
$langs.add($LangCode)
Set-WinUserLanguageList $langs -force

I hope this helps others.

[abnranger67x]

Forgive my ignorance, but I installed the full language packs (.cab) using lpksetup.exe. When I run dism /online /get-intl, I see the installed languages, but as partially localized. That said, is that sufficient if a user wants to change his/her keyboard, UI, etc. language? If not, would I then need to install the local experience packs? One other thing to mention, in the ISO I got from the VLSC for the languages, there were only the local experience packs, and the full languages (.cab) files on there. There were no FOD included, Is that a separate ISO that I need to download? Found this on Benjamin Dudley's comment:

Get-ChildItem -filter *.cab | % {Add-WindowsPackage -Online -PackagePath $($_.name)}

After they are all added, run these commands (Japanese for example):

$LangCode = "ja-JP"
$langs = Get-WinUserLanguageList
$langs.add($LangCode)
Set-WinUserLanguageList $langs -force

Does that mean I need to run this for every language? We have 30 languages for all the countries we are in. We build one gold image. I just want a process that would make the languages available for all users. The machine is already built, so an online process would be ideal. When I injected the languages into the install.wim, cortana/searchUI.exe, for some reason would not work once the machine was built, so I had to end up using lpksetup.exe afterwards.

[abnranger67x]

Well at this point, I think this all moot. Even when you add the languages to the list, it is ONLY for the current user. I hate to think that MS does not have a process for making this available for all users thru via an OSD process or just running a script.

[Bob_Panick]

Did anyone find a solution to this?

I've been beating my head against the wall on it.  I thought I had it solved, only to discover that the LXP routines fail when you try to add them offline because of missing dependencies.  Analyzing German DE-DE I discovered that when you install from the store it adds a bunch of X86 components and updates some existing components.  It looks like the main issue is getting all the prereqs.   But I have concerns that even if I get them installed in a task sequence that the users won't see them because it appears that LXPs are user focused not device focused.

Without LXP Intalled	With LXP installed	Version w/o LXP	Version w/LXP	Arch
Microsoft.Advertising.Xaml	Microsoft.Advertising.Xaml	10.1808.3.0	10.1811.1.0	x64
	Microsoft.Advertising.Xaml		10.1811.1.0	x86
Microsoft.NET.Native.Framework.2.2	Microsoft.NET.Native.Framework.2.2	2.2.27011.0	2.2.27912.0	x64
	Microsoft.NET.Native.Framework.2.2		2.2.27912.0	x86
Microsoft.NET.Native.Runtime.2.2	Microsoft.NET.Native.Runtime.2.2	2.2.27011.0	2.2.27328.0	x64
	Microsoft.NET.Native.Runtime.2.2		2.2.27328.0	x86
Microsoft.UI.Xaml.2.0	Microsoft.UI.Xaml.2.0	2.1810.18004.0	2.1810.18004.0	x64
	Microsoft.UI.Xaml.2.0		2.1810.18004.0	x86
	Microsoft.UI.Xaml.2.1		2.11906.6001.0	x64
	Microsoft.UI.Xaml.2.1		2.11906.6001.0	x86
	Microsoft.UI.Xaml.2.2		2.21909.17002.0	x64
	Microsoft.UI.Xaml.2.2		2.21909.17002.0	x86
Microsoft.VCLibs.140.00	Microsoft.VCLibs.140.00		14.0.27810.0	x64
Microsoft.VCLibs.140.00	Microsoft.VCLibs.140.00		14.0.27810.0	x86
	Microsoft.VCLibs.140.00.UWPDesktop	14.0.26905.0	14.0.27810.0	x64
	Microsoft.VCLibs.140.00.UWPDesktop		14.0.27810.0	x86

Part of the problem with this is, that many language aware applications need the OS languages installed before they themselves are installed.  Microsoft's answer may be to use Auto Pilot, which quite frankly doesn't work.  Even if we get around all the other Auto Pilot problems, we still have the problem of how do we make sure the LXPs are installed before the applications.  We use task sequences because we can guarantee a sequence of installed items with some intelligence built in.