Updated Applcation's MSI DB Retaining Old Component Information After Update

Hi All,

We're seeing an issue where an updated installation is initiating a self repair when an associated file is double clicked.

We thought at first that this might be related to the "advertised shortcuts" setting that is specified by WyUpdate but further investigation revealed that certain files' MSI entries which should have been removed are remaining in the updated application's locally cached MSI. All of the files in the component are dynamically linked and are removed from the file system as expected on update. The problem appears to be that the updated local MSI retains the references to the now removed files.

I was able to locate the component and files in the locally cached updated MSI using installshield's MSISleuth which showed the old file references while completely missing any reference to the replacement file (newer version and different filename). I'll say that we've not had any issues with WyUpdate prior to this so I'm quite puzzled.

1104 Events read like below but that file listed is not part of the new version at all.

Detection of product '{0FCBD505-C501-49C2-AF81-146CE026481D}', feature 'MainApp', component '{1A55C9EB-B9FA-8859-56F3-A7829DA96CEF}' failed. The resource 'C:\Program Files\Actify\SpinFire\11\d3dcompiler_46.dll' does not exist.

So I think the short of it is that our updated application removes some files as expected but the cached MSI is unexpectedly retaining a record of them while a few new files are deployed but are missing from the cached MSI.

Is this something that has ever been seen before?

Thanks in advance for the help -

Michael