Avoid patching administrative installations.

Do not distribute unserviceable merge modules.

Reduce the dependency of updates upon the original sources.

Plan and test a servicing strategy before shipping the application.

Test packages for both per-user and per-machine installation deployment.

Uninstallation leaves the user's computer in a clean state.Enable verbose logging on user's computer when troubleshooting deployment.Keep the original package source files secure and available to users.Enable the DisableMedia policy to limit unauthorized installation.Avoid using the AlwaysInstallElevated policy.Provide the option to install without a user interface.Do not use the SelfReg and TypeLib tables.Keep package names and package codes consistent.If you use assemblies, follow good assembly practices.If you use custom actions, follow good custom action practices.Reduce the size of large Windows Installer packages.Organize the installation of your application around components.Use the API to retrieve Windows Installer configuration information.

Do not depend upon non-critical resources.Do not try to replace protected resources.If you decide to repackage a legacy setup application, follow good repackaging practices.Update your Windows Installer development tools and documentation.Meet the Windows Logo certification requirements.This section enumerates a list of tips, linked to the main Windows Installer SDK documentation, to help Application Developers, Setup Authors, IT Professionals, and Infrastructure Developers discover best practices for using the Windows Installer:

The best uninstaller for windows