Skip to main content
Michael Plaengsken
Participant
March 10, 2026
Question

Node.exe - Are you serious?

  • March 10, 2026
  • 2 replies
  • 285 views

I was really confused about my CPU fans working all the time even when the system is ideling, with no apps running (Win 11) 
I checked the taskmanager and there is a task running with the name of “node.exe”. if I close that task, the peaks of my CPU immediately come down and the system gets quiet… until some seconds later the task is started again and leads to performance peaks in the first 4 Cores of the CPU.

The node.exe is located in this folder: C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs
I just moved it to somewhere else, so it couldn’t restart and voilá, when I kill the task once again, the system stays quiet.

 

the red line marks the time I shut down the node.exe task

Guys, I have this with my home machine, and the PC at work. If this is common for all CC users, it’s a severe waste of energy and maybe CPU lifetime.

If the Creative Cloud App is running, there is another node.exe running, located here:
C:\Program Files\Common Files\Adobe\Creative Cloud Libraries\libs
But that is not as performance costly as the one in the Experience-folder. At least it doesn’t generate those peaks.

 

Adobe, Please fix that!


best
Michael

 

    2 replies

    Bujez
    Participant
    April 26, 2026

    I was about to post the same issue and solution when I came across your post. Indeed the node.exe located in C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs was using a significant amount of CPU for no apparent reason. Even after disabling both Creative Cloud and Creative Cloud Content Manager from starting up, the node.exe process would still launch on system restart.

    I did the same as you and removed node.exe from C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs. For now, everything appears to be working normally. Creative Cloud and Creative Cloud Content Manager start without any issues, my project files are syncing with the cloud, and app updates as well. I’m guessing this node.exe is a left over from some older version that is not needed anymore. 

    Anyhow, defiantly something Adobe team should look into.  

    kglad
    Community Expert
    Community Expert
    March 10, 2026

    you can replace node.exe with the current version.