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