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...
Updated May 02, 2019
Version 3.0
Blog Post
Forgive my ignorance, but I installed the full language packs (.cab) using lpksetup.exe. When I run dism /online /get-intl, I see the installed languages, but as partially localized. That said, is that sufficient if a user wants to change his/her keyboard, UI, etc. language? If not, would I then need to install the local experience packs? One other thing to mention, in the ISO I got from the VLSC for the languages, there were only the local experience packs, and the full languages (.cab) files on there. There were no FOD included, Is that a separate ISO that I need to download? Found this on Benjamin Dudley's comment:
Get-ChildItem -filter *.cab | % {Add-WindowsPackage -Online -PackagePath $($_.name)}
After they are all added, run these commands (Japanese for example):
$LangCode = "ja-JP"
$langs = Get-WinUserLanguageList
$langs.add($LangCode)
Set-WinUserLanguageList $langs -force
Does that mean I need to run this for every language? We have 30 languages for all the countries we are in. We build one gold image. I just want a process that would make the languages available for all users. The machine is already built, so an online process would be ideal. When I injected the languages into the install.wim, cortana/searchUI.exe, for some reason would not work once the machine was built, so I had to end up using lpksetup.exe afterwards.