I\'m sure this is fairly easy, but I\'ve kind of had a hard time with it. I\'ve got a custom action that executes a different (non-msi) installer on installation. Unfortunat
A condition on the custom action, probably with a matching custom action to do the uninstall. Not sure what tools you're using, but assuming the secondary install is tied to a component, I would use that component state. A state of =3 means a target state of installed. A state = 2 means a target state of absent. Note that the state won't be set if there is no change.