Have you ever had a package that always goes for self heal? If so, here are a few points to check ...
If a key file is found to be missing on launch, Windows Installer will trigger a reinstallation of the parent feature. Having a "clean" package is key.
To find out just what the problem is, look in your Application Event log. Or for more detail, turn on Windows Installer logging and search for the word "error" in the resulting log file (found in %TEMP%).
Some common reasons why this may occur:
Missing Files or Registry Keys
Look closely- some files are deleted by the application itself. If your package contains such a file it will self-heal in order to restore the file each time.
Temporary Files Included In MSI
If any temporary files left on the system are captured in your package, they may cause self repairs to occur in order to restore them.
Correct Path for the components.
Sometimes the component will have a...