[This is preliminary documentation and subject to change.]
Microsoft® Windows® installer can repair, replace, and verify files contained in an application. A partial or complete application reinstallation might be required if any files or registry entries associated with any feature have become corrupted or are missing.
The following list contains several means of reinstalling a feature or product. The first two methods have been automated by the installer.
For more information on reinstalling a feature or application, see Resiliency.
If desired, several Reinstall buttons can be created for a single dialog box, allowing the user to select the type of reinstallation performed. In this case, each button is authored as outlined in the preceding procedure, with a different ReinstallMode ControlEvent parameter for each button.
Once a particular product has been installed (with some or all of the product's features), a reinstallation can be performed on the command line.
Specifying these properties allows the user to reinstall any or all of the product's features. The type of reinstallation can also be specified. For example, you can specify that only those files that are totally missing should be reinstalled, or that only corrupted files (for example, any executable file whose checksum doesn't match the actual file contents) be replaced. Alternatively, you can specify that the fitness of the current installation be verified, without actually repairing any broken or missing files/registry entries. In this case, for all installed features, the installer reports (typically in a log file) the results of any verification that you specify, such as whether there are any missing or corrupt files, any files of the wrong version, or any missing or incorrect registry entries. At any later time, you can then run the installation again to repair any or all of the detected problems.