Skip to main content
Participant
December 18, 2015
Question

node.exe high cpu

  • December 18, 2015
  • 3 replies
  • 3575 views

hi,

We have installed a trail of InDesign on our remote desktop server (Windows 2008 R2).

After installed I noticed the CPU was running at a high CPU, the process is node.exe

I have renamed node.exe to disable it from running however what is the impact of doing so? now that node.exe is not running anymore the server CPU has dropped dramatically.

Thanks,

Mark

This topic has been closed for replies.

3 replies

Inspiring
April 26, 2016

I noticed node.exe running in my Win7 desktop task mgr for the first time today (not that it wasn't before, this was just the first time I noticed it). I did just reboot my machine.

I searched internet and found this thread.  I did see Creative Cloud had an update it wanted to install.  After several minutes, I finally opened the Cloud interface program/app in Win7 and clicked to let it update it's software.  As soon as I clicked to do the update, node.exe disappeared out of my memory.

Hope this can give some light as to what node.exe was trying to do (at least on my Win7 machine).

April 7, 2016

I too have watched node.exe consume about 25% of my available CPU, but I too have no idea what it is or what it does. I do know that when I kill the process, nothing on my PC appears to be affected. Pain in the ass having to kill it whenever I'm rendering video from Adobe Media Encoder, or working in Adobe Premiere. Googling node.exe doesn't yield any meaningful information, other than it is likely used by CC. 

Mylenium
Legend
December 18, 2015

Simple answer: Completely unsupported configuration. Servers use different networking and security stuff and who knows how it affects apps designed for desktop computers...

Mylenium

mlebrocqAuthor
Participant
December 18, 2015

Hi Mylenium,

Thanks for your reply however the applications seems to run perfectly fine, and whilst we are only testing it at the moment I was more interested as to why the application requires the node.exe to be running in the first place?

Even on a desktop configuration I would still question the same.

Many thanks,

Mark