Windows installer service 2

Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer.

If they are, see your product documentation to complete these steps. Click Start , and then click Search. In the File name box, type Msiexec. After the search is complete, make a note of the location of the Msiexec. On the File menu, click Close to close the Search dialog box. In the Open box, type regedit, and then click OK. In the right pane of the Registry Editor window, double-click ImagePath.

In the Edit String dialog box that appears, make sure that the string in the Value data box contains the correct path for the Msiexec. Note The following is an example of the correct path, where drive is the drive where Windows is installed:.

If the Value data box does not contain the correct path, make changes to correct the path, and then click OK to close the Edit String dialog box. On the File menu, click Exit to quit Registry Editor. Start your computer in Safe mode, and then register the Msiexec. To do this, follow these steps:. Restart your computer and press the F8 key on your keyboard.

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? Report abuse. Details required :. Cancel Submit. Hello Stephen, Thank you for using answers.

Click Start , and then click Run. In the Open box, type cmd , and then click OK. At the command prompt, type msiexec. In some cases, you may also have to add Administrator accounts. How satisfied are you with this reply?