Adobe Apps Gone, but Creative Cloud Is Still Running on Your Mac

A Mole user removed Lightroom and then found Core Sync, Creative Cloud, Creative Cloud Desktop App, Installer and Uninstaller still sitting on the Mac. None of them showed up in the uninstaller list where they expected to find them. That is not a quirk of one machine. Removing an Adobe app never touches Creative Cloud, and Creative Cloud is not one app in one place.

I installed Creative Cloud 6.10.0.253 and Adobe Bridge 2026 on a test Mac, removed them in different orders, and recorded what each step left behind. The short version: the Adobe apps come out first, Creative Cloud last, and a handful of files stay until nothing from Adobe is left, because other Adobe apps still need them.

Creative Cloud is eight apps in three folders

Creative Cloud does not install into /Applications like most apps. It puts eight apps in root-owned folders under /Applications/Utilities:

• Adobe Creative Cloud: Creative Cloud itself, Creative Cloud Helper, Creative Cloud Desktop App, Installer, Uninstaller and Diagnostics, about 265 MB
• Adobe Creative Cloud Experience: CCXProcess, about 167 MB
• Adobe Sync: Core Sync and its Finder extension, about 165 MB

A fourth folder, /Applications/Adobe Creative Cloud, only holds shortcuts. Each Adobe app then gets a folder of its own, such as /Applications/Adobe Bridge 2026, with the app and an Uninstall Adobe Bridge 2026 shortcut inside, plus a second copy of that shortcut in /Applications/Utilities/Adobe Installers.

This layout is why the leftovers are hard to see. The apps sit two or three folders deep, so a list that only looks at the top of /Applications misses them. The folders belong to root, so Finder asks for an administrator password before anything moves.

What keeps running

Most of Creative Cloud runs from those sibling folders rather than from Creative Cloud.app. At login, three agents in /Library/LaunchAgents start Creative Cloud, Adobe Desktop Service and CCXProcess. A root daemon, com.adobe.acc.installer.v2, runs Adobe's installer helper. Core Sync adds a Finder extension, and Adobe OS Extension adds the Creative Cloud entry to Finder's context menu.

On the test Mac, moving Creative Cloud.app to the Trash stopped none of this. Core Sync, CCXProcess, Creative Cloud Helper, Adobe Desktop Service and AdobeIPCBroker kept running out of the Trash, and ElevationManager's Adobe Installer, which runs as root, kept running too. Anything still running like this stops at the next logout or restart. The login items that would start it again stay in place until someone removes them.

What other Adobe apps still need

Some of Creative Cloud's files are shared, and removing them while Photoshop or Lightroom is still installed breaks those apps rather than cleaning up after Creative Cloud:

Two things never belong in a cleanup at all. ~/Creative Cloud Files holds your own files, and since Adobe deleted the cloud copies of its old synced files service, the local folder may be the only copy. The parent folders /Library/Application Support/Adobe and ~/Library/Application Support/Adobe contain something from every Adobe product.

Removing it in the right order

Copy ~/Creative Cloud Files somewhere outside that folder first. Uninstall Creative Cloud without losing your files explains why the folder gets a new name once you sign out, and how to check the copy.

Then remove every Adobe app. In Creative Cloud, open Apps › All Apps, choose More actions next to the app and select Uninstall. If Creative Cloud will not open, double-click the Uninstall shortcut inside the app's own folder in Applications. Adobe's offline removal steps describe the same shortcut. Quit Adobe apps from their own menus: Bridge treats a plain terminate signal as a crash and shows a "quit unexpectedly" report.

Only then remove the desktop app with Adobe's Creative Cloud Uninstaller, choosing Repair first and Uninstall if that does not help. Adobe only lets it finish once the other Creative Cloud apps are gone. A copy is already on the Mac at /Applications/Utilities/Adobe Creative Cloud/Utils/Creative Cloud Uninstaller.app. Adobe's desktop app removal page has the download. Creative Cloud Cleaner is for an install that is already broken, not a more thorough uninstall; Creative Cloud won't uninstall on Mac? covers that path.

When the app is already in the Trash

If Creative Cloud.app was dragged to the Trash, or the uninstaller never ran, the rest is still there: the three folders in /Applications/Utilities, the shortcut folder, the launch agents and daemon, Adobe Desktop Common and Adobe OS Extension. With no other Adobe app installed, all of them can go, along with the caches, preferences and logs named com.adobe.acc…, com.adobe.accmac, com.adobe.ccd.helper and com.adobe.CCXProcess in your Library. With Photoshop or Lightroom still installed, leave the shared items from the table above.

Removing the root-owned folders takes an administrator password. Restart once afterwards so that nothing is left running from the Trash.

Checking what is left

pgrep -il 'core sync|ccxprocess|creative cloud|adobe desktop service|adobeipcbroker'
ls -d /Applications/Utilities/Adobe* "/Applications/Adobe Creative Cloud"
ls /Library/LaunchAgents /Library/LaunchDaemons /Library/PrivilegedHelperTools | grep -i adobe

No output from pgrep means nothing from Creative Cloud is running; a line it prints is a process that is still running, and once the login items are gone it does not come back after a restart. The second command should list only Adobe Genuine Service, plus Adobe Installers while another Adobe app is installed. The third should only show com.adobe.agsservice.plist, which belongs to Genuine Service, and com.adobe.AdobeDesktopService.plist while another Adobe app remains.

How Mole handles it

In Mole, Creative Cloud is one row. Its seven helper apps are folded into it, because removing Core Sync or the Uninstaller on its own only leaves Creative Cloud broken with its services still running. If Creative Cloud.app is already gone, the first component still installed takes its place and carries the same list, so a half-removed install can still be cleaned up in one pass.

Before anything moves, Mole asks the background components to quit and stops the ones that do not. When Creative Cloud is the last Adobe app, its folders, launch items, Adobe Desktop Common and its caches are selected by default. While another Adobe app is installed, the shared items are not listed at all and the other system-level items are listed without being selected. Libraries (only once Creative Cloud is the last Adobe app), Core Sync's state and sign-in data are listed but never preselected, and ~/Creative Cloud Files, the Adobe parent folders and the licensing pieces are never listed. The root-owned folders need your administrator password and go to the Trash, where you can still get them back. The exact rows and what each one is are in the Creative Cloud uninstall guide.

FAQ

Is Core Sync safe to delete?

Core Sync is Creative Cloud's sync engine, and it goes with Creative Cloud. Your synced files are not inside it; they are in ~/Creative Cloud Files, which is a separate folder you should copy before removing anything.

Why can't I just drag Creative Cloud to the Trash?

Its folders belong to root, and most of it runs from folders next to the app. Dragging the app away leaves the other seven apps, the login items and the background services in place, and those login items start the services again at every login.

I deleted Lightroom, why is Creative Cloud still installed?

Creative Cloud installs and manages the Adobe apps but is not part of any of them. Removing one app leaves Creative Cloud and everything it shares with the other Adobe apps untouched, which is what Adobe intends while other Adobe apps remain.