LogoLogo
TwitterLinkedInGitHubPowerShell Gallery
  • About
  • Events
  • Blog
    • 2022
      • 🆕OSD January Update
      • 🆕PSCloudScript Basics
    • 2021
      • Start-OOBEDeploy
      • OSDCloud
      • PowerShell Gallery in WinPE
      • BitLocker KeyProtectors
      • WindowsCapability -and WindowsPackage
      • Scheduled Tasks
        • Building a Task
        • Task Permissions
        • Task Trigger
        • Action a PowerShell File
        • Action a PS Encoded Script
        • Conclusion
          • Windows Activation and Edition Change
          • REG.exe and Multiple Actions
    • 2019
      • 2019-02
        • Offline Servicing vs Reference Image
      • 2019-04
        • Windows 10 Upgrade MultiLang (Uno)
      • 2019-06
        • Offline Servicing Windows 10 with CU for .NET 4.8
        • OSDBuilder and .NET CU KB4480056
      • 2019-09
        • Black Screen During Windows 10 Setup
      • 2019-11
        • I Hate OSDBuilder
    • 2018
      • WinPE 10 1809 WPF DLL Fix
      • Microsoft Update Releases
      • Create WinPE.wim from Boot.wim or WinRE.wim
      • Windows Setup: FAT32 USB with +4GB Install.wim
      • Windows 10 from ESD
      • Windows 10 1809 Appx Issues
      • Mount-WindowsImage -Optimize
  • Guides
    • Autopilot App Registration
    • PSCloudScript
      • PS Cmdlets
      • GitHub Gist
      • GitHub Git Repo
      • Content-Type | Azure Static Web App
      • Command Shortening
      • Azure Key Vault Secret
      • OSD PowerShell Module
      • PSCloudScript Examples
        • Autopilot
        • AutopilotOOBE
        • OSDCloud Live
        • WinPE PowerShell Gallery
        • OSDCloud WinPE and OOBE
    • go OSDCloud
      • Azure Function
      • Custom Domain
      • SSL Binding
      • Proxies
  • PowerShell
    • OSD
    • OSDCloud
    • OSDBuilder (Offline Servicing)
    • OSDSUS (Update Catalogs)
    • OSDUpdate (MS Updates)
    • OSDDrivers (Compact Drivers)
    • PShot
      • Release Notes
      • Usage
        • -Directory
        • $AutoPath
        • -Prefix
        • -Count
        • -Delay
        • -Clipboard
        • -Primary
        • The Object
      • Technical
        • Why a Module?
        • Resolution, Scale and DPI
Powered by GitBook
On this page
  • The Issue
  • The Workaround
  • Windows 10 fr-FR
  • Windows 10 en-GB
  • Conclusion
  1. Blog
  2. 2019
  3. 2019-04

Windows 10 Upgrade MultiLang (Uno)

Previous2019-04Next2019-06

Last updated 6 years ago

I'll start by saying that working with multiple languages is a pain. I don't use MultiLang in my Enterprise, so I don't have much experience, but I do like to solve problems. Secondly, this is not a solution, but a workaround.

The Issue

Global organizations can deploy Windows 10 in a variety of different (Setup) Languages. This causes a problem when it comes time to deploy Feature Updates, as the Windows 10 Upgrade must be in the same Language as the System UI.

This means that a system that was installed with Windows 10 fr-FR, must be upgraded with Windows 10 fr-FR, Language Packs won't cut it.

worked on this problem by booting to WinPE and changed the System UI there

The Workaround

The remainder of this document will detail the Workaround, and it has a simple premise. Change the default System UI BEFORE you need to do a Windows 10 Feature Update

Windows 10 fr-FR

In this case, I am starting with Windows 10 1803 fr-FR and no Language Packs installed

I've installed Notepad++ as a control to make sure that this is an Upgrade and not a Refresh

I'll start Windows 10 Setup en-US. I have disabled the Network on this VM to ensure I don't get any random interference

Failure. Unfortunately this won't work because the Default System UI Language (fr-FR) does not match the Operating System I am trying to install (en-US)

Windows 10 en-GB

Let's switch gears to an English installation ... same problem, we can't upgrade with en-US if our install is en-GB, but here is the trick. If the Windows installation contains the en-US Language Pack, a simple Registry Change and a Reboot is all that is needed. In this case I have changed the InstallLanguage to 0409 which is en-US

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nls\Language

And now I'll be able to upgrade Windows en-GB to Windows en-US

Upgrading ...

Conclusion

Its quite possible to upgrade any Windows 10 as long as you have the target Language Pack installed and enabled in the Registry. Some things to note:

  • Changing to a different System UI will not change the language for Windows Store Apps, etc. You must allow your computers to talk to Windows Store to obtain the appropriate Language Resources as they will be in your new Base Language only

  • The Language Pack for the existing Language must be added to your new Install.wim

  • You should restore the Registry Keys back after the Upgrade is complete

This was just a practical workaround to prevent changing the System UI in WinPE, and to keep from maintaining multiple images. I'll share Windows 10 Upgrade MultiLang (Deux) in the next few days

While made separate images for each language

Dawn Wertz
Anton Romanyuk
Mastering Windows 10 Language Packs - Vacuum Breatheradmiraltolwyn
Change Language in WinPE
Servicing Windows 10 when Multiple Languages are InstalledLiving Life 1 Diet Pepsi at a time
Separate Language Media
Logo