Uninstall old programversion when installing new programversion, with msi
I am trying
to create an Uninstall with my install.msi which I am editing with Orca. I
would like to uninstall programversion 7.01 and install version 7.1. Under the
Table "Upgrade" I have
"UpgradeCode"
set to the Windows Installer Code ,
"Attributes"
set to 4 (read this but dont know why 4)
"ActionProperty"
set to ActionProperty
For the
rest of them I have no values at all set
("VersionMin", "VersionMax", "Language",
"Remove".
Then I went
to Table Property and added the
"Property"
SecureCustomTransform
with the
"Value"
ActionProperty.
I saved the
msi and ran
msiexec /i
Install.msi /qn
but nothing
happened. I had programversion 7.01
installed and I want it uninstalled and ver 7.1 installed.
I guess I
need to add more values somewhere.
Grateful
for any tips at all.
Thanks!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
dedenker
10 years ago
Did you set different product code, but same update code?
attribute I always set to 769 (from Microsoft side) seems to work best with major upgrade.
and actionproperty set to UPDATE (also from the website)
Microsoft tech page
attribute I always set to 769 (from Microsoft side) seems to work best with major upgrade.
and actionproperty set to UPDATE (also from the website)
Microsoft tech page
Comments:
-
As the updatecode I took the Windows Installer Code from the install.msi package.
What do you mean with product code and where should it be set?
Attribute 769 ( i cant find info regarding this in your linked tech page) what does it do/mean?
I will change actionproperty to UPDATE , ( i cant find info regarding this in your linked tech page) what does it do/mean?
Thanks! - Rain 10 years ago-
Every MSI has product code (this is also used if you want to uninstall) and an upgrade code.
Both are on the "Property" table.
The 769 is a combination of the features:
msidbUpgradeAttributesMigrateFeatures
msidbUpgradeAttributesVersionMinInclusive
msidbUpgradeAttributesVersionMaxInclusive
But 4 should work as well. - dedenker 10 years ago-
Ok. I will use 769.
Neither the product code, the upgrade code or the old msi (teh one I want to uninstall) works when I use them under Table-Upgrade.
Can you write an exampleview of Table-Upgrade and Table-Property?I cant find the error on why the edited msifile won´t work. Perhasp it is because EndNote has the same WindowsInstaller-iD regardless of versionupdate within version 7. - Rain 10 years ago
Posted by:
dedenker
10 years ago
Old msi (to be removed): New msi (that will remove old):
Product code: 1234 Product code: 5678
Upgrade code: ABCD Upgrade code: ABCD
Version: 1.0 Version 1.1
And in the Upgrade table of the new MSI:
UpgradeCode Column: ABCD
VersionMin: 1.0
Attribute: 769
ActionProperty: UPGRADE
Product code: 1234 Product code: 5678
Upgrade code: ABCD Upgrade code: ABCD
Version: 1.0 Version 1.1
And in the Upgrade table of the new MSI:
UpgradeCode Column: ABCD
VersionMin: 1.0
Attribute: 769
ActionProperty: UPGRADE
Comments:
-
Good examples. Sadly it does not work when I run the msi. Probably because the Product Code is the same in old msi and new. I do not know why the product codes (windows installer id) are the same for old and new versions of EndNote X7. I I will try this on other programupdate than EndNote. This is the only program I have been in contact with that has the same product code for all versions 7.x. Would have been nice to use this on EndNote though.
Besides the example above should I have “SecureCustomTransform” set to UPGRADE (Property Table) ? I tried both with and without. - Rain 10 years ago-
Thank you. And strange if both product code are the same means for windows it is the same product.
But I did already see many times, a vendor just re-uses the MSI and thus making very ucly and/or messed up installations...
You can always adjust the original MSI with a MST. - dedenker 10 years ago-
I usually use mst but I would like to be able to keep the uninstall msi in the install msi so it installs the new version wheterornot the old is installed. And so I dont get an error (red)in SCCM 2012 monitoring tool.
I´ll have to try this later on with versions with two different productcodes. If you get more info on how to solve this please get back to me in this forum. Thanks! - Rain 10 years ago
