Adobe is renowned for making it challenging to uninstall its applications and services, and Core Sync is no exception. How to get rid of it will be demonstrated.
The Adobe Creative Cloud (CC) suite’s Core Sync feature allows for synchronizing. Core Sync slows down your Mac since it consumes a lot of CPU power, but that’s not the worst thing about it because it frequently remains installed even after Adobe has been removed, occasionally prompting you to retrieve files.
The intrusive warning has terrified some people, but allowing access won’t compromise your privacy. Core Sync has shown to be extremely challenging to uninstall using the typical uninstall procedure. Fortunately, you may manually terminate its processes to prevent them from loading again. We have the directions, so why don’t we get to work?
What Is Core Sync on Your Mac?
The Adobe suite includes Adobe Content Synchronizer, often known as Core Sync, which is installed automatically. To ensure that Core Sync always runs when you start your Mac or log in and out, Adobe’s Creative Cloud installer adds it to your login items. Additionally, it adds a macOS extension for the Finder interface that displays the synchronization status of Adobe cloud files.
Last but not least, Core Sync develops background processes that sync your documents, Adobe fonts, CC libraries, and other assets. These things also consume RAM and CPU resources, overheating your MacBook and shortening its battery life.
Core Sync cannot be successfully removed using Adobe’s Creative Cloud Cleaner tool. However, if you want to try it out, click the download button on Adobe’s support document.
How to Disable Core Sync in Adobe CC for Mac
With just a few clicks, you can disable the Finder extension, delete Core Sync from macOS Login Items, and halt background sync if the Creative Cloud suite is installed on your Mac. This will momentarily turn off Core Sync, but you may turn it back on by undoing the modifications you make below.
Launch Creative Cloud, click your profile symbol in the top-right area, and select Preferences to pause syncing. Then, on the right, click Pause Syncing after selecting Syncing from the sidebar.
Select General in the sidebar, go down, and toggle off Launch Creative Cloud at login and Sync Creative Cloud files in the background after quitting to prevent Creative Cloud from starting up immediately and starting syncing. Next, select Done.
Go to System Settings > General and select Login Items to disable the synchronizing component. Turn off Adobe Creative Cloud by selecting it from the Allow in the Background menu.
We’ll disable Adobe’s extension that links Core Sync with Finder as the final step. Select Extensions under Others at the bottom of System Settings > Privacy & Security, click Added extensions, uncheck Finder extensions below Core Sync, and then click Done.
Now that Core Sync has been turned off, you can restart your Mac and check.
How to Remove Core Sync From Your Mac After Uninstalling Adobe CC
If Core Sync persists after you uninstall CC, you might be unsure of what to do. You can delete all property list (.plist) files associated with Adobe that act as hooks for the macOS launchd process, which launches LaunchDaemons and LaunchAgents in the background.
Open Finder first, then select Go > Go to Folder from the menu bar. Then, go to the next three directories and choose all.Each directory contains plist files with the prefix “com.adobe”, Move to Trash by selecting using a control click on the item.
- /Library/LaunchDaemons/
- /Library/LaunchAgents/
- ~/Library/LaunchAgents/
Restart your Mac for the changes to take effect.
Free Your Mac From Adobe’s Core Sync
Core Sync is renowned for demanding a lot of CPU resources, which might overheat and make your Mac sluggish. So, even after uninstalling Adobe, these recommendations should help you fix the issue if macOS continues to prompt you for permission to access files on your Mac.
There are other software packages that behave poorly and won’t completely uninstall, besides Adobe Creative Cloud. Adobe is probably the most extreme example of such a user-hostile approach, although other well-known developers like Microsoft also implement background processes that are challenging to eliminate.