How To Turn Off Creative Cloud

by -78 views

Demonstrative screen capture of Adobe processes. I ran these manually just now, and then resource usage is low.

Aye, the ones you didn’t know were running this whole time.

If yous’ve already scoured the internet for a response to this question, near now you’re probably expecting me to feed yous a canned response from corporate and redirect you to pausing your file-sync in the app preferences.

I’m going to exit that to the professionals:

Corporate Response from Adobe.

If you lot’re at the kickoff of your search, that may actually be what yous’re looking for, and I encourage you to go plough off the beginning-on-login and file-sync features there.

I’thou here to discuss preventing these processes and services from running continuously when you’ve already flipped all bachelor switches in app preferences and aren’t even using Artistic Cloud.

If you’ll be reading onward, I’ll assume you’re interested in the same.

The Problem

For me, it all started while I was troubleshooting some network issues. I checked traffic on port 53, running
sudo tcpdump -i en0 port 53, and to my surprise, my computer was pinging
p13n.adobe.io
every 2d along with several other adobe endpoints at less frequent intervals.

Surprised, I checked for stray Adobe processes, running
ps -ax | grep “Adobe", and I institute
12
of them.

Now startled, I checked Action Monitor to become a prettier view of what I then knew to be truthful.

Demonstrative screen capture of Adobe processes. I ran these manually merely now, so resources usage is depression.

The Solution

Library-based processes and services are expressed as
plist
files and
should
simply ever by located amidst three folders:
/Library/LaunchAgents,
/Library/LaunchDaemons, and your user-specific
~/Library/LaunchAgents. Adobe conveniently prefixes all their
plist
files with
com.adobe. This gives usa some room to programmatically find these suckers.

I tried forcefully ending the processes and disabling them, using
launchctl unload -wF. This wouldn’t work at all unless I starting time manually stopped each one as well.

        ls -d /Library/LaunchDaemons/com.adobe* | xargs launchctl finish
ls -d /Library/LaunchAgents/com.adobe* | xargs launchctl stop
ls -d ~/Library/LaunchAgents/com.adobe* | xargs launchctl stop
ls -d /Library/LaunchDaemons/com.adobe* | xargs launchctl unload -wF
ls -d /Library/LaunchAgents/com.adobe* | xargs launchctl unload -wF
ls -d ~/Library/LaunchAgents/com.adobe* | xargs launchctl unload -wF

Upon restart, I found I even so had one
Core Sync Helper
process running. Also, with the insistence Adobe has displayed in running software despite knowing my preference to the reverse, I didn’t feel I could trust that Adobe wouldn’t go into the register and re-enable these processes at some hereafter bespeak (for my own good, of course). As such, I opted to simply move these files to a carve up folder.

        mkdir -p /Library/LaunchAgents_ignored
mkdir -p /Library/LaunchDaemons_ignored
mkdir -p ~/Library/LaunchAgents_ignored
mv /Library/LaunchAgents/com.adobe* /Library/LaunchAgents_ignored
mv /Library/LaunchDaemons/com.adobe* /Library/LaunchDaemons_ignored
mv ~/Library/LaunchAgents/com.adobe* ~/Library/LaunchAgents_ignored

This, I realized, would as well help firm other deceptive background processes, should whatsoever of my other applications step out of line.

Even after this modify and the corresponding restart, I was still stumped by this single extra
Cadre Sync Helper
procedure.

After some online digging, I made my way to the StackOverflow post of the hour. The issue was with a registered extension past Adobe to let Creative Cloud to integrate with Finder. This, I disabled through
System Preferences > Extensions > Core Sync > Finder Extension (uncheck).

Alas, I could slumber.

TLDR:

There are three steps.

  1. Open Creative Deject’s App Preferences and disable run on login and file sync.
  2. Disable the Cadre Sync extension on your organisation:
    System Preferences > Extensions > Core Sync > Finder Extension (uncheck)
  3. Stop the processes from running in the future. (2 options)
  • Choice A: Finish, unload, and disable all the processes with
    launchctl
  • Selection B: Move all the relevant
    plist
    files to backup folders.

Disclaimer:

I haven’t notwithstanding needed to employ Creative Cloud again. When I practise, I imagine I’ll need to disengage some of these steps. I’ll circumvolve back and mail whatsoever novel steps here when that happens. It shouldn’t be more than moving the plists back, but all is rarely as it should be:

        mv /Library/LaunchAgents_ignored/com.adobe* /Library/LaunchAgents
mv /Library/LaunchDaemons_ignored/com.adobe* /Library/LaunchDaemons
mv ~/Library/LaunchAgents_ignored/com.adobe* ~/Library/LaunchAgents

If anyone finds time to create a little package for this to brand it more user-friendly for folks afraid of the terminal, let me know and I’ll link information technology here.

Please share in the comments what led you here on your search.
Did your calculator slow to a crawl with Core Sync hogging your CPU? Were the background processes eating up l% of your RAM? Did yous accept a surprising network experience like me? I’d like to know!

Also, feel free to accomplish out with any questions.

#Unreviewed #Unedited

Cheers,
Justin

Source: https://justin-ross.medium.com/how-to-disable-adobes-creative-cloud-background-processes-fb4e572a628c