Windows 10: Info on the Language Packs and the Local eXperience Packs

balubeto · Jan 13, 2021

Hi

What is the difference between the iso files that contain the Language Packs and the Local eXperience Packs?

Could you please tell me the names of these iso files for Windows 10 Enterprise LTSC 2019 32 bit and 64 bit?

Thanks

Bye

:)

Brink · Jan 13, 2021

Adding Local Experience Packs to your Windows 10 image

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.

Click to expand...

Source: Adding Local Experience Packs to your Windows image - Microsoft Tech Community - 254125

Brink · Jan 13, 2021

Adding Local Experience Packs to your Windows 10 image

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.

Click to expand...

Source: Adding Local Experience Packs to your Windows image - Microsoft Tech Community - 254125

WinDoge · Jan 13, 2021

Adding Local Experience Packs to your Windows 10 image

So this is why installing a second language worked fine before, but now it fails.

Before, when the second language I'm trying to install (English (US)) was a regular language pack it all worked fine, but now when I try to install it on a new computer it tries to install the English (US) Local Experience Pack instead and fails.

One would the think that English is a rather well known language that doesn't need a Local Experience Pack to improve translations (from English to English?) but apparently not.

Windows 10: Info on the Language Packs and the Local eXperience Packs

Info on the Language Packs and the Local eXperience Packs

Info on the Language Packs and the Local eXperience Packs

Info on the Language Packs and the Local eXperience Packs

Info on the Language Packs and the Local eXperience Packs - Similar Threads - Info Language Packs

Where is English Australia Local Experience Pack

Microsoft why is there not a Local Experience Pack for Australia

en-us enterpise local experience pack

Random local experience packs in various languages in the app list

local experience pack

No Handwriting in Language Experience pack

How to Remove Local Experience Packs

language pack english united kingdom experience

What is the difference between "Add a language" and adding a Local Experience Pack