LangPack Integration (21H2's Appx vs 1809's CAB files) - Cross-Apply process Change Question

bseklecki_ge

bseklecki_ge

Member
On older v1809 builds with CAB based langpacks, I was able to cross-apply the Langpack to the Setup (Boot.wim) image.

However, my first experience on 21H2, with AppX langpacks, under Apply, if I check [Integrate - MSIX/APPx - Boot.wim (Windows Setup)] , it doesn't appear in the "pending task" list.

Is this normal?



~BAS

Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup0.png

Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup1.png

Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup4.png

Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup3.png
 

Attachments

  • Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup0.png
    Integrate_LangPack_AppX_LTSC_2021_21H1_Apply_Setup0.png
    183.9 KB
Thanks.

Is in the boot.wim (WinPE) in versions >v1809 (2004-22H2) able to just accept the single .CAB format instead ? (Same process as the old version?) Even if it is sub-optimal.

E.g., Microsoft-Windows-Client-Language-Pack_x64_XX-YY.cab, apply to both images?

Otherwise, there are 35x+ .cab files in the \Windows Preinstallation Environment\[arch\\WinPE_OCs]\[Lang]\* subfolders; seems messy

I'll do some testing today on [Win10 EntIOT LTSC 2021] and [Server 2022] and come back with results.

1672296552647.png

1672296768104.png
 
I don't know why on the newer ISO, they named every base version "lp.cab" instead of "lp_fr-fr.cab". Seems rather stupid.

No, WinPE always has separate LP CAB's which you can't mix with normal Windows CAB's. That's always been the rule. In the past, you needed to install the ADK/AIK to download the WinPE CAB's. Now they're on their own ISO.
 
You're correct; putting the Langpack/AppX for the main OS Image WIM (Install.WIM) will just skip/fail in the Setup/WinPE:

(However, I could swear that this worked back in v1809 -- I'll go back and check my notes)

What I'll do now:

Append/Modify my documented procedure to open just the Boot.Wim/Setup and apply all of the WinPE LangPack (.cab)s first, save/apply only just that task, then proceed with the other changes to the main Install.Wim

Update: My procedure already calls for opening Boot.Wim/Setup already first, to add a "subset" of drivers stirctly for STORAGE systems, so if this indeed works, its not a drastic change.

1672306674678.png


1672306725635.png

1672306762092.png

1672306782286.png
 
Last edited:
Most of these LP-Related .cabs other than the main lp.cab will fail to integrate anyway.

For extra-credit: Why does WinPE have a "GamingPeriphreals" langpack? >:}

1672307633049.png

1672307570400.png


1672307673006.png
 
garlin said:
I don't know why on the newer ISO, they named every base version "lp.cab" instead of "lp_fr-fr.cab". Seems rather stupid.

No, WinPE always has separate LP CAB's which you can't mix with normal Windows CAB's. That's always been the rule. In the past, you needed to install the ADK/AIK to download the WinPE CAB's. Now they're on their own ISO.
Click to expand...

ADK WinPE addon still available and include the same (or less) WinPE lang packs
main pack had been named lp.cab since Wndows 8 :)
with Vista/7 AIK it was lp_fr-fr.cab

now you mentioned it, why don't add links for adkwinpeaddons.iso instead adkwinpesetup.exe here? :)

Language Packs for WinPE (Windows 11/10/8.1/7)

Users may want to create a multi-language WinPE image, allowing them to choose the Setup language after boot. This requires adding WinPE-specific Language Packs, which are different from the Language Packs added to normal Windows. Adding WinPE language packs only changes Setup, it doesn't...
www.ntlite.com www.ntlite.com
 
bseklecki_ge said:
For extra-credit: Why does WinPE have a "GamingPeriphreals" langpack? >:}

View attachment 8887
Click to expand...
MS instructs OEM's to use WinPE for their factory prep of pre-configured systems. You need Gaming Peripherals support to check if certain HW works before shipping it. Otherwise you would have to boot a full Windows to validate.

bseklecki_ge said:
View attachment 8886
Click to expand...
You can't integrate the language add-on if the base CAB isn't installed. All the red packages are optional features.
 
garlin said:
I bet abbodi would know that answer!

All I can find is:
https://software-download.microsoft...4-1628.co_release_amd64fre_adkwinpeaddons.iso
Click to expand...

It's the same predictable file name scheme :)
but they started to make it harder with GUID in W11 22H2

Code: 
22621
http://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/22621.1.220506-1250.ni_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/22621.1.220506-1250.ni_release_amd64fre_adkwinpeaddons.iso
22000
http://software-static.download.prss.microsoft.com/pr/download/22000.1.210604-1628.co_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/pr/download/22000.1.210604-1628.co_release_amd64fre_adkwinpeaddons.iso
20348
http://software-static.download.prss.microsoft.com/pr/download/20348.1.210507-1500.fe_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/pr/download/20348.1.210507-1500.fe_release_amd64fre_adkwinpeaddons.iso
19041
http://software-static.download.prss.microsoft.com/pr/download/19041.1.191206-1406.vb_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/pr/download/19041.1.191206-1406.vb_release_amd64fre_adkwinpeaddons.iso
18362
http://software-static.download.prss.microsoft.com/pr/download/18362.1.190318-1202.19h1_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/pr/download/18362.1.190318-1202.19h1_release_amd64fre_adkwinpeaddons.iso
17763
http://software-static.download.prss.microsoft.com/pr/download/17763.1.180914-1434.rs5_release_amd64fre_ADK.iso
http://software-static.download.prss.microsoft.com/pr/download/17763.1.180914-1434.rs5_release_amd64fre_ADKwinpeaddons.iso
 
>>>> (However, I could swear that this worked back in v1809 -- I'll go back and check my notes)

Update: At least with Srv16/v1607, I only ever had to integrate the Langpack into the main OS image, and never had to modify WinPE (HINT: possibly the RTM WinPE Images for Server2016 had most of the mainstream langpacks pre-integrated?)

[X21-23013 Windows Svrs 2016 1607 MultiLang OPK -3 Language Pack]
[UTE X21-49493 SW DVD9 NTRL Win Svr Language Pack 2016 64Bit MultiLang -3]

Name: [x64fre_Server_fr-fr_lp.cab]
 
You must log in or register to reply here.
Back
Top