When we released Windows 10, version 1803, we introduced Local Experience Packs (LXPs), which are modern language packs delivered through the Microsoft Store or Microsoft Store for Business. The biggest advantage to LXPs is that we no longer have to wait for feature update releases to deliver improved translations to you. Instead, translation improvements can be delivered via LXPs as a Microsoft Store application update.

Not only can language packs be updated based on user feedback, allowing new versions to be released and applied to all PCs via the Microsoft Store application update process, we have also made it easier for users to provide feedback on Windows display strings by going to the Language Community tab of the Feedback Hub.

With the introduction of LXPs, we have started to retire legacy language packs (lp.cab). Beginning with Windows 10, version 1809, we have retired legacy language packs (lp.cab) for all Language Interface Packs (LIP).

If you are an OEM or an IT administrator, you can create Windows images with LIP by installing the appropriate LXP from the language pack ISOs that shipped with Windows 10, version 1809; however, for full languages (aka SKU languages), we have not yet retired the legacy language packs (lp.cab), so you will need to continue to add lp.cab for full languages to the OS image using Deployment Image Servicing and Management (DISM).

After the OOBE, if the device is online and connected to the Microsoft Store or Microsoft Store for Business, Windows 10 will automatically bring in the appropriate LXP for the user so that the device always has the latest translations. If the device is in a corporate environment where Microsoft Store access is blocked, the user will not receive translation improvements. The device will only have the translations that were shipped with the corresponding OS release.

The information above is designed for OEMs or IT professionals. If you are an end user, you can install and set a display language by either going to the Settings and selecting Time & Language > Region & language or by visiting the Microsoft Store. For more information, see Get Windows to speak your language. We will ensure that you get the appropriate LXP and have up-to-date translations on your device.


Continue the conversation. Find best practices. Bookmark the Windows 10 Tech Community.

Looking for support? Visit the Windows 10 IT pro forums.

Occasional Visitor

Hi Pankaj,


Is there any English Australian, Local Experience Packs that we can use to install on Windows 1809 using SCCM? or inject into the 1809 Image before upgrading from 1703 to 1809 please?


Or even if I can do it using DISM as before? Before creating SCCM task sequence.


After upgrading to perfectly working 1703 using SCCM upgrade TASK Sequence I get this errors. This is for Enterprise level. Our users do no pick these details when they log in, we set and install them before hand. No interaction from users. 




@WillemK : There is no separate English - Australian language pack at this time. To get this working you will have to add English - United Kingdom (en-GB) lp.cab for translation resources and associated FODs during the task sequence. LXPs only contain translation resources and in 1809, we have only retired lp.cab for LIP languages. For SKU / full languages like en-GB please continue using lp.cab.