Skip to main content

Remove previous versions using MSI Upgrade Table

There are several methods to uninstall the existing older versions of an application e.g. Script, MSI upgrade table, SCCM deployment conditions. We are here discussing the method using Upgrade table.

Upgrade table can be used effectively to detect and uninstall the previous versions of a MSI based application provided the upgrade code is known.

Here is an example on populating Upgrade Table:

Locate the UpgradeCode in Property Manager. Remember this could either be same or different in previous version and if it is different then grab the code from previous version.


Go to the Upgrade Table in Direct Editor.

Copy the upgrade code to its column. Populate the Version columns based on requirement (consider all the digits as per previous MSI versions).

Attribute column needs to be configured with appropriate bit flag for corresponding upgrade behavior. Refer to Upgrade Table to calculate the proper bit flag. In example, 768 is the sum of 256+512 which means, detect the range of version including the Versionmin and Versionmax. Then specify an ActionProperty name which will be executed if version detection is successful, here specified as REMOVEOLD.
  
Make sure to append this ActionProperty to SecureCustomProperties filed in the Property Table as shown below.

These configurations will enable the MSI to detect existing previous version and remove it before installing itself.

Author: Dinesh Shilpakar

Labels:

Comments

  1. AnonymousApril 20, 2022 at 5:45 AM

    Remove Previous Versions Using Msi Upgrade Table >>>>> Download Now

    >>>>> Download Full

    Remove Previous Versions Using Msi Upgrade Table >>>>> Download LINK

    >>>>> Download Now

    Remove Previous Versions Using Msi Upgrade Table >>>>> Download Full

    >>>>> Download LINK FV

    ReplyDelete

Post a Comment

Popular posts from this blog

Active Setup Registry Key : What it is and how to create in the package using Admin Studio Install Shield

While launching from Admin account or doing “Run as Admin” it was launching properly but when launched from the standard-user account, though it was launching but GUI was not coming properly and before launching, it throws the error that some particular Skin file is missing. I checked in installation folder and skin file was there but still while launching I was getting the error, but when launched from Admin account or using “Run as admin” it was launching properly with proper GUI and no skin file missing error. On exploring further I found that application was installed by admin account and it created some entries in HKCU, and these entries contain the path and name of skin file to be used. So when we launched the application from Standard user account then these entries were empty in HKCU for Standard user. So to solve this problem while re-packaging I used Active Setup . Active Setup provides a great solution for installing current user data when the package is not installed ...
1 comment
Read more

Active Setup for MSI with no Entry Points

Active setup provides a solution when the aim is to deliver user based components when no advertised entry points exist in an MSI package. Most packages will contain some kind on entry point; commonly an advertised shortcut. When launching this kind of shortcut Windows Installer will check the keypath of the component the shortcut belongs to and verifies that the component is installed. If it is found to be missing Windows Install will kick off a repair. This provides a great solution for installing current user data when the package is not installed in the user context. It is also a very good reason why you should never mix machine and user data in the same feature. So what do you do if there are no shortcuts to advertise? Active Setup will solve the problem. An MSI package has been created to install an Outlook plug-in. This package installs both user and machine data. User preferences are stored as a combination of HKCU registry and a XML file written to %USERPROFILE%. As t...
Post a Comment
Read more