Please feel free to provide feedback or file bugs here.

PowerShell sessions don't support mixed-culture values such as 'en-DE'

Note: This may ultimately require resolution in the .NET framework.

Recent versions of Windows 10 support mixed culture values such as `en-DE` (sic) (since version 1703 - see https://msdn.microsoft.com/en-us/library/cc233982.aspx)

After using, e.g., `Set-Culture en-DE` to set the culture for future PowerShell sessions (which in itself succeeds, as you can verify at registry location [HKEY_CURRENT_USER\Control Panel\International]), subsequent PowerShell sessions quietly fall back onto culture 'en-US', as reflected in $PSCulture and [cultureinfo]::CurrentCulture.

Note that such a mixed culture *is* honored in PowerShell *Core*.

1 vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Michael Klement shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base