Hello,
We deploy Windows 10 in 11 different languages (de-de, en-gb, en-us, es-es, es-mx, fr-ca, fr-fr, nl-nl, pl-pl, pt-br, zh-cn). We install the language packs from the VLSC using dism, during a pause in the image capture sequence through MDT. We've created our last 2 images (21H1 and 21H2) this way without issue, but when we try to do this with the 22H2 iso from VLSC, the languages don't apply correctly.
We have a task sequence that sets the OS language/locale and deploys a computer in that language, using the pre-installed language pack. When we try to use this with 22H2 (en), our previously unattended task sequence now requires a selection of language at the end. If you choose fr-fr for example, it will only partially switch the language. The keyboard is still the default en-us one and the lockscreen is in english. This leads me to believe there's something wrong with how we're installing the language packs, but from what I've read, it appears there haven't been any recent changes to the deployment process for languages the way we use them. Also, we've configured Office to match the language of the Operating System during install. Previously, this worked as expected, but now it defaults to en-us (I assume this is because there's something wrong with applying the languages in the task sequence).
Has anyone seen this issue before? Can anyone recommend any log files that would be useful to see why switching the already pre-installed languages in the task sequence is no longer working? I appreciate any suggestions.
We deploy Windows 10 in 11 different languages (de-de, en-gb, en-us, es-es, es-mx, fr-ca, fr-fr, nl-nl, pl-pl, pt-br, zh-cn). We install the language packs from the VLSC using dism, during a pause in the image capture sequence through MDT. We've created our last 2 images (21H1 and 21H2) this way without issue, but when we try to do this with the 22H2 iso from VLSC, the languages don't apply correctly.
We have a task sequence that sets the OS language/locale and deploys a computer in that language, using the pre-installed language pack. When we try to use this with 22H2 (en), our previously unattended task sequence now requires a selection of language at the end. If you choose fr-fr for example, it will only partially switch the language. The keyboard is still the default en-us one and the lockscreen is in english. This leads me to believe there's something wrong with how we're installing the language packs, but from what I've read, it appears there haven't been any recent changes to the deployment process for languages the way we use them. Also, we've configured Office to match the language of the Operating System during install. Previously, this worked as expected, but now it defaults to en-us (I assume this is because there's something wrong with applying the languages in the task sequence).
Has anyone seen this issue before? Can anyone recommend any log files that would be useful to see why switching the already pre-installed languages in the task sequence is no longer working? I appreciate any suggestions.
