Windows PowerShell RC2 FAQs

Windows PowerShell RC2 FAQs

  • Comments 8

Since the release of Windows PowerShell RC2, we've been receiving many questions around some of the changes from previous versions of PowerShell to RC2. To help clear up and confusion, I've taken the most common questions I've been hearing and have answered each below.

Q: Which platforms are supported for PowerShell RC2?


PowerShell RC2 is currently available on Windows XP and Windows Server 2003 in both 32bit and 64bit versions. A version of PowerShell for Vista is currently under development.


Q: What languages are supported by PowerShell RC2?


Windows PowerShell RC2 is the first version of PowerShell to be released in all of our final localized languages, namely: Chinese Simplified, Chinese Traditional, German, English, Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), and Russian.


PowerShell is available as both a single localized package in the language of choice, as well as a Multilingual User Interface (MUI) package which can be installed on English MUI-enabled systems to install all PowerShell supported languages simultaneously.


Q: Windows Powershell has disappeared from Add/Remove Programs! How do I remove it?


Windows PowerShell is considered an update to Windows. To display its entry within Add/Remove Programs, you must check the "Display Updates" checkbox at the top of the window.


Q: I'm a software developer and reference the Windows PowerShell assemblies. I cannot find them now. Where are they installed?


For increased performance in RC2, Windows PowerShell now GACs and NGENs its assemblies. These assemblies no longer reside directly on the filesystem, but live inside the GAC. The PowerShell reference assemblies for developers are now packaged as part of the Windows SDK along with the rest of our developer tools and documentation.


Q: Where is Windows PowerShell installed?


Windows PowerShell installs to %systemroot%\system32\WindowsPowerShell\V1.0.


On 64bit machines, Windows PowerShell installs the 64bit executable in %systemroot%\system32\WindowsPowerShell\V1.0 and the 32bit executable in %systemroot%\Syswow64\WindowsPowerShell\V1.0


These changes were done to enable Windows PowerShell to be integrated in with the default OS install at a later date.


Q: Where are the Windows PowerShell Profile files stored?


In a change from RC1, the PowerShell profile files are now stored two locations:


User-specific profiles are now stored in <My Documents>\WindowsPowerShell


Machine-wide profiles are stored in the PowerShell Install Directories (see the answer to the question above). Note that this means you can have separate machine-wide profiles for 32bit and 64bit instances of PowerShell.


Why these locations? I was going to write up a long summary post of our many in depth conversations, but Lee Holmes has helpfully beat me to the punch. You can learn all about the rationale for these changes on his blog:


Hopefully this helps to answer some of the questions you may have had with the recent changes in Windows PowerShell RC2. If you have any additional questions, please post a comment here on the blog.


Leonard Chung

Program Manager - Windows PowerShell & Microsoft Management Console (MMC)

Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post
  • What happened to the make-shell utility? I couldn't find it after installing RC2, and the docs didn't mention it anymore, so I presume it's history?
  • make-shell is now part of the Windows SDK. The Windows PowerShell setup now only contains the bits required for the end-user runtime.

    Leonard Chung

    Program Manager

    Windows PowerShell & Microsoft Management Console

  • Why PowerShell isn't included in Longhorn Server Core OS? Please add PowerShell to Server Core OS.
  • My application invokes powershell scripts via C#, what is needed to deploy that application + powershell functionality to a Windows Server 2003 machine that does not have PowerShell installed?

  • Hi Chris;

    You should consider PowerShell to be a prerequisite to your installation.  If you have control over the machines, you can automatically deploy and install PowerShell.  If you do not have control of the machines, you should direct users to install PowerShell.  Our guidance for that is here:


  • Hi, I upgraded to RC2 and now i can not run scripts .ps1 or .psc1.

    I have ran set-ExecutionPolicy RemoteSigned

    but still no luck. Is it me?

  • > Hi, I upgraded to RC2 and now i can not run scripts .ps1 or .psc1.

    This should work fine.  The Newsgroup is the best way to get help for issues like this (you can post it here but the response rate will be significantly slower).  To answer the question, you need to provide show what you type and what the system response is (as well as the any other commands /command output that illustrate the problem).


    Jeffrey Snover [MSFT]

    Windows PowerShell/MMC Architect

    Visit the Windows PowerShell Team blog at:

    Visit the Windows PowerShell ScriptCenter at:

  • Powershell has disappeared from add/remove programs on my Windows 2003 64-bit server.  Checking "display updates" does not show it, either.  Yet, when I try to re-install it (in response to an issue I am trying to resolve with Microsoft Premier Support) it tells me it is already installed and I must uninstall it before it can be installed.  Any other ideas??


Page 1 of 1 (8 items)