Re: PSAPI.DLL Corrupt?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Nov 14, 10:59 pm, Andrew Martin <andrew.franklin.mar...@xxxxxxxxx>
wrote:
I am running Windows Server 2003sp2 and attempting to install McAfee
Total Protection for Small Business. As I try to install the
firewall component, I get an error:

The procedure entry point GetProcessImageFileNameW could not be
located in the dynamic link library PSAPI.DLL

This error is similar to the behavior of when IE7 tries to launch:

http://support.microsoft.com/kb/932540

This is typically indicative of one of a number of applications that
deploy their own copy of PSAPI.DLL:

(From Hanselman's Blog:http://www.hanselman.com/blog/TheProcedureEntryPointGetProcessImageFi...)
Verizon DSL schmutz
Ergodex Manager for the DX1 Pad
SmartBridge (MotiveSB.exe)
Something else that is distributing an old version of PSAPI.dll

I have none of these applications, nor do I have any other instance of
PSAPI.dll on the server. I've checked the PSAPI.DLL that does exist
in System32, and it fails to re-register:

C:\Windows\system32\psapi.dll was loaded, but the DllRegisterServer
entry point was not gound.

This file can not be registered.

The version I have is 5.2.3790.3959, and I downloaded 5.1.2600.2180
from dlldump.com, but it also results in the same registration error.

Has anyone been able to overcome a similar issue? All of the
suggestions I've found reference the articles I've mentioned above and
do not help with the install issue I'm seeing.

Per this thread:

http://groups.google.com/group/microsoft.public.windows.server.general/browse_frm/thread/c166b414feb2bedb/1c16f49024708894?lnk=gst&q=psapi#1c16f49024708894

Renaming the c:\windows\system32 psapi.dll will result in a new .dll
being generated. It seems that this task creates a "working" dll
until the next reboot. I'm seemingly able to get past the above error
with this workaround.
.

Relevant Pages

  • Re: Python DLL in Windows Folder
    ... with the old DLL. ... the requirement for backwards compatibility is not normative. ... I can install in according to 2.6 is the System folder. ... applications", not "to ensure backward compatibility with the old DLL". ...
    (comp.lang.python)
  • Assembly version compatibility issue
    ... I have a common assembly DLL that's installed into GAC (using msi created by ... It contains classes used by all the applications we have. ... and install the newer DLL properly when it's deployed. ...
    (microsoft.public.dotnet.framework)
  • Assembly version compatibility issue
    ... I have a common assembly DLL that's installed into GAC (using msi created by ... It contains classes used by all the applications we have. ... and install the newer DLL properly when it's deployed. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Assembly version compatibility issue
    ... I have a common assembly DLL that's installed into GAC (using msi created by ... It contains classes used by all the applications we have. ... and install the newer DLL properly when it's deployed. ...
    (microsoft.public.dotnet.languages.csharp)
  • PSAPI.DLL Corrupt?
    ... I am running Windows Server 2003sp2 and attempting to install McAfee ... I have none of these applications, nor do I have any other instance of ... but it also results in the same registration error. ...
    (microsoft.public.windows.server.general)