DLL not registering -- Win7

[linder]

Chris,



You are not allowed to replace "expsrv.dll" because it is a file covered by Windows File Protection (WFP). OS Protected version is: 6.0.72.9589. You may need to update the operating system for this program to work correctly with package version: 6.0.72.9590. In other words, only a Windows update can replace this file. It shows as pending because the installer tried to overwrite it but it was locked (protected). Then Windows rebooted, replaced the file but WFP restored it to its original version.

Does this help?

Friedrich

[Chris]

I do not understand (yet) what is happening, but I have sorted out the original problem.

I've removed any mention of expsrv.dll from SB8 Install script. And deleted the Registry entry for PendingFileRenameOperations.
Then install again. This puts expsrv.dll back into the Pending... in the registry.
Also vbajet32.dll which is dependent on expsrv.dll.
Neither of these is mentioned in the install script so I do not know why they get put into the Registry as tmp files waiting to be renamed; every time I run the install.

Not a SB problem, but if you have any thoughts I'll be interested.

Thanks for the assistance and useful comments in this thread.

[linder]

Chris,

If you check the compiler .htm file, do you see any reference to expsrv.dll?

And do you install any "external" runtime component (e.g. a MS redistributable) from the installer?

Friedrich

[Chris]

>> Windows File Protection (WFP).........
>> only a Windows update can replace this file. It shows as pending because the installer tried to overwrite it but it was locked (protected). Then Windows rebooted, replaced the file but WFP restored it to its original version.

Many thanks. I think that explains all the odd and different results I've found on various computers and operating systems.

[linder]

You are welcome

Friedrich

[Chris]

One last question on this subject, sorry :-)

>> It shows as pending because the installer tried to overwrite it but it was locked (protected). Then Windows rebooted, replaced the file but WFP restored it to its original version.

Does this mean that every time any software is installed in future, the OS will give the message "The System needs to be restarted...." because that pending file will never be cleared??

(and if so, should I try to do anything about it?)

[linder]

"The System needs to be restarted...." is only displayed if your install replaced a locked/in-use file. This creates a new pending action. If the previous pending action was not cleared (e.g. system not rebooted) and the installer was able to replace the file (because something removed the "lock" state) then the install will not request a reboot even when there is still a reboot pending.

Friedrich

[Chris]

In my case the Pending action can never be cleared because it is trying to replace a protected file so will always fail.

So I presume the Pending action will still be there after future restarts?
And therefore future installs will see this Pending action, and suggest restart??

(some installers check for pending items Before starting install, and suggest user restarts first to clear the pending item).

IF the above is all true, then should I try and clear the Registry Pending item?

[linder]

The reboot "should" clear the pending file rename action. Windows deletes the old file, moves the new file from the temporary location to the target location (this removes the registry entry), WFP detects the file change and a rollback to the original file is triggert. So after the reboot, the registry entry "should" be gone. It is not advised to manipulate the pending rename registry on your own. It's very well possible that other programs or a windows update added items.

Friedrich