Since Microsoft has decided to replace language packs (LPs) in .cab format with Local Experience Packs (LXPs) format. In the future, Microsoft is going to support LXPs only. There will no longer be any LPs.cab files for LIP. This will remove the overhead of needing language Packs (LP) as a prerequisite for installing Language Interface Packs (LIPs). Here are some possible errors you can encounter while resolving this issue Error 0xc1570103: The license file was not found in the specified path , and how to fix error 0xc1510114: The wim file needs to be remounted.
Local Experience Packs are faster to install and have a smaller operating system 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. LXPs are the successor of the traditional LIP files. Additional to the list of the previous LIPs, you now also have LXP files for all those languages for which you have had only a full language pack available.
It is worth noting that, this doesn´t mean you can deploy an LXP for a language like German or French, etc., and expect that the entire Operating System gets translated. LXP files where a full language pack is available will just translate the most used parts of the Operating System. That’s what they mean by “partially localized language” in the output and why LXPs are smaller than the LP CAB files.
Note: 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.
Note: Windows 2019 will still retain the .cab format for now. At the moment, System Admins who want to add additional LPs to the Windows image before deployment can choose between .cab files and LXPs for the May update.
The Local Experience Packs (LXPs) If required can also be downloaded directly from the Microsoft Store as Appx packages as well. These Appx will be added from the Microsoft store. This is a very quick way to implement Feature on Demand such as Handwriting, speech to text dictation, and additional language packs.
Here are the various ways, you can add the LXPS to Windows. I will be discussing below how this can be achieved with DISM tool and PowerShell.
– Via the GUI in Windows and
– The Unattend.xml route
With DISM: Integrate LXPs into Windows Image (install.wim).
With this method, OOBE, you can add one or more local experience packs (LXPs, basically, stripped-down language packs) so that the user can choose between them at the start of OOBE. More Information can be found here.
dism /image:G:\Path-to-the-mount-file\MountZ /Add-ProvisionedAppxPackage /packagepath:G:\Path-the-LXPs\de-de\LanguageExperiencePack.de-DE.Neutral.appx /licensepath:G:\Path-to-the-License\de-de\License.xml
When th above command is run and it is successful, you should get a similar message as shown below.
Image Servicing and Management tool
Image Version: xxxxxxxx
The operation completed successfully.
Now that the packages have been added successfully, you will have to save (commit) the changes made to the wim file as shown below. This will unmount and save the newest state.
dism /unmount-wim /mountdir:G:\Path-to-the-mount-file\MountZ /commit
PowerShell: Integrate LXPs into Windows Image (install.wim).
This provisions the AppX in the system, and it should appear in the language selection during the out-of-box experience (OOBE) phase. More information can be found here.
Add-AppxProvisionedPackage -Path G:\mount -PackagePath .\LanguageExperiencePack.de-DE.Neutral.appx -LicensePath .\License.xml
For more information, on how to add languages to Windows image using DISM and PowerShell, see the following guide.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session