I have created a solution for this topic for Windows 11 (23H2). I tested it on a vanilla en-us image, but I’m confident it will work with any other image as well. My goal was to provide a good user experience during Autopilot (= correct keyboard layout) and also allowing users to change both the operating system language and keyboard layout afterward.

I implemented this using the following two solutions:

Change language and keyboard layout during Autopilot (Windows 11 (23H2)) – cmdctrl4U – An IT blog

Confirm timezone, language and keyboard layout after Autopilot – cmdctrl4U – An IT blog

Feel free to check it out and give it a try. I’d greatly appreciate any feedback!

What kind of bugs me is the timing. Even with a modern, fast laptop being connected to a 250 Megabit Internet connection the process of adding a language takes up to 25 minutes for me. And I try to keep the ESP as slim as possible, since Office 365 already takes a good portion of the time during ESP.

Unfortunatly I ran a bit tight on the clock and switched to a different method (as we use OSDCloud anyways currently in this special use case). But I was wondering if anyone got better runtimes with using the “-ExcludeFeatures” parameter. I’m just not sure yet on how to add the FoD languates afterwards. Maybe running the command again without the switch?

Same problem running the script both via a win32 and platform script.
Hangs for many minutes before the autopilot/esp service ends it and continues/fails the esp.

I’m not sure if this is the right script you need to use as you only want to change the display language.
You’re now mentioning different settings, that are managed with different settings/ PowerShell commands.
Set-WinHomeLocation for example changes the location.
With Get-WinUserLanguageList you can change the keyboard.
But you might also need Set-WinSystemLocale, which needs to be run as administrator. So you need to see for yourself which combinations of settings/ commands does the job in your situation.

To add a little more details.
Our PC’s come with Danish installed. But our requirements are US as corporate Display Language.
So I’d need to install the US as Display language as well as install the language needed for the other settings, region, time/date, keyboard etc.
Got any tips for me Peter?

I also would like to know what I should change in the script if I need the Display Language in US and all other settings in the language I define.
Thanks in advance!

Hi Gordon,

Regarding the default language, remove CopySettings from the script and see if that does the job for you.
If you mean the location that is retrieved by running Get-WinHomeLocation, you need to change the value for $geoId to 244.

This is great! It worked like a charm for me. I would like the default language and location to still be en-US. What’s the best approach to do that given your script? Should a $language2 be added or parts of your script be removed?

Hi Hennie,

I added some info to the blog post to describe these values.