Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Failed to install PSFSIP Error 0x80004005: Unspecified error

128 views
Skip to first unread message

MikeB

unread,
Mar 12, 2008, 5:28:02 PM3/12/08
to
Here is the scenario. SQL server was uninstalled from the server not
realizing that WSUS was in use there. I thought MSDE version was the one
being used but apparently it was SQL server. I am trying to reinstall WSUS
server but continue to get Failed to install PSFSIP Error 0x80004005:
Unspecified error.

I can't seem to find what is the cause of this issue. Anyone know of a fix.
I've uninstalled all the .NET stuff and re-installed it.

What is PSFSIP anyway?
Any help would be appreciated.

I've pasted the log in below.

2008-03-12 13:57:25 Success MWUSSetup WSUS Server Setup Started.
2008-03-12 13:57:25 Success MWUSSetup Parsing command line
arguments
2008-03-12 13:57:25 Success MWUSSetup WSUS Setup: Performing
Install
2008-03-12 13:57:26 Success MWUSSetup Validating pre-requisites
2008-03-12 13:57:27 Success MWUSSetup .Net framework SP1 is
detected on this machine
2008-03-12 13:57:27 Success MWUSSetup Creating WSUS registry key
2008-03-12 13:57:27 Success MWUSSetup Initializing installation
details
2008-03-12 13:57:27 Success MWUSSetup Initializing wizard
2008-03-12 13:57:31 Success MWUSSetup No SQL instances found
2008-03-12 13:57:50 Success MWUSSetup Installing ASP.Net
2008-03-12 13:58:02 Success MWUSSetup Asp.Net is installed
successfully
2008-03-12 13:58:02 Success MWUSSetup ASP.Net is installed
successfully
2008-03-12 13:58:02 Success MWUSSetup MSXML2 is already
installed on this machine
2008-03-12 13:58:03 Success MWUSSetup Installing WMSDE
2008-03-12 13:58:54 Success MWUSSetup WMSDE Installed Successfully
2008-03-12 13:58:55 Success MWUSSetup WMSDE is installed
successfully
2008-03-12 13:58:55 Success MWUSSetup Initializing MWUS
installation
2008-03-12 13:58:55 Success MWUSSetup Installing PSFSIP
2008-03-12 13:58:55 Success MWUSSetup VerInstallFile return
code: 7
2008-03-12 13:58:55 Error MWUSSetup Failed to install PSFSIP
(Error 0x80004005: Unspecified error)
2008-03-12 13:58:55 Error MWUSSetup InstallPSFSIP failed
(Error 0x80004005: Unspecified error)
2008-03-12 13:58:55 Error MWUSSetup Installation of PSFSIP
failed (Error 0x80004005: Unspecified error)
2008-03-12 13:58:55 Error MWUSSetup PerformInstall failed
(Error 0x80004005: Unspecified error)
2008-03-12 13:58:55 Success MWUSSetup Rolling back Installation
2008-03-12 13:58:55 Success MWUSSetup WSUS Server installation
failed. You can look at C:\Program Files\Update
Services\LogFiles\WSUSSetup_080312_1357.log file to determine the cause of
the failure
2008-03-12 13:59:15 Success MWUSSetup WMSDE Uninstall Succeeded
2008-03-12 13:59:15 Error MWUSSetup Failed to copy
Setup\UninstallHelper.exe to
C:\DOCUME~1\username~1\LOCALS~1\Temp\1\UninstallHelper.exe (Error 0x80070003:
The system cannot find the path specified.)
2008-03-12 13:59:16 Success MWUSSetup Insert string: %1 For more
information, see the Setup log "%2".
2008-03-12 13:59:16 Success MWUSSetup szErrorType: Microsoft
Windows Server Update Services could not install PSFSIP.
2008-03-12 13:59:16 Success MWUSSetup ErrorLog: C:\Program
Files\Update Services\LogFiles\WSUSSetup_080312_1357.log
2008-03-12 13:59:16 Success MWUSSetup StringObtained: Microsoft
Windows Server Update Services could not install PSFSIP. For more
information, see the Setup log "C:\Program Files\Update
Services\LogFiles\WSUSSetup_080312_1357.log".

MikeB

unread,
Mar 12, 2008, 5:38:07 PM3/12/08
to
I also tried to unregister the psfsip dll

