This article is contributed. See the original author and article here.

With Windows 10, version 2004, OEMs and system administrators can now package Windows images with Local Experience Packs, or LXPs.


With Windows 10, version 1803, we started to deliver language translations via Local

Experience Packs, also referred to as LXPs. LXPs are smaller than their counterparts because they only contain a subset of language translations that cover most of Windows. Once the device is connected to the internet the rest of the translations are downloaded to the device. As an OEM or system administrator; however, you previously had to add for full languages (SKU languages) to the OS image using Deployment Image Servicing and Management (DISM).

Now that OEMs and system administrators can package images with LXPs, there can be significant storage space savings. Specifically, devices with LXP-backed images can support more than twice as many languages out of the box with less than half the storage space[1] needed by traditional images.


The table below gives an overview of common language configurations and the potential space savings[2] that LXPs can provide.


Note: When creating images with LXPs, at least one will still be required.


Image configuration

Total size (on disk)

Total LXP size (on disk)

Space reduction

(~40 languages)

7.1 GB

2.47 GB


(~25 languages)

5.2 GB

1.8 GB



While Language Interface Packs (LIPs)  are only supplied as LXPs, full languages are supplied both as LXPs and lp.cabs.


To add an LXP to your Windows image, you will need to use the AddProvisionedAppXPackage cmdlet. Once you have added an LXP to your image, you should see the following behavior.


  • The languages backed by LXP will show up on the language selection screen during the out-of-box experience (OOBE).
  • Once the user selects their language, 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 will be in the selected language.

Things to be aware of

When creating an LXP-powered image, please be aware of the following pre-conditions:


  • The System Default UI Language can only be set to a language that is backed by To have the system display a language backed by LXP, you will need to set the User UI Language setting to that language. For more information, see User Interface Language Management.
  • After OOBE, the PC must be connected to the internet to download resources and complete the localization experience as LXPs only contain a subset of all translations. If a device is not able to connect to WSUS after installation, then it is recommended that lp.cabs be used instead.
  • LXPs only carry language resources for Features on Demand (FODs) with satellite language resources preinstalled by Microsoft. If other FODs with satellite resources are added to the image, language resources will be downloaded later in the background, when LXPs are used. For more information on how to enable FODs with satellite language resources out of the box. see Features On Demand.


[1] Storage savings are estimates, actual space savings will vary. 

[2] The savings displayed on the table primarily correspond to the image size. After the Windows Installation is complete, unused languages will be removed from the system. 

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

%d bloggers like this: