How do I Uninstall PowerShell 2.0 to upgrade Windows 2003 or 2003 R2 to Windows 2008? $KB968930 folder is empty

Hello, I have several Windows 2003 or Windows 2003 R2 servers that need to be upgraded to Windows 2008. I have opened PowerShell on the server and determined that it is version 2.0. The install will not run until PowerShell 2.0 is uninstalled. However the Add/Remove Programs method to uninstall Windows Management Framework Core fails. The error: it has already been uninstalled. The uninstall file folder $NtUninstallKB968930$ is empty. How do I uninstall PowerShell 2.0? Is there a manual uninstall process? Thank you, Charisse Benson



Have you tried re-installing the update so that the uninstall folder has been reinstated?

I have not found a manual process of uninstalling the powershell.



Have you tried re-installing the update so that the uninstall folder has been reinstated?

I have not found a manual process of uninstalling the powershell.



Hello Peter , I did try to re-install the update and received an error that it was already installed. Thank you.



Hi,

I believe that the server has got SP2 installed? if so, the uninstall order would be;

Control Panel -> Add/Remove Programs -> "Service Pack 2"

Control Panel -> Add/Remove Programs -> Click the "Show Updates" Tickbox -> Locate "windows management framework core"

Once both updates are uninstalled, rename the below folders;

Server 2003 32 bit: %windir%System32WindowsPowerShell

Server 2003 64 bit: %windir%Syswow64WindowsPowerShell

Try the upgrade now and you will be good to go.



Hello,
The server was installed with SP2 in the install process. Is there someway to delete keys in the registry to manually uninstall PowerShell? Thank you.



Hi,

Unfortunately there isn't a specific registry location for powershell as it's spanned with several locations. Take a full backup of registry (ofcource data as well) and search for powershell entries in registry and delete them all. It's definitely not a recommended procedure but seems no other options.

Share this

Related Posts

There was an error in this gadget