>

Change the Windows Display Language with PowerShell

Use Set-WinUILanguageOverride to switch the language Windows shows in menus and dialogs, e.g. to en-US or zh-CN.

WindowslanguagelocalepowershellLow risk
Run Set-WinUILanguageOverride -Language en-US (substitute any installed language tag) in PowerShell, then sign out and back in for every part of the UI to switch.

01Command

Command
$ Set-WinUILanguageOverride -Language en-US

02What it does

The display language is the language Windows itself uses for Start menu, Settings, and dialogs. Set-WinUILanguageOverride writes an override for the current user so Windows always uses that language regardless of the order in your language list. The language must be installed first — otherwise use Get-InstalledLanguage / Install-Language, or add it in Settings. The change is not instant everywhere: Explorer and most apps pick it up after signing out and back in.

03Risk

RiskLow risk
RequirementsThe target language must already be installed (check with Get-InstalledLanguage or add it via Settings).
!Warning: This changes UI text only, not keyboard layout or regional formats — pair it with Set-WinUserLanguageList or Set-Culture for those. Third-party apps with their own language settings ignore this.

04Undo

✓No undo needed — this command does not change persistent state.

05Sources

  • Set-WinUILanguageOverride
    Microsoft Learn · vendor-doc · 2026-09-17
    Evidence: Set-WinUILanguageOverride sets the Windows display language for the current user by overriding the user profile language list order.

Last verified: 2026-09-18 · Category: System & Settings

06Related solutions

Grep on Windows: Select-String
Windowssearchtextpowershell

Search inside text files and logs with regex, returning file, line number and match.

Low risk ✓ 2026-09-17
Zip Files with Compress-Archive
WindowsZip & Archivesarchivepowershell

Create or update a .zip from any files or folder contents straight from PowerShell.

Low risk ✓ 2026-09-17
Test a TCP port connection on Windows with Test-NetConnection
Windowsnetworktroubleshootingpowershell

A built-in PowerShell one-liner that answers 'is port 5432/3389/443 actually open through this network?' — no telnet client needed.

Low risk ✓ 2026-09-17