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
Kollenbach Christoph, What language packs are you downloading? I'm downloading (sept for 1809)
This pack does not contain the traditional lp.cab files, it instead contains Microsodt-Windows-client-language-packs so I'm not sure if I'm using the wrong packs or you are
When I use dism to merge the language packs, the commands are successful, and a subsequent /get-intl command confirms that the language packs are present in the wim and also within WinRe (after mounting and adding them there as well). However, when I deploy the Wim, the language packs are no longer present in either, and I do not see why.
I would rather not specify a locale using an unattend file, because as I understand it, that effectively changes the default UI of the Windows install, and because cross-language upgrades are not supported, a region-specific ISO would have to be used in order to upgrade the devices in the future, and that doesn't scale when managing several different countries. I may be incorrect in my understanding, but I've seen that referenced in multiple places.
My goal is to integrate a few languages into a standard default en-us .wim, and deploy it with English out of the box, but allow the users to toggle between desired language at the login prompt. Is that no longer possible?