Skip to main content
Known Participant
March 9, 2021
Question

CoreSync.exe and Explorer.exe High CPU - Win10

  • March 9, 2021
  • 2 replies
  • 446 views

There was a very relevant post that got locked, so here's an attempt to bring this up and keep it recent.

 

Coresync.exe causes Explorer.exe to shoot up to 40% cpu usage, with coresync.exe itself running at about 15%. When this happens, my computer is nearly unuseable, and good luck navigating Windows Explorer--stutters like crazy.

 

When I kill coresync.exe / close out of Adobe Creative Cloud alltogether, Explorer.exe resumes normal cpu usage and everything is peachy again.

 

(sidenote: for any Adobe forum mods or anyone from Adobe Support that cares--in order to post this question here, I was required to pick a topic category from four options that were, at best, very inaccurate to the nature of this issue. This question is unrelated to "File Sync" "Collaboration" "Libraries" or "Cloud storage web assets." Consider reviewing how this feature is implemented.)

This topic has been closed for replies.

2 replies

John T Smith
Community Expert
Community Expert
March 9, 2021

How to disable a program in Windows startup
-Click the 'window pane' in the very bottom left corner of the Windows desktop
-Select * Settings
-Select Apps
-Select Startup
-Select/toggle the program you want to disable/enable
-BE VERY CAREFUL WHAT YOU DISABLE SO YOU DON'T STOP WINDOWS FROM RUNNING

LinSims
Community Expert
Community Expert
March 9, 2021

There have been constant complaints about the resources Creative Cloud uses and how it can cause the computer it is used on to heat up a great deal. Unfortunately for all of us, Adobe support generally does not monitor these forums.

 

If you want Adobe development teams to pay attention to the issue, I suggest you go to https://www.adobe.com/products/wishform.html

 

This is the only method I know of to let them know that there's a problem they need to look at. I expect that there are numerous bug reports about this. The more reports the development teams receive on the topic, the more likely they are to address it (although I, personally, make no guarantee that they will).