509

It is loaded by default by /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist. If you run launchctl unload -w /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist that will disable it for your user. To turn it back on launchctl load -w /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist


58

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. For 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 - https://apple.stackexchange.com/a/237585/23876. From what I ...


57

After several attempts I finally found the file that is created during the installation process. So to prevent AnyDesk from starting at login, you need to delete the file, /Library/LaunchAgents/com.philandro.anydesk.Frontend.plist That solved my issues with autostarting AnyDesk at login.


52

Click on the menu bar icon. Click the ellipsis icon at the top-right. Select “Preferences” Uncheck “Launch at login”. Note: The “Preferences” option does not appear until you log in to Creative Cloud.


41

I looked into the plist file (/Library/LaunchAgents/com.philandro.anydesk.Frontend.plist) suggested in one of the answers here. You can open the file using any text editor and change the lines: <key>RunAtLoad</key> <true/> to <key>RunAtLoad</key> <false/> This worked for me. Update for file path: /Library/...


17

macOS Catalina Update: While the information in this answer holds true as stated and tested in the versions of OS X/macOS listed below, it does not work in macOS Catalina 10.15. I tested the following under macOS 10.14.6, macOS 10.13.1 and OS X 10.8.6. In Terminal, using the following syntax: osascript -e 'tell application "System Events" to make login ...


16

I'm currently using this set of commands—the wildcard answer will be a bit more future-proof if Adobe adds more services, but: Apple is shifting to having these services embedded inside app bundles, so new services added by Adobe may not appear in the usual /Library/Launch*/ paths but still have the same infuriating launch-at-login behavior and this answer ...


15

Open your terminal and type this : sudo plutil -replace RunAtLoad -bool false /Library/LaunchAgents/com.philandro.anydesk.Frontend.plist Basically this will set the auto start boolean value in the *.plist file from true to false which as a result would disable the autostart function. It's practically the same thing as the above solutions but much simpler. ...


10

The following services are are started at login by launchd /Library/LaunchAgents/com.citrix.AuthManager_Mac.plist /Library/LaunchAgents/com.citrix.ReceiverHelper.plist /Library/LaunchAgents/com.citrix.ServiceRecords.plist You can use launchctl to stop the processes like so launchctl stop com.citrix.AuthManager_Mac However I am currently unable to ...


9

Like @cheezsteak mentions, starting and stopping is done through launchctl. The process below allows you to stop autostart at boot. First, I fetched a list of all "citrix" processes that run on startup: launchctl list | grep citrix In order to remove them completely from starting up automatically, I use the following commands: launchctl remove com....


8

For Windows users, you have to disable the application on startup and change the service startup type to manual. For example on Windows 10 you should do the following: Task Manager => Startup tab => right click on AnyDesk and change it to disable. Control Panel => Administrative Tools => Services => AnyDesk Service => Right click and select properties => ...


5

Well, it seems there's no cleaner way than Applescript - at least my searches have turned up nothing. So I've written a simple script to add/remove/list login items: % loginitems -a Caffeine -p "/Applications/Caffeine.app" % loginitems -l Caffeine % loginitems -d Caffeine % loginitems -l %


5

Despite these programs aren't listed in Login Items I'd recommend you to check again the state of "Open at Login" option in the dock. Next stop is to verify the content of these folders ~/Library/LaunchAgents /Library/LaunchAgents /System/Library/LaunchAgents Launch Agents are usually loaded by launchd when the user logs in


5

It's far late, but I have discovered today, trying to remove a similar zombie item that you cannot remove items for ALL ITEMS when the padlock icon is closed. Open the padlock for any action that involves other users. That's all.


5

From Little Snitch itself… Login Connections While no user is logged in or a login is in progress, Little Snitch cannot display Connection Alerts. It therefore creates suggestions for all connection attempts that occur during that time. See the Little Snitch Help, chapter Rule suggestions for more information. & detail from just the first entry in that ...


5

There are several ways that programs can automatically start in macOS: First check "Login Items" which are found in System Preferences after clicking the "Users & Groups" icons. I understand that you have already checked here and did not find Spotify. Another possibility is that Spotify have been set to open at login from the dock. ...


4

Actually there is a non-deprecated way to do it: Open the "Script Editor" app Paste do shell script "PUT YOUR START SCRIPT PATH HERE" on quit do shell script "PUT YOUR STOP SCRIPT PATH HERE" continue quit end quit File > Save, Select Application and Stay open after run handler and Save ...


4

You can stop the item from launching with launchctl disable gui/$UID/bundle-id. If you don't know the bundle ID, you can find it by typing launchctl list. That will list all processes running under your user, with their PIDs in the first column. So, if you saw this: $ launchctl list - 0 com.apple.SafariHistoryServiceAgent 277 0 com.apple.Finder - 0 ...


4

Try to run the script with launchd instead. Save a property list like this as ~/Library/LaunchAgents/some.label.plist: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <...


3

Creating an app in Automator with shell script works fine to unload at startup without removing the plist files. You have to add : launchctl unload –w /Library/LaunchAgents/com.citrix.AuthManager_Mac.plist launchctl unload –w /Library/LaunchAgents/com.citrix.ReceiverHelper.plist launchctl unload –w /Library/LaunchAgents/com.citrix.ServiceRecords.plist ...


3

This is a deeply unsatisfying answer, but I got it to work by running /System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background & in a subshell. I changed login.sh to... #!/bin/bash longname=$0 shortname=$(basename "${longname}") echo "$(date -u "+%Y-%m-%d %H:%M:%S") ${shortname} (${...


3

Open System Preferences > Users & Groups > Login Items Select AnyDesk, then press the minus button.


3

One notable absentee from your list is the category 'plugins'. I.e. additional software that runs within existing software on your Mac. It could be browser plugins, plugins for Microsoft Office, or many other types of plugins. Besides that there's not really supposed to be other ways if you're only installing "well-behaving" software. If you install ...


3

Part of the list is stored in ~/Library/Preferences/loginwindow.plist under the LoginHook key. Also you'll find a set of LaunchAgents stored in this folder: ~/Library/LaunchAgents/ Each of the files in there detail a program that is started when your user account logs in. There's also a similar list in /Library/LaunchAgents and /System/Library/...


3

Yes, you can change it by buying the Pro version of Matthew Palmer's Vanilla which will allow you to permanently add the app to the Login Items list. If you really do not want to give 4.99$ to a guy giving out free software that he spends his own time making, you could startup the app using launchd or similar that doesn't use Login Items. Or you use a ...


2

(This is not about the user visible Login Items under the Users & Groups Systems Preferences) The Contents/Library/LoginItems/ buried in the application bundle is what appears to be the implementation of Apple's approach to sandboxed apps. The tip from @user495470 about the storage of the login item reference in /var/db/launchd.db/ seems to be now ...


2

You should be able to stop and remove the helper from launchd from the command line. Open up Terminal.app and do launchctl list | grep -i com.your.helper Look once you've located the job_label in the third column, you can run sudo launchctl stop com.your.helper sudo launchctl remove com.your.helper The manual for launchctl can be found here


2

The following list might help you to disable some program at startup : Those in System Preferences » Accounts » Login Items (actually, these include the ones from 1.) The login hook for loginwindow described here, read current value with defaults read com.apple.loginwindow LoginHook Some of those specified as part of a launchd script (or otherwise managed ...


2

Use a LoginHook. sudo defaults write com.apple.loginwindow LoginHook /path/to/script See here for more detail.


2

After decoding the LSSharedFileList entry, I discovered this is from an Erlang install.


Only top voted, non community-wiki answers of a minimum length are eligible