1. regsvr32 /u psfsip.dll
2. rename psfsip.dll in %windir%\system32 to OLD-psfsip.dll
3. Try to re-install.

didn't work.
Source:
http://forums.techarena.in/showthread.php?t=233601

Lawrence Garvin [MVP]

unread,
Mar 12, 2008, 7:46:22 PM3/12/08
to
"MikeB" <Mi...@discussions.microsoft.com> wrote in message
news:024303FC-DA73-4D74...@microsoft.com...

> Here is the scenario. SQL server was uninstalled from the server not
> realizing that WSUS was in use there.

Given this situation, I'd guess that your WSUS is all confused.

I'd start by :
[a] Uninstalling WSUS including the database (you can keep the content).
[b] Ensuring your SQL Server installation is fully uninstalled.
[c] Double check that there are no vestiges of any WSUS or SQL Server
installation left on the machine.
[d] Run the MSI Cleanup Tool and a Registry Cleaner (or manually search
for the WSUS and SQL Server keys in the HKLM hive).
[e] Triple check that there are no vestigates of any WSUS or SQL Server
installation left on the machine.
[f] Reboot the system.
[g] Reinstall WSUS from scratch.

> I am trying to reinstall WSUS
> server but continue to get Failed to install PSFSIP Error 0x80004005:

The two known (suspected?) causes of this error are:
[a] The file is registered, but doesn't exist in the location WSUS
expects to find it.
[b] The file is registered, but is the wrong version.

In either case, unregistering and renaming the file should resolve the
issue; unfortunately, most of the people who have encountered this issue,
have never posted back with any commentary on the success/failure of this
issue.

> I've uninstalled all the .NET stuff and re-installed it.

Hopefully you uninstalled all of the =application= software that uses .NET,
or uninstalling the underlying .NET Framework might have just complicated
the problem.

> What is PSFSIP anyway?

http://www.fileproperties.com/default.aspx?id=26328&filename=psfsip.dll

It's the "Crypto SIP" provider for signing and verifying *.PSF files (Patch
Storage Files).


--
Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

MikeB

unread,
Mar 13, 2008, 5:58:01 PM3/13/08
to
Thanks for the help Lawrence but noting i've done has worked. I am in the
process of a new server build and reload of WSUS. I tried cleaning the
registy and just about everything else i could think of or find on other
newsgroups and have had no luck. Just didn't want to spend anymore time with
it.

thanks again.

MikeB

unread,
Mar 13, 2008, 5:58:03 PM3/13/08
to

MikeB

unread,
Mar 20, 2008, 4:29:01 PM3/20/08
to
Ok, i finally opened a call on this with M$. it ended up being a .NET
framework issue and I was able to get a .net 2 framework cleaner tool from
the tech. It was called simply cleanup_tool.exe. Google search it and you'll
find it

She ran it about 3 times and then we rebooted and reinstalled

If it fails again go to start and run. type in microsoft.net and it will
open a folder. delete the the v2 .net stuff from the framework folder and try
again .net installs again. Eventually WSUS did install after some cleanup of
the .net stuff.

I hope this will help other people resolve some issues with .net and WSUS
playing together.

Mike

Lawrence Garvin [MVP]

unread,
Mar 20, 2008, 9:16:33 PM3/20/08
to
"MikeB" <Mi...@discussions.microsoft.com> wrote in message
news:61B46FF1-8B4B-4873...@microsoft.com...

> Ok, i finally opened a call on this with M$. it ended up being a .NET
> framework issue and I was able to get a .net 2 framework cleaner tool from
> the tech. It was called simply cleanup_tool.exe. Google search it and
> you'll
> find it
>
> She ran it about 3 times and then we rebooted and reinstalled
>
> If it fails again go to start and run. type in microsoft.net and it will
> open a folder. delete the the v2 .net stuff from the framework folder and
> try
> again .net installs again. Eventually WSUS did install after some cleanup
> of
> the .net stuff.
>
> I hope this will help other people resolve some issues with .net and WSUS
> playing together.

Thanks for the postback Mike!

This is, interestingly enough, the =first= feedback in over two years we've
ever received in this group concerning actual resolution of the PSFSIP error
other than the unregister/rename solutions previously presented (which have
never, to my knowledge, been confirmed as a functional solution).

I've pocketed the .NET Framework cleanup tool in my bag of tricks.

0 new messages