Windows 10: Inject LXP language packs to Windows 10 image

/u/_kniem · Nov 24, 2020

Hi,

When I inject LXP language packs to Windows 10 install.wim and start installation with that media OOBE does not allow me to select a language. Does anyone know what is the trigger for OOBE to allow selecting language?

I also tested this method without success.

Windows 10 2004 + every local experience pack = A planet-wide OS image – Out of Office Hours (oofhours.com)

submitted by /u/_kniem
[link] [comments]

:)

Brink · Nov 24, 2020

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 · Nov 24, 2020

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

Nachappa C K · Nov 24, 2020

Speech Language packs

Hi,

Thank you for posting your query in Microsoft Community.

I understand the inconvenience that you are experiencing. I will definitely assist you.

There are few languages that windows 10 has pre installed in the system itself, I suggest that you check these languages and locate the language that you want to install. Follow the steps below to locate the language.

Click on the Start Menu, locate and select Settings.

Click on Time and Language.

Locate and select Region and Language.

Click on Add a Language.

If you cannot find the language there you can download a language pack for Windows 10 from the link below:

Language packs for Windows

Hope the information helps. Please let us know if the issue persist and we will be happy to assist you further.

Windows 10: Inject LXP language packs to Windows 10 image

Inject LXP language packs to Windows 10 image

Inject LXP language packs to Windows 10 image

Inject LXP language packs to Windows 10 image

Inject LXP language packs to Windows 10 image - Similar Threads - Inject LXP language

Language Packs

language pack

Windows 10 language pack issue

Windows Language pack

Windows 10 Language Pack

Language Pack Windows 10

windows 10 home language pack

Window language pack

How to Inject Drivers to Windows 10 Image