Local Experience Packs: What are they and when should you use them?

[Pankaj Mathur]

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.

[WillemK]

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. 

[Pankaj Mathur]

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

[Sochito]

Hi Pankaj, Thank you for this post. We need to roll out Windows 10 1903 in our Company in different geographies, UK being the main location. Just wanted to understand, for applying en-gb do I need to use .cab or .appx as Multilanguage ISO contains both for 1903? Please suggest.

[grantmm]

Just +1 on having issues with this in 1903, 1909. I've resorted to manually setting during the capture stage as existing methods no longer work. This is in particular related to trying to set Australia as the Windows Display Language.

[abucione]

I was able to successfully add LXP to our images (we use 4 languages in our client) and I get prompted to select which language to use in OOBE. So far, so good.

But, how do I make this selection in unnatend.xml? the <UILanguage> directive seems to be ignored by OOBE. Is there an alternative?

[Bob_Panick]

I really wish Microsoft would stop "fixing" things that already work, particularly when you don't provide a viable solution to implement them.  We are deploying operating systems using SCCM OSD, and I have yet to figure out a way to make the old or the new solution work.  We were planning on moving from 1803 as our standard image, but this is holding us back. Our requirement is Win 10 en-us with the option to install languages based on user need before installing the rest of the applications in a task sequence.

It appeared that I could use the S4B, select the German LPX, and use the offline version which packages up with SCCM nicely.  But alas, the install fails because a prereq is missing, and I haven't a bloody clue what its missing.

And before you say, just let the users install it, sorry that doesn't work, because language sensitive applications are effected by it.  We also can't use Intune and Auto Pilot, well because it doesn't work, particularly with dependencies.  Like install German before installing Office, and install Office before adding WebEx components. 

[codaamok]

When should I use LPX and when should I use "for full languages (aka SKU languages)" (lp.cab)? What do I not get with LPX whereas I do get with LP?

[Bob_Panick]

Take a look at this thread it has a very detailed explanation of what's required and should answer your questions.  Unfortunately its complex, fortunately the author shows how to do it.

https://techcommunity.microsoft.com/t5/premier-field-engineering/windows-10-multilanguage-deployment...

[codaamok]

Sadly not, it just shows how to install LXP during bare metal OSD using ConfigMgr. Doesn't really give me the foundation understanding of when I should LXP over LP, or vice versa.

I have noticed in lab however, trying out installing LP and LXP, that everything (?) is localised using LP whereas LXP has the majority localised, and you can "top-it-up" with FoDs.

The benefit I found with LXP is that the InstallLanguage does not change, so if you use task sequence to IPU then you don't have to worry about using lots of OS media with different languages.

The onus is on the user though because not everything is localised.

Also, it seems you have to update from the Microsoft Store to get more localised, because immediately after OSD not as much is localised compared to after updating lots of apps from the Store. This lines up with what I've been reading about LXP, it gives Microsoft more opportunities to implement better translations over time seamlessly.

That's my take after playing around in a lab for a couple of days. It's quite a minefield really.

[abucione]

Hi @Bob_Panick , thanks for the article, I will try that!

[codaamok]

@abucione check out this blog post I wrote which may help: Language Packs, Language Experience Packs, Language Interface Packs.. what 

[abucione]

Hi @codaamok , Excellent article! thanks for sharing!

[chengm]

agree

[ValentynaFilimonova]

Hi Pankaj, FYI: just noticed that the link to the video Get Windows to speak your language in the final paragraph seems to be broken or the resource no longer exists.