Windows® Installer is needed for the installation, maintenance and removal of software on Microsoft® Windows® systems. It is much improved from its predecessor, Setup API.

New Features in Windows® Installer 3.1

Windows® Installer 3.1 has many new and improved features than its predecessor. These are as follows:

1. New minor Update Target RTM Property
  • Because of this feature target of patch files has been modified. Now, patch files has the capability to target both the original release baseline and the latest service-pack-level baseline present on the system.
2. New Msi Set External UI Record API
  • This feature has change the mode of receiving messages.
  • Packages which are using an external user interface will now receive messages as records rather of receiving the messages as strings.
3. New x64 and Msix64 properties
  • Due to this feature packages can exhibit x64 processor-based operating system support, by using the x64 and Msix64 properties.
4. New MsiNotifySidChange API
  • This API will help you in upgrading Windows® Installer configuration, if the security identifier (SID) of a user is changed.
  • Flyweight patching is now an opt-in behavior, Windows® Installer 3.0 had introduced new flyweight patching functionality.
  • You can enable this by setting the OptimizedInstallMode property in the MsiPatchMetaData table.

Windows® Installer 3.1 is much improved as compared to its predecessor and Windows® Installer help is also improved, to facilitate users.

Solved issues

Several issues, which were faced by the users in the past and can are now solved with Windows® Installer 3.1 are as follows:

  • Null characters when used in a registry value marker or in a service dependency are now logged correctly by Windows® Installer.
  • For very large unversioned files like of 2 GB, MsiGetFileHash function will work correctly.
  • The MediaSrcProp property of a patch has been modified. It is now arranged with the original launched-from location when the patch is installed. But previously it was set to the cached patch location for later transactions. If the package installs more than 2GB of files, then in this situation progress bar will work in a correct way.
  • Now, patching of isolated components will work.
  • Those custom actions which are marked as asynchronous will not be skipped by it.
  • It will now send INSTALLSTART_ACTIONSTART message for all actions. While administrative image patching will be going on, patch sequencer no longer incorrectly rejects a valid patch.

Windows® Installer Help available in the market

Windows Installer help is provided by Microsoft® so that users should not face any problem in the installation, upgradation or removal of Windows® Installer comfortably. You can take assistance from Windows Installer help, if you encountered with some issues while utilizing Windows® Installer.

Otherwise, what you can do is seek technical assistance from some of the tech organizations.We have all the necessary requisites, i.e. experience, resources, technology and tools to render effective Windows Installer Help.