Get all installer 4 sources

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. Windows Installer 5. Windows Installer 4.

See the Windows Installer Run-Time Requirements for information about the minimum Windows service pack that is required by a Windows Installer version. Please check off the apps you want above.

Get Your Ninite. Ninite works on Windows 10, 8. Email me at optional when it's ready. Suggest this app Thanks! Ninite Pro has a new web interface. Click here to learn more. Our website is free for home use money-wise, but also free of ads and junkware because Pro users keep Ninite running. Toggle navigation. No clicking next. Just pick your apps and go. Always Up-to-date You don't have to watch for updates.

Multiple package transactionIn a multiple package transaction, you can create a single transaction from multiple packages. In a multiple package transaction, a chainer is used to dynamically include packages in the transaction. If one or more of the packages do not install as expected, you can roll back the installation. This makes a custom UI easier to integrate. Or, you can invoke an embedded UI handler during a Windows Installer repair process.

Embedded chainerYou can use the embedded chainer to add packages to a multiple package transaction. You can use an embedded chainer to enable installation events across multiple packages.

For example, you can enable install-on-demand events, repair events, and uninstall events across multiple packages. Update supersedence resiliencyThis feature lets you correct for changes in the FeatureComponent table during supersedence.

Shared component patching resiliency during uninstallThis feature makes sure that the most recent version of a component is available to all products. Custom action execution on update uninstallThis feature lets an update add or change a custom action so that the custom action is called when an update is uninstalled.

The issues present in earlier versions of Windows Installer that are addressed in Windows Installer 4. This lack hindered any custom actions that needed this user right. Some case-sensitive service-name comparisons in the InstallValidate action resulted in an unnecessary "files in use" message in Windows Vista. When you uninstalled an update that added a new component, the component was also uninstalled. This occurred even if the component was shared by other products.

The following new and improved features have been implemented in Windows Installer 4. Need more help?