Share via

Add languages to custom image

Antoine Julien 0 Reputation points
2026-05-01T18:26:10.65+00:00

Hi,

I am trying to create a custom pro image and add languages to this image.

I followed this procedure : https://learn.microsoft.com/en-us/azure/virtual-desktop/language-packs

Here is my issue : When I first enter OOBE, if I select a language that is not the default language (en-us is set by default), the UI does not update (stays in en-us) until first reboot.

If I complete setup and reset the PC, when I enter OOBE, the UI updates dynamically depending on the selected language right away.

Am I missing something?

Thanks.

Windows for home | Windows 11 | Recovery and backup
0 comments No comments

2 answers

Sort by: Most helpful
  1. Lychee-Ng 18,605 Reputation points Microsoft External Staff Moderator
    2026-05-04T12:16:09.4433333+00:00

    Hi Antoine Julien,

    I understand how confusing it can be to see unexpected results even when you’ve followed the instructions correctly. The Q&A Assist has given very detailed explanation, so I'll be direct here: you’re not missing any steps in your procedure.

    That behavior occurs because the method you used only installs and stages the language packs, not for changing default UI language in OOBE on first boot. As the guide is designed for Azure Virtual Desktop, it focuses more on making those available to users after sign‑in.

    So when you follow that to configure your Pro image, during the first OOBE, the UI still initializes using the base image language (en‑US). Selecting another language may not apply immediately until the first reboot completes. The language configuration is only initialized after setup and reset.

    In short, the guide prepares languages for post‑login usage. It doesn’t control how OOBE applies UI language on first boot. If your goal is to have the UI switch immediately during the very first OOBE, you’ll need to configure that language as default in the image before capture.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Q&A Assist
    2026-05-01T18:26:24.14+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior is expected for commercial Windows editions starting with Windows 11 and Windows 10, version 2004, and is related to how the System UI language and System Preferred UI language are set.

    Key points from the documented behavior:

    1. Starting with Windows 11, the default System UI language set by DISM is left unaltered on all commercial editions. The language chosen during OOBE is set as the System Preferred UI language, and Windows is displayed in this language.
    2. As of Windows 10, version 2004, when an .appx-based Language Experience Pack (LXP) is passed to DISM, that language becomes the System Preferred UI language and its parent language becomes the Default System UI language.
    3. For online images, changing language/locale after deployment is done via Control Panel or the International Settings PowerShell cmdlets (Get-WinSystemLocale / Set-WinSystemLocale), not by re-running the same offline DISM steps.

    What this means for the scenario:

    • When the image is first generalized and captured with en-US as the default System UI language, OOBE initially runs with that default. Selecting another language in the very first OOBE run may not immediately switch all UI elements until after the first reboot, because the System Preferred UI language is only fully applied after OOBE completes and the system restarts.
    • After completing OOBE once and then resetting the PC, the image now has the System Preferred UI language mechanism fully in place. On the next OOBE run, changing the language causes the UI to update dynamically as expected.

    Nothing is missing from the language-pack integration itself; this is how language selection and application are designed to work with System UI vs System Preferred UI language on Windows 11 and Windows 10, version 2004 and later.

    If a different language must appear as the default right from the first OOBE screen, configure that language as the System Preferred UI language in the image before capture (for example, using DISM /Set-AllIntl:<language> on the offline image, or Set-WinSystemLocale on the online reference system before running sysprep), so that OOBE starts in that language instead of en-US.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.