问暂时将powershell语言改为英语？

EN

- On Windows Server 2012 / Windows 8 and above, the [**`Set-WinUILanguageOverride`**](https://learn.microsoft.com/en-us/powershell/module/international/set-winuilanguageoverride) **cmdlet** allows you to (persistently) **change the system-wide UI language for the current user**, but that only takes effect in _future_ logon sessions - that is, **logging off and back on or a reboot are required**.

- As an aside: On Windows Server 2012 / Windows 8 and above, there is also the [**`Set-Culture`**](https://learn.microsoft.com/en-us/powershell/module/international/set-culture) cmdlet, but its **purpose is** _**not**_ **to change the** _**UI**_ **culture (display language)**, but only culture-specific **settings such as date, number, and currency formats**. It too changes the setting _persistently_ for the current user, but only requires a new _session_ (process) for the change to take effect.

- Set [`[cultureinfo]::CurrentUICulture`](https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentUICulture) (temporarily) to the desired culture name (use [`[cultureinfo]::GetCultures('SpecificCultures')`](https://learn.microsoft.com/en-US/dotnet/api/system.globalization.cultureinfo.getcultures) to see all predefined ones) ; e.g.,  `[cultureinfo]::CurrentUICulture = 'en-US'`

    - Complementarily, you may want to set [`[cultureinfo]::CurrentCulture`](https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentCulture) (note the missing `UI` part) as well, which determines the culture-specific number, date, ... formatting.
    - In older versions of PowerShell / .NET, you'll have to set these properties on [`[System.Threading.Thread]::CurrentThread`](https://learn.microsoft.com/en-US/dotnet/api/System.Threading.Thread.CurrentThread) instead; e.g.,

- See the **bottom section** for **helper function** **`Use-Culture`** that wraps this functionality for execution of code with a different culture temporarily in effect; here's an example call with the culture-sensitive [`Get-LocalGroupMember`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/get-localgroupmember) cmdlet:

- An **ad hoc example**, if you don't want to define a helper function (only the UI culture is changed here):

# Runs a script block in the context of the specified culture, without changing 
# the session's culture persistently.
# Handy for quickly testing the behavior of a command in the context of a different culture.
# Example: 
#   Use-Culture fr-FR { Get-Date }
function Use-Culture
{    
  param(
    [Parameter(Mandatory)] [cultureinfo] $Culture,
    [Parameter(Mandatory)] [scriptblock] $ScriptBlock
  )
  # Note: In Windows 10, a culture-info object can be created from *any* string.
  #        However, an identifier that does't refer to a *predefined* culture is 
  #        reflected in .LCID containing 4096 (0x1000)
  if ($Culture.LCID -eq 4096) { Throw "Unrecognized culture: $($Culture.DisplayName)" }

  # Save the current culture / UI culture values.
  $PrevCultures = [Threading.Thread]::CurrentThread.CurrentCulture, [Threading.Thread]::CurrentThread.CurrentUICulture

  try {
    # (Temporarily) set the culture and UI culture for the current thread.
    [Threading.Thread]::CurrentThread.CurrentCulture = [Threading.Thread]::CurrentThread.CurrentUICulture = $Culture

    # Now invoke the given code.
    & $ScriptBlock

  }    
  finally {
    # Restore the previous culture / UI culture values.
    [Threading.Thread]::CurrentThread.CurrentCulture = $PrevCultures[0]
    [Threading.Thread]::CurrentThread.CurrentUICulture = $PrevCultures[1]
  }
}

function Set-CultureWin([System.Globalization.CultureInfo] $culture) { [System.Threading.Thread]::CurrentThread.CurrentUICulture = $culture ; [System.Threading.Thread]::CurrentThread.CurrentCulture = $culture } ; Set-CultureWin en-US ; [system.threading.thread]::currentthread.currentculture