I have the same issue except the exe I want to run is installed by a chained MSI installer. I can't figure out how to run the .exe during uninstall before the file itself gets removed. Again, since the file is installed with the chained MSI, I don't have the option to put it in the Support Files. Any ideas? ... View more

I've run into the same issue. I put the dynamically linked files in the RemoveFile table but InstallShield still gives me the error that they are missing. I've seen the Microsoft documentation for the RemoveFile table, but still no luck. Maybe someone here can help: Here's what I've done-- FileKey: The file as referenced in the log file (e.g. _129A200AD62618DB481DBCCD01EF6E5B) Component: The component as listed in the second column of the File table (e.g. _C1CEA82291ADCF15B1DA8EB13A805C21) FileName: The file name as listed in the third column of the File table (e.g. ludlow.tfw) DirProperty: The directory as listed in the third column of the component table (e.g. _65D192058DA9487E94DC4D605CE4ED8B) InstallMode: 3 Any help would be greatly appreciated. -Clark ... View more

Messing with the merge modules created all sorts of problems for me that I just abandoned it altogether. I now include the Microsoft run time libraries as an exe and run it as a prerequisite with conditions to check if it's been installed on the target machine or not. ... View more

I attached my log, if it helps you Michael. Does anything stand out? ... View more

Thanks for the heads up. On a related note, the feature prerequisite I'm running uninstalls a program. It calls a simple program that takes the uninstall string of the program to be uninstalled from the registry and passes it as a command line argument. Now that I'm able to store the registry value in a property and access it, the installer ends once the "uninstall program x" feature prerequisite finishes. Any clue what might be happening here? -Clark ... View more

So how would I access the property in the command line of a feature prerequisite: [PROPERTY]? Clark ... View more

I just tested my theory and it didn't work. I changed the key file by adding a duplicate component so that the default key file would get changed to Program.exe1 as opposed to Program.exe. I still ended up with the same problem as before. ... View more

I keep running into this issue as well-- running a major upgrade that leaves files out because they are marked as disallowed before the installer knows everything will be uninstalled. I wonder if there's a way to change the file key while keeping the filename the same. Windows installer documentation says "If the installer finds a file with the same name as the component's key file installed on the target location, it compares the version, date, and language of the two key files and uses file versioning rules to determine whether to install the component provided by the package." If I could change the key file, and keep the filename the same, wouldn't that let me bypass the comparison? I don't know much about key files, but the logic makes sense to me. Does anyone know if this is possible or how to do it? Clark ... View more

Same issue here. ... View more

I guess I didn't address your other questions... I saw the Microsoft KB article you linked to, but it seems this refers to an error with Office XP service pack 1. At any rate, I don't believe the file to be patched had changed relative to the new file because I was testing on a Virtual Machine and would run the patch immediately after installing the previous full version. If I remember correctly, running the patch as a full installation did work. Like I said, the problem is fixed now, so I don't even think I have the bad patch file stored anywhere to test with. Thanks for your response. Clark ... View more