I recently updated Photoshop to CS5 and I now have an irritating new startup called Adobe Updater. This thing parks itself in the menu bar and slows down startup, and I cannot find where it lives. It is not in any of the startup folders nor in the user account startup item list. Does anyone know how I can get rid of this thing? I try to keep a lean system and I will check for updates myself, I very much dislike all these programs leaping into action when I startup the machine but for some reason the Adobe updater is not following the rules and is being "clever..."
Does anyone know how I can get rid of this thing and how it insinuates itself into the startup process? I would like to make sure that other applications are also not doing the same thing and running code over which I have no control. It's getting like Windows for all love...
Thanks - Lawrence
Mac SE, PowerBook 140, 2 MacMinis, MacBook Pro 17", 24" iMac and a panic of PCs,
Mac OS X (10.6.2)
Nope. My main concern is how can one insert a startup program into the Mac startup stream outside of the channels that I know about. And I assume it is not inserting this thing into the OS X UNIX boot process. Hence I thought to ask OS X folks first, thinking it would also be quicker.
If the update icon isn't sitting up in the menu bar, open any CS5 app and choose Help > Updates. The same updater dialogue will launch. Click on Preferences at the upper right. Turn off the check box for "Notify me of new updates in the menu bar." Click Done, click Quit.
Unlike CS4 and earlier, this is the only way to check for updates from your computer (without just going to Adobe's site and looking), so remember to launch it every so often to see what's available.
Thanks, yes, I saw that option. What I wonder though is how did this application get started up? I cannot find it in any of the usual startup places. I work with Windows machines as well as OS X and Linux and there are a whole world of mechanisms to get applications going at startup, some of which are fiendishly tricky to identify. Outside of the Unix startup mechanism that Apple employs to get OS X cranked up, there are the system and user Library/Startupitems and then the list of items in the user account. I did not find this Adobe updater in any of those. So how does it get launched?
I did not find this Adobe updater in any of those. So how does it get launched?
Good question. I first looked in the normal places too, and found nothing. Tech Tool Pro also has a self placing icon for the menu bar, which can only be disabled from its System Preferences applet.
Thanks for the quick response. I've checked these and the only slightly relevant thing is a com.adobe.ARM plist in the user LaunchAgents folder. However this appears to be a DRM thing for Acrobat Pro. I've also checked the system list of registered launchd items and found nothing.
Macintosh HD > Library > Application Support > Adobe > Updater (possibly Updater5).
Removing it should do the job, but you'll probably then be irritated by a dialogue box at PS start up saying there are files missing. Don't you just love Adobe?
While this would remove the updater, it doesn't solve the problem of how the update is running on startup. It also potentially wouldn't remove any mechanism that the updater is using to run itself on startup.
Acrobat Reader has or had a similar annoyance, from v8 upwards. The updater app is contained somewhere within the app bundle, as is an install checklist. If the updater doesn't live in /Library/AppSupport, it will be copied as long as the former 2 entities exist. It's been one reason for me to stick with AcroRead v7...
Have a look on the ArsTechnica MacAch — if I remember correctly the exact recipe to get rid of the updater AND of the self-repair is still online there.
Do a search for updater.app and you find that there's one inside Adobe Reader and I suspect any other Adobe product. What's triggering it? I haven't the faintest, but I've disabled it by removing the updater app from all Application Support folders. As others pointed out, contact Adobe, it's their mucked up apps causing the problem.