I have a custom action that needs to call uninstaller.exe of an application before I install my installation. The application that will be uninstalled is not an msi package. The uninstall of the application can take a minute or two. I want my Custom Action wait for the uninstall to finish and then execute the next action. However, it is not waiting for the completion. Even after my application installation finishes, it takes another 5 or so secs for the uninstaller of the other application.
What can happen many times with these types of installers is that the bootstrap that you reference uninstaller.exe then calls something else to finish the uninstall, but MSI is only monitoring the process uninstaller.exe. This is demonstrated by point 3 in that article referenced. In this event you will likely need to write your own custom action that is in a loop and waits until a certain condition is met. Probably the best way would be to use something like process explorer to manually find out what process is really finishing the uninstall then monitor that process at run time of the install to completion in your C.A.
Hmm that's it.. There was another exe inherited from the exe that I executed. So after I execute that I now check if the inherited exe is finished in another Custom Action.
