Behind PowerShell Installer (for Windows XP / Windows Server 2003):

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

Mario Solano — Mon, 21 Jun 2010 17:22:44 GMT

Hi,

I need to run MSPS reports to identify some issues in my servers. The reports use power shell. So, question is, if until I use MSPS reports, is power shell simply there (standing by to be invoked?)

Once I use MSPS reports, will there be any performance issue to the server?

Thanks

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

Doug — Sat, 26 Dec 2009 21:48:43 GMT

I see this problem also after downloading WPK

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

Dood — Thu, 10 Dec 2009 16:06:55 GMT

I'm having the same ISE problem!

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

mhavherhick9 — Wed, 09 Dec 2009 15:08:13 GMT

Any update to Nov 5th posting from Alex?

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

Alex Alas — Thu, 05 Nov 2009 23:39:09 GMT

I am experimenting a problem after installing PowerShell V2 CTP3 and Windows Management Framework Core. Now every time I try to open Powershell ISE, it crashes. In the event log I found the an eventID 5000, Source:.NET Runtime 2.0 Error. Description: EventType clr20r3, P1 powershell_ise.exe, P2 6.1.6949.0, P3 4943044e, P4 mscorlib, P5 2.0.0.0, P6 492b834a, P7 e37, P8 1cd, P9 system.argumentexception, P10 NIL.

I google everywhere for solution but I have not found one yet.

Please advise!

Alex

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

David Williams — Wed, 23 Sep 2009 21:58:00 GMT

Hope this saves people a lot of frustration and time. Reviewing other blogs requesting how to uninstall powershell it has been made abundantly clear that it can't be done cleanly. The silence we hear from the Powershell MVP's on the topic is deafening.

So if you have Server 2003 or 2008 (W2K8) 64 bit or 32 bit and looking for an uninstall process or command line to remove Powershell to update to Powershell V2 CTP3, it’s not going to happen folks. Put down your pomp pomp’s for Powershell and face the fact this command line utility was released to the public way to early and has a long bumpy road before it will be acceptable for public consumption.

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

sarneff — Thu, 05 Feb 2009 19:01:16 GMT

Hi all,

I have a problem after run C:\windows\$NtUninsallKB926139\spuninst\spuninst.exe

All PowerShell dlls are still in GAC(c:\windows\assembly).

I receive multiple error messages for all ddls when I try to remove them from GAC-

"Assembly 'microdoft.powershell.commands.management' could not be uninstalled because it is required by other application"

Could anybody help me?

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

PowerShell Angel — Tue, 18 Nov 2008 02:09:33 GMT

The uninstaller on the disk can be accessed from C:\windows\$NtUninsallKB926139\spuninst\spuninst.exe

Call it and install V2

re: Behind PowerShell Installer (for Windows XP / Windows Server 2003):

Jimaco — Thu, 13 Nov 2008 01:59:40 GMT

Hi I tried to uninstall PowerShell v1.0 on my XP SP3 laptop. Checked Show Updates and selected Remove for the Windows PowerShell entry under Windows XP - Software Updates. The result was that I no longer have an entry for PowerShell in Add/Remove Programs, but everything else (Program Files entry, windowspowershell folder in the %System% directory, HKLM registery keys, and presumably dlls in the GAC) are still there and I still cannot install PowerShell 2.0. I know that by now someone must have developed a script (or some tool) to clean the uninstall up -- how do I get it? :) Thanks!

Sql Server, WMI and PowerShell

Peter's Pattern — Wed, 12 Mar 2008 13:37:18 GMT

So I started out on a quest: a quest for the overview of installed SQL Server instances on my machine.