Adobe Reader and Acrobat 8.1.2 SU1 security update
Adobe's latest security update is now supplied as a MSI. It uses a bunch of Custom Actions to handle the patching of qualifying products (Acrobat Reader, Acro Standard/Pro/3D, vers 8.1.2).
Details and how to check its installed: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403742&sliceId=1
Anyway, its easy to install:
But not so easy to uninstall!
It has its own product code but ties itself as a child to the Product it updates. You'll see it as such in Add/Remove if you check "Show Updates" (XP) and in the HKCR\Installer regsubtree as "{AC76BA86-7AD7-1033-7B44-A81200000003}_Adobe Reader 8.1.2".
Trying the UninstallString regkey that WindowsInstaller sets: "msiexec /x{6846389C-BAC0-4374-808E-B120F86AF5D7}"
gives the "...only valid for installed products.." error. This is due to how it registers itself above I presume.
Messing with the NoModify and ARPsysComp keys wont help, you can enable the Remove option but after a ARP refresh its still there (since it runs the same /x cmd above anyways).
So it looks like the only backout solution (which the company requires) is to uninstall/reinstall the FULL Acrobat product you are updating?
Can anyone confirm they find the same, or am I missing something?
Details and how to check its installed: http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403742&sliceId=1
Anyway, its easy to install:
msiexec /i AcrobatReaderUpd812_SU1_all.msi /qnBut not so easy to uninstall!
It has its own product code but ties itself as a child to the Product it updates. You'll see it as such in Add/Remove if you check "Show Updates" (XP) and in the HKCR\Installer regsubtree as "{AC76BA86-7AD7-1033-7B44-A81200000003}_Adobe Reader 8.1.2".
Trying the UninstallString regkey that WindowsInstaller sets: "msiexec /x{6846389C-BAC0-4374-808E-B120F86AF5D7}"
gives the "...only valid for installed products.." error. This is due to how it registers itself above I presume.
Messing with the NoModify and ARPsysComp keys wont help, you can enable the Remove option but after a ARP refresh its still there (since it runs the same /x cmd above anyways).
So it looks like the only backout solution (which the company requires) is to uninstall/reinstall the FULL Acrobat product you are updating?
Can anyone confirm they find the same, or am I missing something?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jmcfadyen
15 years ago
doesnt surprise me being they have a long history of doing stupid things in their msi's.
Posted by:
rakesh.kumar
15 years ago
Delete the Condition NEVER for PublishProduct in InstallExecuteSequence Table, it will become as normal .msi, means you can uninstall
Regards
Rakesh Kumar
Regards
Rakesh Kumar
Posted by:
R3N3GAD3
15 years ago
Hello Rakesh Kumar,
I tried doing this (modifying the MSI) and it doesn't seem to work. It appears to run through the install, but the update isn't actually deleted. Is there something else I can try?
Thanks!
I tried doing this (modifying the MSI) and it doesn't seem to work. It appears to run through the install, but the update isn't actually deleted. Is there something else I can try?
Thanks!
Posted by:
makelley
15 years ago
The update states in the ARP that it is not removable. In order to remove, you will have to uninstall 8.1.2 and then reinstall the orgional package WITHOUT the update.[8D]
Posted by:
nheim
15 years ago
Hi folks,
this update uses indeed some questionable approaches.
However, i have seen much worser things from Adobe and other vendors.
It will be uninstalled, with the main (8.12) installation of Reader/Acrobat, as it transforms the main package for it.
This update does just two things:
1. It exchanges the file "Annots.api" against a newer version.
2. It puts the following registry key under: "HKLM\SOFTWARE\Adobe\Acrobat Reader\8.0\Installer"
VersionSU=1
Therefore, this could be easy integrated on a administrative install point.
Regards, Nick
this update uses indeed some questionable approaches.
However, i have seen much worser things from Adobe and other vendors.
It will be uninstalled, with the main (8.12) installation of Reader/Acrobat, as it transforms the main package for it.
This update does just two things:
1. It exchanges the file "Annots.api" against a newer version.
2. It puts the following registry key under: "HKLM\SOFTWARE\Adobe\Acrobat Reader\8.0\Installer"
VersionSU=1
Therefore, this could be easy integrated on a administrative install point.
Regards, Nick
Posted by:
aPacker
15 years ago
Thanks for the responses.
Rakesh - you probably mean RegisterProduct (PublishProd is more to do with advertising). In any case that action is in there and not conditioned, but registers the prod under the parent app, so doesnt work.
Thinking about it more, there is no point trying to make an uninstall work since the patch is handled by Custom Actions and there are no specific uninstall CAs so its not like it will 'unpatch' Acrobat anyway!
So unless we deconstruct each update (yuck, dont.) or update an AIP (if we use those, ta Nick), then the backout is uninstall/reinstall main prod.
Cheers all,
Craig.
Rakesh - you probably mean RegisterProduct (PublishProd is more to do with advertising). In any case that action is in there and not conditioned, but registers the prod under the parent app, so doesnt work.
Thinking about it more, there is no point trying to make an uninstall work since the patch is handled by Custom Actions and there are no specific uninstall CAs so its not like it will 'unpatch' Acrobat anyway!
So unless we deconstruct each update (yuck, dont.) or update an AIP (if we use those, ta Nick), then the backout is uninstall/reinstall main prod.
Cheers all,
Craig.
Posted by:
rakesh.kumar
15 years ago
I created .mst and i changed only two things Deleted ARPSYSTEMCOMPONENT from Property Table and removed condition for PublishProduct , I was able to uninstall it
Regards
Rakesh Kumar
Regards
Rakesh Kumar
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.