It would be difficult for me to say "No" to this as I am not sure the checks in place when Adobe updates one of their programs. If you followed the steps all the way through, then you should still have the old node.exe just renamed. Before you do an update, you can rename the updated node.exe to something else, and change the name of the old node.exe back to node.exe. That way there shouldn't be any issues with the update. Cheers. ... View more

I have posted this over in another thread https://forums.adobe.com/thread/1326489 People tend to navigate to that suggested answer of suspending the node.exe to alleviate the constant error pop ups. However doing so stops the user from using Libraries. My response to that thread was to update node.exe and add an exception to the firewall (See below). Here are the steps I used to fix this issue for my users Download node.exe from the nodejs.org website (32-bit | 64-bit) Tested successfully with the 32-bit Backup the old node.exe by renaming it to something like node.exe.old, just in case. For me it was located under (C:\Program files\Adobe\Adobe Creative Cloud\CCLibrary\libs) Copy over the downloaded node.exe to the same folder (See Step 2) Add the exe to the windows firewall (Start Menu - Search "Allow a program through windows firewall") Click on "Allow another program..." Click "Browse..." and then navigate to the path in Step 2. Select node.exe and click "Open" Click "Add" to add the program to the Allowed programs list. Make sure all required boxes are selected. For me I just needed to make sure Domain was selected. Open your Adobe product to verify the error popup no longer appears. This worked on all of my Creative Cloud machines here in my office. Hope this helps others besides the users in my office. Cheers ... View more

The node.exe is typically called by the CCLibrary.exe (Creative Cloud Library) when you open your adobe product. If you are getting the Evented I/O window that opens and quickly closes, you will see it appear and disappear as a child of the CCLibrary.exe in processexplorer when you open an Adobe product like InDesign, Photoshop, etc. ... View more

Your best option is to resolve the issue long term. Here are the steps I used to fix this issue for my users Download node.exe from the nodejs.org website (32-bit | 64-bit) Tested successfully with the 32-bit Backup the old node.exe by renaming it to something like node.exe.old, just in case. For me it was located under (C:\Program files\Adobe\Adobe Creative Cloud\CCLibrary\libs) Copy over the downloaded node.exe to the same folder (See Step 3) Add the exe to the windows firewall (Start Menu - Search "Allow a program through windows firewall") Click on "Allow another program..." Click "Browse..." and then navigate to the path in Step 3. Select node.exe and click "Open" Click "Add" to add the program to the Allowed programs list. Make sure all required boxes are selected. For me I just needed to make sure Domain was selected. Open your Adobe product to verify the error popup no longer appears. This worked on all of my Creative Cloud machines here in my office. Cheers, DLindner ... View more