Inspiring

Node.js JavaScript Runtime uses 100% of a core all the time

Forum|Forum|1 month ago
June 7, 2026
16 replies
97 views

On Windows 10, using the latest version of Adobe CC, the process “Node.js Javascript Runtime” uses 100% of a core, all the time. This is a relatively new problem. My computer’s fans are running non-stop as a result.

The Node.js thing is located in: C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs

PhotoVideoCZ26

Participating Frequently

I can reproduce the same issue on Windows 11 64-bit with Creative Cloud Desktop 6.10.0.252.3.

Every time I open Creative Cloud Desktop, node.exe from:

C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs\node.exe

starts using approximately 12.5–13.5% of total CPU continuously. On my 8-thread processor, this corresponds to one logical CPU core being fully utilized. The laptop fan then runs continuously.

The process chain is:

Adobe Desktop Service.exe → CCXProcess.exe → node.exe

The high CPU usage continues even after I exit the Creative Cloud Desktop window.

I have already tried:

- repairing Creative Cloud Desktop;
- restarting Creative Cloud with Ctrl+Alt+R;
- completely removing Creative Cloud Desktop with Adobe Creative Cloud Cleaner Tool;
- installing a clean copy of Creative Cloud Desktop;
- renaming/resetting the OOBE and AAMUpdater folders.

None of these steps solved the problem.

Disabling the Adobe Creative Cloud scheduled startup task prevents the issue after Windows starts, but opening Creative Cloud Desktop manually immediately reproduces it. Force-closing Creative Cloud, Adobe Desktop Service, CCXProcess and node.exe stops the CPU usage and the fan becomes quiet again.

Please investigate this as a Creative Cloud Desktop / CCXProcess bug.

kglad

Community Expert

@PhotoVideoCZ26

node.js over-activitiy indicates a syncing problem.

PhotoVideoCZ26

Participating Frequently

Thanks. Which specific syncing component do you mean — Adobe Content Synchronizer, Creative Cloud Files, Libraries, or something else?

In my case, node.exe starts using one full logical CPU core immediately after opening Creative Cloud Desktop, even when there are no visible file transfers and disk/network activity is nearly zero.

How can I identify or temporarily disable the affected syncing component for testing without breaking app updates or licensing?

J

JflemayAuthor

Inspiring

I’ve deleted node.exe from C:\Program Files\Adobe\Adobe Creative Cloud Experience\libs and for now, this appears to have solved the problem. My computer runs normally and quietly again. See my other reply below for other things I tried.

kglad

Community Expert

as long as your not using any adobe’s cloud services you shoud be ok.

kglad

Community Expert

replace node.js with the current version.

J

JflemayAuthor

Inspiring

I’ve tried repairing the Adobe Creative Cloud installation in Windows’s Apps and Features, it didn’t work. I’ve also tried installing Node.js separately as a piece of software from nodejs.org, it didn’t work. Node.js JavaScript Runtime still runs and takes a full core. I’ve disabled all auto-updates and synching in the Creative Cloud preferences; no avail. When I terminate the Node.js process, it reappears.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.