title: Change the current culture of a Powershell session, v3.0+ specific
body: <p>I want to change the culture of accepted data and errors in my current interactive Powershell session. I am aware of this question <a href="https://stackoverflow.com/questions/7052765/powershell-changing-the-culture-of-current-session">powershell : changing the culture of current session</a> and of this question <a href="https://superuser.com/questions/727459/changing-current-culture">Changing current culture</a> on SuperUser. The main problem that it doesn't work with Powershell 3.0 and 4.0. </p>
  
  <pre><code>PS C:\users\me\Documents&gt; [system.threading.thread]::currentthread.currentculture
  
  LCID             Name             DisplayName
  ----             ----             -----------
  1049             ru-RU            Русский (Россия)
  
  
  PS C:\users\me\Documents&gt; [system.threading.thread]::currentthread.currentculture=[system.globalization.cultureinfo]"en-US"
  PS C:\users\me\Documents&gt; [system.threading.thread]::currentthread.currentculture
  
  LCID             Name             DisplayName
  ----             ----             -----------
  1049             ru-RU            Русский (Россия)
  </code></pre>
  
  <p>UI culture also does not accept new settings. <code>Set-Culture</code> in total does not work, regardless of whether I'm using admin access or not - anyway, it shouldn't be affected by this, as the effect is only for a single process. The <a href="https://stackoverflow.com/questions/2379514/powershell-formatting-values-in-another-culture/"><code>Using-Culture</code></a> from MSDN Powershell blog, adapted by SO community, works, but only partially, for example, with current culture of "ru-RU" I am able to get proper date from "6/19/15 2:26:02 PM" string, which is in the "en-US" culture via <code>Using-Culture "en-US" {get-date -date "6/19/15 2:26:02 PM"}</code>, but receiving an error in another language is not possible: say <code>Using-Culture "en-US" {$null.test='1'}</code> results in an error with Russian locale, as if the culture was not changed.</p>
  
  <p>This behavior was tested on my local Win7 Professional workstation with Powershell 4.0 installed, and a Windows Server 2012 with Powershell 3.0 installed, which is required to parse wrongly localized date strings. The latter has UI culture of "en-US" and system locale "ru-RU".</p>
  
  <p>So, is changing Powershell session's culture still possible with PS3 and above, and if yes, how? (Or is it bugs again, or change in PS3 that I am not aware of?)</p>