My scenario:
Upon uninstalling Adobe Acrobat 8 *, the file associations, among other things, are broken for PDF files. Repairing the Reader install fixes this. I'd like to have the Reader repair called as the last step of my Acrobat uninstall. Running the msiexec command line from a CA gives an error, as a Windows Installer Process is already running.

Is there a way to repair another MSI's features from a custom action, or to somehow schedule the command to run after the current msiexec exits, without using a vbscript wrapper for the uninstall command?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Andrew,
you need to place the msiexec CA after 'InstallFinalize and add 192 to the type field. Then it should work.
Regards, Nick
Answered 07/03/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment