Manual install boot.wim with DISM
- Thread starter RBCC
- Start date
I'm not understanding why you want to add optional language support to both images.
When performing a clean install, you can use Windows Setup (index 2) or a scripted WinPE solution (index 1). Because you can't use both images at the same time, the unused other image gets no benefit from added updates.
The install process can support multiple languages in three distinct scenarios:
https://www.ntlite.com/community/in...age-packs-for-winpe-windows-11-10-8-1-7.3013/
You have to decide which features you want to support. Could you add all 38 languages to Setup? Yes, but that's too much work.
In the real world, most admins add a handful of extra languages to Setup.
When performing a clean install, you can use Windows Setup (index 2) or a scripted WinPE solution (index 1). Because you can't use both images at the same time, the unused other image gets no benefit from added updates.
The install process can support multiple languages in three distinct scenarios:
- You're using a single-language Setup to install a multi-language install.wim
Setup will only display in the base language, but it can choose to apply a multi-language Windows to the target disk. When the install disk boots for the first time, it continues the install running as the multi-language Windows.
- You're using a multi-language Setup to install a single-language install.wim
Setup can display in multiple languages, but it will install a single-language image without being able to modify the install image.
- You're using a multi-language Setup to install a multi-language install.wim
Both Setup and install.wim have independently installed language support. You could run Setup in French, to install an Italian image. Setup's language preferences are unconnected to the install.wim's contents. The two WIM's don't even have to have matching languages.
- individual WinPE Language Pack (lp.cab)
- WinPE-Setup_[lang]
- WinPE-Setup-Client_[lang] (for Desktop editions)
- WinPE-Setup-Server_[lang] (for Server editions)
https://www.ntlite.com/community/in...age-packs-for-winpe-windows-11-10-8-1-7.3013/
You have to decide which features you want to support. Could you add all 38 languages to Setup? Yes, but that's too much work.
In the real world, most admins add a handful of extra languages to Setup.
Last edited:
After you install any language pack(s) to an image, they're permanent until removed by DISM. If you didn't see any new languages, then you're not adding them (or all of the required OC's) correctly.
What exact packages have you integrated in boot.wim?
winpeshl has nothing to do with language support, it's a wrapper app in the WinPE startup sequence which is used to launch other apps, if WinPE doesn't find setup.exe in the right places.
You haven't followed any of the directions provided in previous link.
If you did try to add those WinPE packages, it would be obvious that NTLite currently has a bug where it ignores the language OC's, and won't integrate them – but it will add the other required Setup files. Since NTLite appears to be ignoring the LP CAB's, you have to bypass that step by adding them by hand.
1. Download and install WinPE ADK Add-on's (26100.2454).
3. From NTLite, load boot.wim (index 2).
4. For each language, add the local WinPE-Setup_* and WinPE-Setup-Client_* packages from folder "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs".
5. Apply changes.
6. Manually mount the boot.wim:
7. Manually add each of the PE LP's:
8. Edit the "C:\Mount\sources\lang.ini" file:
9. Commit the changes to boot.wim:
10. From NTLite, create an ISO from the ISO folder.
All that has been done is Setup itself will be displayed in a different language. This has no impact on the actual install image, which be customized separately with a set of Windows (not WinPE) LP's.
If you did try to add those WinPE packages, it would be obvious that NTLite currently has a bug where it ignores the language OC's, and won't integrate them – but it will add the other required Setup files. Since NTLite appears to be ignoring the LP CAB's, you have to bypass that step by adding them by hand.
1. Download and install WinPE ADK Add-on's (26100.2454).
If you have an older version of the PE Add-on's installed, adkwinpesetup will ask you to uninstall the old version before proceeding.
2. Extract the Windows ISO to a local folder, using 7-Zip.3. From NTLite, load boot.wim (index 2).
4. For each language, add the local WinPE-Setup_* and WinPE-Setup-Client_* packages from folder "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs".
5. Apply changes.
6. Manually mount the boot.wim:
Code:
mkdir C:\Mount
Dism /mount-image /imagefile:\path\to\folder\boot.wim /index:2 /mountdir:C:\Mount7. Manually add each of the PE LP's:
Code:
Dism /image:C:\mount /add-package /packagepath:"\path\to\da-dk\lp.cab"
Dism /image:C:\mount /add-package /packagepath:"\path\to\de-de\lp.cab"
Dism /image:C:\mount /add-package /packagepath:"\path\to\es-es\lp.cab"
Dism /image:C:\mount /add-package /packagepath:"\path\to\fr-fr\lp.cab"8. Edit the "C:\Mount\sources\lang.ini" file:
Code:
[Available UI Languages]
en-us = 3
da-dk = 0
de-de = 0
es-es = 0
fr-fr = 0
it-it = 0
nb-no = 0
nl-nl = 0
[Fallback Languages]
en-us = en-us9. Commit the changes to boot.wim:
Code:
Dism /unmount-image /mountdir:C:\Mount /commit10. From NTLite, create an ISO from the ISO folder.
All that has been done is Setup itself will be displayed in a different language. This has no impact on the actual install image, which be customized separately with a set of Windows (not WinPE) LP's.