Version in Add/Remove programs is wrong - how to change?
What table/property contains the version information that shows up in the Add/Remove programs -> "Click Here for support information"?
I tried finding the wrong version in my MSI but I can't find it (I actually didn't code the MSI, that person is not here anymore).
For example:
It shows up as say version: 6.4.3
But it's really 6.4.5
I only saw one spot for 6.4.3 and I edited it, but it doesn't seem to be the right spot, as it's still showing up "wrong".
I tried finding the wrong version in my MSI but I can't find it (I actually didn't code the MSI, that person is not here anymore).
For example:
It shows up as say version: 6.4.3
But it's really 6.4.5
I only saw one spot for 6.4.3 and I edited it, but it doesn't seem to be the right spot, as it's still showing up "wrong".
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
aogilmor
16 years ago
Posted by:
kjhurni
16 years ago
Posted by:
anonymous_9363
16 years ago
ORIGINAL: kjhurniYour copy must be unique. That's not a restriction I've come across. Even the eval version edits MSIs...
the version of Admin studio I have only makes transforms, not actually editing the .MSI file)
If this is a vendor MSI, you should not be editing it, but using a transform instead. If you're having problems with applying the transform, you would best be advised to ask for advice here, rather than bypassing the issue in a non-recommended way.
Posted by:
kjhurni
16 years ago
It's the ZENworks edition of Admin Studio. It doesn't let you edit MSI files, only make transforms (among several other restrictions).
Even though the transform did have the correct property in it, it would not actually populate that section of the registry properly, so I had to edit the MSI directly.
The vendor actually is the one who messed up and issued a software update and forgot to edit their own MSI to put the updated version in there.
Already been apprised that it's "not supported" but it seems to work fine so far.
Thanks!
Even though the transform did have the correct property in it, it would not actually populate that section of the registry properly, so I had to edit the MSI directly.
The vendor actually is the one who messed up and issued a software update and forgot to edit their own MSI to put the updated version in there.
Already been apprised that it's "not supported" but it seems to work fine so far.
Thanks!
Posted by:
anonymous_9363
16 years ago
Jumping Jehesophats! Get yourself some proper tools! :) Even a freeware tool has to be a better option than a crippleware one, no?
As for the vendor's MSI...is anyone surprised? Irrespective of that, if your solution to a perceived inability of a transform to apply a new property value is to edit the MSI, your packaging career may be short-lived. Applying sticking plaster to a broken leg isn't going to make it heal.
As for the vendor's MSI...is anyone surprised? Irrespective of that, if your solution to a perceived inability of a transform to apply a new property value is to edit the MSI, your packaging career may be short-lived. Applying sticking plaster to a broken leg isn't going to make it heal.
Posted by:
kjhurni
16 years ago
Posted by:
anonymous_9363
16 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.