Windows 10 version 1703 language pack
The following forum(s) have migrated to Microsoft Q&A: All English Windows 10 IT Pro forums!
Visit Microsoft Q&A to post new questions.
Answered by:
Question
Does anyone know what Disk or File I need in order to add different languages to a US version of Windows 10 Enterprise 1703?
For my 1607 build I had an actual Language Pack DVD with *.lp files that I could use lpksetup to automatically and silently install. One these language packs are not compatible with 1703. Two the only discs I could find 1703 specific were the Feature on Demand disks. But these don’t have the *.lp files I am expecting, but have cab files. I’ve installed the cabs with DISM but don’t know how to confirm if the languages are installed or not (When I go to change the language there is not a list of the 5 languages I installed).
Does anyone know how to do this? What *exact* disk I need? what *exact* steps to install? Microsoft documentation seems to make it more confusing than it has to be (at least to me).
Any help is appreciated.
Christopher Westpoint — Infrastructure Architect
Answers
Found it! This is the disc with the language packs — mu_windows_10_language_pack_version_1703_update_march_2017_x86_x64_dvd_10204769.ISO. This works with my LPKSETUP script.
This issue is this disc is on MSDN and not on the MVLS site where I get my 1703 distros.
Microsoft should call that out in documentation somewhere.
Christopher Westpoint — Infrastructure Architect
All replies
the LIP (Language Interface Pack) files for Windows 10 are for use with OEM builds to change the base language of the OS. Is that what you are looking for or are you trying to add optional keyboard, text to speech, spelling dictionaries and voice recognition updates (winkey+[spacebar]). the later do not change the UI language or default keyboard layout for the OS language. As far as I know, these can only be installed via the Settings>Region & language control panel. and are not LIP’s.
for deployment options using a customized windows image.
See if these links are useful:
Well in Windows 10, they were just called Language packs. This is what I used for Windows 10 1607 — SW_DVD5_NTRL_Win_10_1607_32_64_MultiLang_LangPackAll_LIP_X21-05987. Within that Disc was Microsoft-Windows-Client-Language-Pack_x64_es-es.cab (where es-es were the different languages I selected) and I was able to install and script with LPKSETUP to silently install. Now, the Microsoft-Windows-Client-Language-Interface-Pack_x64* were also on this disc but I don’t think I used them. When scripting with LPKSETUP I just point the executable to the folder of extracted files from the CD and provide the languages I need (i.e. — es-es, ar-sa, etc). Considering i dont see a LIP on that disc with ar-sa I assume I installed the language packs.
I am now trying to do the same with Windows 10 1703. I can’t find a MultiLang_LangPackAll_LIP CD for 1703. All I could find were two Feature on Demand Discs — SW_DVD9_NTRL_Win_10_1703_64Bit_MultiLang_FOD_1_X21-35556. Only Disc1 has anything remotely resembling language but they are named Microsoft-Windows-LanguageFeatures-Basic-es-es-Package.cab. Put when trying to install via LPKSETUP is doesnt recognize this disc or its cabs as language files making me believe this isn’t the right disc of language pack flies.
I can use DISM to install these language features but don’t know if they are the actual language packs.
The docs you linked explain what the packs are but not where to download them for 1703.
Christopher Westpoint — Infrastructure Architect
Windows 10 version 1703 language pack
ul > li:nth-child(1) > label < cursor: default; >.tabs2 input[name=tab-control]:nth-of-type(1):checked
.slider < transform: translateX(0%); >.tabs2 input[name=tab-control]:nth-of-type(1):checked
.content > section:nth-child(1) < display: block; >.tabs2 input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < cursor: default; >.tabs2 input[name=tab-control]:nth-of-type(2):checked
.slider < transform: translateX(100%); >.tabs2 input[name=tab-control]:nth-of-type(2):checked
.content > section:nth-child(2) < display: block; >.tabs2 input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < cursor: default; >.tabs2 input[name=tab-control]:nth-of-type(3):checked
.slider < transform: translateX(200%); >.tabs2 input[name=tab-control]:nth-of-type(3):checked
.content > section:nth-child(3) < display: block; >.tabs2 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < cursor: default; >.tabs2 input[name=tab-control]:nth-of-type(4):checked
.slider < transform: translateX(300%); >.tabs2 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(1) > label < cursor: default; >.tabs input[name=tab-control]:nth-of-type(1):checked
ul > li:nth-child(1) > label svg < >.tabs input[name=tab-control]:nth-of-type(1):checked
.slider < transform: translateX(0%); >.tabs input[name=tab-control]:nth-of-type(1):checked
.content > section:nth-child(1) < display: block; >.tabs input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < cursor: default; >.tabs input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label svg < >.tabs input[name=tab-control]:nth-of-type(2):checked
.slider < transform: translateX(100%); >.tabs input[name=tab-control]:nth-of-type(2):checked
.content > section:nth-child(2) < display: block; >.tabs input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < cursor: default; >.tabs input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label svg < >.tabs input[name=tab-control]:nth-of-type(3):checked
.slider < transform: translateX(200%); >.tabs input[name=tab-control]:nth-of-type(3):checked
.content > section:nth-child(3) < display: block; >.tabs input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < cursor: default; >.tabs input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label svg < >.tabs input[name=tab-control]:nth-of-type(4):checked
.slider < transform: translateX(300%); >.tabs input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(1) > label < cursor: default; >.tabs3 input[name=tab-control]:nth-of-type(1):checked
ul > li:nth-child(1) > label svg < >.tabs3 input[name=tab-control]:nth-of-type(1):checked
.slider < transform: translateX(0%); >.tabs3 input[name=tab-control]:nth-of-type(1):checked
.content > section:nth-child(1) < display: block; >.tabs3 input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < cursor: default; >.tabs3 input[name=tab-control]:nth-of-type(2):checked
.slider < transform: translateX(100%); >.tabs3 input[name=tab-control]:nth-of-type(2):checked
.content > section:nth-child(2) < display: block; >.tabs2 input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < cursor: default; >.tabs3 input[name=tab-control]:nth-of-type(3):checked
.slider < transform: translateX(200%); >.tabs3 input[name=tab-control]:nth-of-type(3):checked
.content > section:nth-child(3) < display: block; >.tabs2 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < cursor: default; >.tabs3 input[name=tab-control]:nth-of-type(4):checked
.slider < transform: translateX(300%); >.tabs2 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(1) > label < background: rgba(0, 0, 0, 0.08); >.pay-dow < margin-top: 0px; >div.widget-area.woodmart-sidebar-content < margin-top: 0px !important; >.tabs2 input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < background: rgba(0, 0, 0, 0.08); >.tabs2 input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < background: rgba(0, 0, 0, 0.08); >.tabs2 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < background: rgba(0, 0, 0, 0.08); >.tabs2 ul li label < padding: 5px; border-radius: 5px; >.tabs2 ul li label span < display: none; >.tabs2 .slider < display: none; >.tabs2 .content < margin-top: 10px; >.tabs2 .content section h2 < display: block; >.tabs input[name=tab-control]:nth-of-type(1):checked
ul > li:nth-child(1) > label < background: rgba(0, 0, 0, 0.08); >.tabs input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < background: rgba(0, 0, 0, 0.08); >.tabs input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < background: rgba(0, 0, 0, 0.08); >.tabs input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < background: rgba(0, 0, 0, 0.08); >.tabs ul li label < padding: 5px; border-radius: 5px; >.tabs ul li label span < display: none; >.tabs .slider < display: none; >.tabs .content < margin-top: 10px; >.tabs .content section h2 < display: block; >.tabs3 input[name=tab-control]:nth-of-type(1):checked
ul > li:nth-child(1) > label < background: rgba(0, 0, 0, 0.08); >.tabs3 input[name=tab-control]:nth-of-type(2):checked
ul > li:nth-child(2) > label < background: rgba(0, 0, 0, 0.08); >.tabs3 input[name=tab-control]:nth-of-type(3):checked
ul > li:nth-child(3) > label < background: rgba(0, 0, 0, 0.08); >.tabs3 input[name=tab-control]:nth-of-type(4):checked
ul > li:nth-child(4) > label < background: rgba(0, 0, 0, 0.08); >.tabs3 input[name=tab-control]:nth-of-type(4):checked
Windows 10 version 1703 language pack
The following forum(s) have migrated to Microsoft Q&A: All English Windows 10 IT Pro forums!
Visit Microsoft Q&A to post new questions.
Asked by:
Question
Using MDT 8443 I’ve created a 1703 image and applied en-gb (using packages within MDT) which basically updates the unattend.xml with the required language file..
In customsettings.ini setting UILanguage to en-gb sets the display interface correctly as one expects..
the issue I get is if I want to add additional language packs like fr-FR, de-DE etc.. I’ve tried to add them to the image using ‘packages’, LPKSETUP and Dism /Offline /add-packages..
Using Dism . /get-intl correctly shows the language pack installed but when the image has finished, the additional packages don’t appear within Settings, Region & language, Languages
Is this an issue with 1703?
All replies
According to your description, you have installed the language package into image. I su spect that the package may be not used when you install the system. Because this action could be controlled by answer file or task sequence.
You could check the setupact.log if the package installs successfully.
The link below is a similar case with your issue. But it uses the SCCM.
Hope it will be helpful to you
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
The language packs other than then default (en-gb) are not installed (checked with DISM /online /get-intl nor do they display within ‘Region & language’
The only way I can add the additional language packs is to use DISM /Add-Package (either offline or online)
Once I add these, I can see them in ‘Override for Windows display language’ but they don’t appear within ‘Change you language preferences’ unless I manually add them through the GUI or run ‘control intl.cpl,,f:\test.xml
Thank you for the update on the issue.
Yes, you can use DISM to add language packs to a Windows image. The Windows image that you start with can be in any language. For example, you can start with an English (en-US) image, and add support for French (fr-FR) or other language.
You could do it in answer file during deployment:
The answer is you could add UILanguage option in unattend.xml file in oobeSystem phase.
Hope it will be helpful to you
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
We have the same issue.
Under 1607 you used to be able to install a language pack with the command:
Then it was available to be selected either in Settings or through the unattend.xml file.
If you use the exact same command in 1703, what happens is that the language pack seems to install fine. There is no error message returned in response to the dism command, and if you do a «dism /online /get-packages» the package shows up as expected.
But, if you try to activate the language pack in settings the «Set as default» button is grayed out. If you try to set the language in the unattend file, you receive a cryptic error «Something has happened» then Windows continues booting in English.
IMO the reason for this is that the language packs released for 1703 so far are simply bugged and haven’t been beta tested.
Any further thoughts or updates on this one?
I have the cab added with dism, and have been trying to set it as default by using the «control.exe intl.cpl,, /f:»C:\Regional.xml» method, and doesn’t seem to be working in 1703. Really need a way to change selected language pack post installation, which means no unattend.xml.
I’ve just managed (3 minutes ago) to inject the en-GB language pack into a Windows 10 1703 (the July Respin with the July update rollup in) with SCCM 1702 and integrated MDT.
The steps I used were to run the following command line steps right after applying the install.wim image, still in WinPE:
With Microsoft-Windows-Client-Language-Pack_x64_en-gb.cab as the only file in the SCCM package attached to that step, finding it in the VLSC was a real pain until I found this MultiLanguage hint
And this to make it the default (no SCCM package needed):
I have also applied the 5 x Feature on Demand en-GB packages in another step identical to the first language pack, but a different SCCM Package; however I don’t think it is required for it to work.
Now I just need to work out how to retrospectively apply those to the 200 PCs we installed Windows 10 on so far in the last week and a half.
Really good write up on this!
I too have seen these issues. With the Online Application there is an issue in the ZTIOnlineLangPacks.wsf where it does not handle the Windows Version correctly and hence will not apply (dism is the answer) however its too late to enforce from the answer file.
Your first command combats what seems a bug in 8443/1703 combination by applying the Language pack albeit the application execution is a little more time comsuming in terms of seconds to execute.
The second command can be combatted by having an unattend.xml declaring out the OSDvaribales and then Dynamic variables in the TS prior to the Windows Settings which mean by the time the language pack appies (just after the image) it already knows what the OSDUILanguage value needs to be.
I delivered the Japanese Language Pack as a test and this 2nd command threw me an error 87 but if I just interface the first command with the items I mention above I get a complete experience in Japanese with a UK keyboard input so I can find my way around 🙂
Hope that helps if you are looking at Multi-National language delivery.