Windows Autopilot

Configure language settings for any scenario

You might have noticed that there are new properties available in Windows Autopilot user-driven scenarios, both for Azure AD Join:


And for Hybrid Azure AD Join:


But if you try it, you’ll find that they do nothing.  That’s because these new options require changes that are present in Windows 10 Insider Preview builds and will ship in a couple of months as part of Windows 10 2004.  So if you want to try it out, grab one of those builds.

There is one key limitation with these settings (beyond the OS version requirement):  In order for them to be effective, the device will need to be connected via Ethernet so that the Autopilot profile containing these settings can be downloaded and processed early on.  If you are connecting via Wi-fi, you have to choose the language, locale, and keyboard layout manually before you can make a Wi-fi connection, and therefore it’s too late to apply these settings because you’ve already passed that point.

Another important note about these:  If you configure them, you won’t be able to initiate a white glove deployment any more, because OOBE will automatically progress past the point where you can press the Windows key five times.  So, if you want to automatically choose a language, don’t do white glove; if you want to do white glove, don’t configure these.  We’ll try to remove this restriction in a future release.  (Alternatively, you could choose not to make a network connection, e.g. don’t connect the Ethernet cable, until after you’ve pressed the Windows key five times.)

Categories: Windows Autopilot

4 replies »

  1. The setting language (region) , affect this also the language pack if availble in image (lxp pre-installed)?

    Regarding “…won’t be able to initiate a white glove…” , it would general helpful/great to shift the user login prompt behind the steps device prep, setup and account setup (without auth) to the end. So, the advantage of WhiteGlove would not be lost and even if the end user do the user driven enrollment (reset) it himself, it would only be necessary to do something when the device is almost ready. Comes close to the self-deploying autom. process, but with user.


  2. This is great news but I’d love an option to at least default to the local region so the end user can just hit next next next. We use white glove heavily and this is a great progress step for automation but won’t work for our Surface Go’s because of that Ethernet requirement! Those pesky trade offs 😀