CS6 Mac Updater Failed - How I fixed it
Installed a fresh CS6 Production Premium on a freshly installed 10.7.8 OSX laptop. After the install, went to Photoshop, Updates and it brought up the Adobe Application Manager. Checked off all the boxes and every install failed after a lengthy download period.
Uninstalled, reboot, reinstalled, same thing. Downloaded the new AAM, same problem. This is no mean feat considering each uninstall and download attempt takes over an hour. I did not want to manually download all the app updaters.
Errors reported were worded differently depending on the AAM version:
Another instance of deployment is already running. Error Code: U44M1I11
Sorry! Adobe patch installer doesn't seem to be running
Solution was archiac. Apparently the AAM forks out another install process for the root user when I start it up. So the updates fail because my local user and the root user are both running the updater application at the same time. No idea why it would do this as the local user is also the admin. Baffling behavior, Adobe, truly baffling.
I had to enable the root user, give it a password, then open up a Terminal session. I used su to become root. Then I had to navigate to:
/Library/Application Support/Adobe/OOBE/PDApp/Core and execute ./PDApp.app
At that point, it was running the AAM as root, and I still had to login as myself to the Adobe.com website for it to properly check for updates. Again, baffling and annoying. But it found the updates and installed them after several hours of screwing around.
Finally I have to remember to go in and disable the root user for security purposes. Oh yeah, every time there's a new update available, I have to go through all these steps again.
Adobe: Pretty tired of this and the lack of any KB articles or assistance in these forums. Finally google tracked down the solution from another user on his Wordpress Blog for the same issue with CS5. Very disappointed at the amount of wasted time on this. Also, before I could post this message, I had to input a "Screen Name" and every single damn combination of screen names I could think of was taken. I even tried "Decker120908327128937129837" and it didn't accept it, because yeah, chances are that screen name is really in use, huh?
