"Could not load: XXXX.dll" error in log (possibly XP SP3 related)

I've run into an issue where an installer will not work on a machine that was previously "hosed up" by XP SP3. Prior to the botched SP3 install, the computer had the software installed and was working fine. resolving the botched SP3 install involved restoring to a previous restore point (i'm not sure if this was windows restore or a 3rd party restore util) which was also prior to the software being installed.

However, the installer no longer works on this machine.

I've left out all the gory details of the install log, however, normally it goes like this (I have highlighted the file names which I replaced to protect the innocent):

Output folder: C:\Program Files\InstallDirectory\

Extract: File1.exe... 100%

Extract: File2.dll... 100%

Extract: File3.dll... 100%

Extract: File4.exe... 100%

...

Continue on with other files and directorys in the install dir

...

Create folder: C:\Documents and Settings\USER\Start Menu\Programs\ApplicationName

Create shortcut: C:\Documents and Settings\USER\Start Menu\Programs\ApplicationName\Application.lnk

Created uninstaller: C:\Program Files\InstallDirectory\uninst.exe

Registering: C:\Program Files\InstallDirectory\File2.dll

Registering: C:\Program Files\InstallDirectory\File3.dll

Completed

On the machine in question, it goes as follows (fails at the registering stage).

Output folder: C:\Program Files\InstallDirectory\

Extract: File1.exe... 100%

Extract: File2.dll... 100%

Extract: File3.dll... 100%

Extract: File4.exe... 100%

...

Continue on with other files and directorys in the install dir

...

Create folder: C:\Documents and Settings\USER\Start Menu\Programs\ApplicationName

Create shortcut: C:\Documents and Settings\USER\Start Menu\Programs\ApplicationName\Application.lnk

Created uninstaller: C:\Program Files\InstallDirectory\uninst.exe

Could not load: C:\Program Files\InstallDirectory\File2.dll

Could not load: C:\Program Files\InstallDirectory\File3.dll

Completed

Upon checking the Install directory, it is empty which explains the could not load error, however, what could possibly cause the installer to report that it extracted the file but the file not actually get extracted?

Any thoughts/ideas/help would be greatly appreciated...

I realise that the answer I probably am going to get is something along the lines of "reinstall XP" or "no way of knowing what is happening" but if anyone has any other advice, please help.

TIA,

I'll give you both. No way and you need to reinstall XP. No way because it'd tell you if it couldn't extract, so something is probably deleting the files later. And reinstall XP because it fails loading due to missing dependencies.

Re: "Could not load: XXXX.dll" error in log (possibly XP SP3 related)

Originally posted by kinar
I realise that the answer I probably am going to get is something along the lines of "reinstall XP" or "no way of knowing what is happening" but if anyone has any other advice, please help.

Luckily we don't get much that kind of answers around here. 🙂

The first thing that comes to mind is that your AV thinks those files are malware and is removing them, but then you probably should get a warning from the AV.

You could try to run to Filemon. It's a tool from Microsoft to monitor system file activity.

Just use "File2.dll;File3.dll" as Include filter in Filemon and run the installer again. That should tell exactly what's happening to those files.

Edit: Lol kichik! Though you are might be right.

kichik, thanks for the response. As a developer, I certainly appreciate seeing someone else use the "no way in hell that is happening" response (I use it frequently). I'll look into what might possibly be removing them.

Also, {_trueparuex^}, thanks for the suggestion of FileMon. I am familiar with it from back before MS bought sysinternals.

Unfortunately this is not a machine that I can sit down in front of so I may not ever find a solution, but I'll see if I can arrange to remote into the machine on monday and poke around a bit.

I'll make sure to post back here any results.

As usual, it turns out that I got some bad information.

The files are extracted to the installation directory as expected.

The DLL registration failure is being caused by the fact that vcredist_x86 is not properly installing the MFC80 dlls which causes the application dlls to fail registration.

The funny thing about all of this is that while searching the forums prior to posting, I found all 80 million posts about dll registration failing due to missing dependancies but had assumed it wasn't the issue due to the information I had previously been given.

Sometimes it is quite amazing how things work out.

Thanks one last time for the help guys.