Adobe Creative Cloud Uninstaller Not Working on Mac? 7 Fixes for 2026

If you have run into the Adobe Creative Cloud uninstaller not working on Mac, you are not alone. Adobe's cleanup tools have always had a reputation for leaving behind a sprawling trail of caches, preference files, and helper daemons — and the situation is no better in 2026 on macOS Sequoia and Tahoe. Whether the uninstaller hangs, throws an error, or vanishes without removing anything, the seven fixes below will get you to a genuinely clean state on both Apple Silicon and Intel Macs.

Why Adobe's Uninstaller Fails in the First Place

Before diving into fixes, it helps to understand what is actually happening. Adobe Creative Cloud is not a single app — it is a suite of background services, launch agents, and helper apps spread across multiple system locations. When the uninstaller runs, it needs to stop these services before it can remove the files. If any of them are still running, or if the uninstaller binary is older than the apps currently installed, the process can silently fail or produce a generic error.

Common root causes include:

• Adobe Creative Cloud Helper or the CEPHtmlEngine process is still active in the background.
• The uninstaller binary is outdated — older than the apps currently installed.
• System Integrity Protection (SIP) is blocking removal of files written by a different process.
• A partial previous uninstall left the install database in a corrupted state.
• macOS Sequoia's tighter permission model means the uninstaller needs Full Disk Access to reach certain directories.

Fix 1: Force-Quit All Adobe Processes Before Running the Uninstaller

Open Activity Monitor (Applications > Utilities > Activity Monitor), search for "Adobe", and quit every process you find. Then do the same via Terminal to catch anything that respawns:

1. Open Terminal.
2. Run sudo pkill -9 -f Adobe to kill all Adobe-named processes.
3. Run sudo pkill -9 -f 'Creative Cloud' to catch any remaining helpers.
4. Wait ten seconds, then relaunch the Adobe Creative Cloud Uninstaller from /Applications/Utilities/Adobe\ Creative\ Cloud/Utils/Creative\ Cloud\ Uninstaller.app.

If that path does not exist, Adobe may have placed the uninstaller inside the Creative Cloud app bundle at /Applications/Adobe\ Creative\ Cloud/Utils/Creative\ Cloud\ Uninstaller.app.

Fix 2: Grant Full Disk Access to the Uninstaller

On macOS Sequoia, apps without Full Disk Access cannot read or delete files in protected directories like ~/Library when invoked by another process. To fix this:

1. Open System Settings > Privacy & Security > Full Disk Access.
2. Click the + button and navigate to the Creative Cloud Uninstaller app.
3. Toggle it on, then re-run the uninstaller.

You can remove the entry from Full Disk Access once the uninstall is complete.

Fix 3: Use the Adobe Creative Cloud Cleaner Tool

Adobe publishes a separate, more aggressive removal utility called the Adobe Creative Cloud Cleaner Tool. This is different from the in-app uninstaller — it is a command-line tool designed to remove corrupted installations and broken CC states. Download it from Adobe's official support pages, then run it from Terminal:

1. Download AdobeCreativeCloudCleanerTool.dmg from Adobe's support site.
2. Mount the DMG and copy the binary to your Desktop or another writable location.
3. In Terminal, make it executable: chmod +x ~/Desktop/AdobeCreativeCloudCleanerTool
4. Run it: sudo ~/Desktop/AdobeCreativeCloudCleanerTool --cleanupBoth

The --cleanupBoth flag targets both the CC Desktop app and all installed CC products. It will prompt you to confirm each product removal. The tool also handles removing launch agents and daemons that the standard uninstaller often misses.

Fix 4: Manually Remove Launch Agents and Daemons

Even after a successful uninstall run, Adobe background services often persist as launch agents and daemons. These cause the Creative Cloud icon to reappear on next login. Remove them manually:

• ~/Library/LaunchAgents/ — look for any com.adobe.* plist files.
• /Library/LaunchAgents/ — system-wide Adobe agents (requires sudo to remove).
• /Library/LaunchDaemons/ — Adobe daemons that run at boot.
• /Library/Application Support/Adobe/ — shared application support files.

To unload and remove a launch agent before deleting it, use:

1. launchctl bootout gui/$(id -u) ~/Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist
2. rm ~/Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist

Repeat for every com.adobe.* plist you find. You need sudo for entries under /Library/LaunchDaemons/.

Fix 5: Delete Residual Files Across the Library Tree

Even after launch agents are gone, Creative Cloud leaves behind gigabytes of support files and caches. Here is a map of the key locations and typical sizes you might find:

A tool like Crumb can audit all of these locations at once and show you exactly what is safe to remove before you commit to deleting anything. For a broader look at how application leftovers accumulate, see our guide to completely uninstalling apps on Mac.

Fix 6: Remove Stubborn Files Owned by Root

Some Adobe components are installed with root ownership, which means your normal user account cannot delete them even from Finder. You will need Terminal with sudo. After confirming which paths contain Adobe files, run:

• sudo rm -rf "/Library/Application Support/Adobe/"
• sudo rm -rf "/Library/Logs/Adobe/"
• sudo rm -rf "/private/tmp/adobe*" (temporary install files that can accumulate)

Use caution with sudo rm -rf. Always verify the exact path before running the command. If you are not comfortable with the command line, the Creative Cloud Cleaner Tool from Fix 3 handles this automatically.

Fix 7: Check for Leftover Kernel Extensions (Intel Macs)

On Intel Macs running older versions of Creative Cloud, Adobe occasionally installed kernel extensions (kexts) for GPU acceleration features in Premiere Pro. On macOS Sequoia these will not load due to tighter kext signing rules, but they can still clutter your system. Check /Library/Extensions/ for any files beginning with AdobeXPC or com.adobe. On Apple Silicon, this is generally not an issue because Adobe shipped universal binaries that dropped kext dependencies.

If you find stale kexts, remove them with sudo rm -rf /Library/Extensions/AdobeXPC*.kext and then run sudo kextcache -invalidate / to rebuild the kext cache.

How Much Space Can You Recover?

The answer varies significantly by how many apps you had installed and for how long. Users who ran Photoshop, Premiere, After Effects, and Illustrator for several years often find that the combined application folders, font caches, media caches, and support files exceed 20 GB. Caches stored under ~/Library/Caches/ alone commonly reach 5–8 GB across a full Creative Cloud subscription. Understanding what counts as system data in macOS Storage can help you make sense of where that space is going before and after the uninstall.

After the Uninstall: Confirm Everything Is Gone

Once you have worked through the fixes above, do a final verification pass in Terminal:

1. Run mdfind -name adobe | grep -i 'application support\|LaunchAgent\|LaunchDaemon' to use Spotlight's index to locate any remaining Adobe-related system files.
2. Open System Settings > Login Items & Extensions and confirm no Adobe items remain under Background Items.
3. Restart your Mac and open Activity Monitor to confirm no Adobe processes appear.

If you still see Adobe entries after a restart, repeat Fix 4 for any plist files the cleaner tool may have reinstalled. In rare cases a second run of the Adobe Creative Cloud Cleaner Tool with the --removeAll flag is needed to catch components that were in use during the first pass.