Adding Local Experience Packs to your Windows image

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. 

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?

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?

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!

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

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

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

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-features-on-or-off-in-wsus-environments/

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

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