6/20/2023 0 Comments Uninstalling adobe updater![]() ![]() And there’s no guarantee that you’ll be able to fix every uninstall problem with this approach. Yes, you can follow my example and edit XML files to fix things, but this is a never-ending chore, as more and more items are updated, you’ll potentially have to make more and more edits over time. This points out yet another major flaw in Adobe’s enterprise deployment toolkit – it can’t adapt to changes post-install. I suspect now that instead of removing the reference to the Adobe Update Manager in the AdobeUberUninstall.xml files, I could have possibly edited a payload xml file to get this working. If I edit the script to test for version “9.3.1”, AdobeUberUninstaller now successfully removes the CS4 Suite. After we’re fully updated, Acrobat Pro’s version is “9.3.1”, and so the test fails. The script is checking for an application with the identifier “”, and only for versions “9.0.0” and “9.1.0”. Looking at this script, it’s obvious what the problem is. Toward the end of that file is an embedded script named “IsInstalledScript”: In the install media that AdobeUberUninstaller.xml references, in payloads/AdobeAcrobat9Core-mul, is a file named. I wanted to figure out why the AdobeUberUninstaller thought that Acrobat Pro was not installed. More frustrating was that the Uninstaller(s) that Adobe puts on the machine in /Applications/Utilities/Adobe Installers/ worked just fine – they’d uninstall the products even when the AdobeUberUninstaller failed. I noticed that if I installed one of the suites, but didn’t update Acrobat Pro at all, the uninstall would complete successfully. The CS Suites still gave me issues on uninstall, though, complaining that Adobe Acrobat Pro was not installed, when it absolutely was. This got uninstalls of Photoshop, Illustrator and After Effects working again, with the downside that the Adobe Updater was left behind. I ignored the warning and edited the AdobeUberUninstaller.xml, removing the reference to Adobe Update Manager. When you uninstall your software silently, the install.xml file and uninstall.xml you use MUST match each other or the process will fail. I decided it wasn’t vital that an uninstall remove the Adobe Updater from /Applications/Utilities, so I ignored this warning from Adobe: To me it seems idiotic that an uninstaller would throw a fatal error when it’s asked to uninstall something and finds it’s not installed, but in this case, it’s probably for the best, as I would have just been puzzled that the uninstaller claimed that it completed successfully, but had left the Updater behind. The first problem I saw when trying to remove an updated Photoshop CS4 was it claimed it could not uninstall because it thought the Adobe Updater was not installed, even though it was. If you poke through the log files in /Library/Logs/Adobe/Installers, you might be able to get some clues why. But if you update CS4 products in your install, a later removal will probably fail with the dreaded “Exit Code 7 – Unable to complete the silent workflow”. If you install a CS4 product and then immediately remove it, it generally works as you’d expect. I can apply updates to the apps and suites, including updating Acrobat Pro all the way to 9.3.1 – all in an automated fashion, without user intervention.Īdobe’s tools and documentation have you create the XML file for uninstall at the same time you are creating the XML file for the install. I’ve since been able to (mostly) wrestle it into submission, and can install several of the CS4 Suites and several of the CS4 standalone apps. I’ve previously posted about my issues with the Adobe CS4 Deployment Toolkit. ![]()
0 Comments
Leave a Reply. |