Please comment if someone does see Adobe touching the override database.įor more information on launchd, the launchd Tutorial is a great overview on launchd jobs. LaunchDaemon jobs are run as root so we use sudo to disable them for the root user.įrom what I have seen so far, Adobe installs do not update the override database, so you shouldn't need to run the commands again after an Adobe install (unless they introduce another job). The override database is on a per user basis. Library/LaunchAgents/) is marked as enabled. launchd will follow the override database entry even if the job definition (e.g. Sudo launchctl unload -w /Library/LaunchDaemons/com.adobe.*.plistĪs background, launchctl unload -w disables each service in the override database.

launchctl unload -w /Library/LaunchAgents/com.adobe.*.plist After running, reboot to enjoy an Adobe free launch (until you actually run an Adobe product). You can ignore any “Could not find specified service” warnings. Building on Shutko’s answer, the following will disable them everywhere. So you will need to check for updates from inside one of the Adobe apps or explicitly run Adobe Create Cloud.Īdobe actually puts their launchd job definitions in several places and those places change depending on the Adobe version. Note that the following will also disable Adobe automatic update checking. From what I have seen, you will need to repeat this step after each Adobe Creative Cloud upgrade.įor the launchd jobs, read on.

To turn off everything Adobe launches at startup on the Mac you need to both disable its launchd jobs and the Adobe Core Sync extension.įor the Adobe Core Sync extension, it is a Finder Sync extension so you can disable it under System Preferences → Extensions as described in this answer.

Cc installer