Skip to main content
New Participant
November 1, 2013
Answered

Evented I/O for V8 JavaScript, is it safe?

  • November 1, 2013
  • 33 replies
  • 180452 views

After opening Photoshop CC (14.1.2) I receive a Window Security Alert stated that Windows Firewall has blocked some feature of this app. The details are as follows: Windows Firewall has blocked some of the features of Evented I/O for V8 Javascript on all public and private networks. The publisher is Joyent, Inc. and the path is C:/program files/adobe/adobe photoshop cc (64 bit)/photoshop-node.exe. My question, is it safe to allow Evented I/O for V8 to communicate on private and/or public networds?

This topic has been closed for replies.
Correct answer Compass NZ

OK, I will try to explain easily the workaround proposed by annexa89826053

1. Go to here and download process explorer: https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

2. You will get a .zip file that you need to extract to a normal windows folder -> Right click extract

3. Run the file procexp.exe

4. Accept the  license terms

5. Once the Process Explorer is running you can select from the list a process called: node.exe (green icon)

6. right click node.exe and select Suspend

DONE !

Hope this helps

33 replies

New Participant
March 26, 2016

This fix does work, thank you, but I have had to do it each time I sign on to my computer.  The error message comes up without opening any of the CC Apps.

Inspiring
March 28, 2016

If you go to Youtube.com and do a search on "How do disable adobe apps at startup in windows" Assuming you are using windows and NOT Apple computer. You will find instruction on how to stop CC App from loading each time you sign into your computer. WIndows 7, 8 and 10 all three has video instructions.

New Participant
February 17, 2016

‌I can,t use photoshop cc. The I/o script message repeats every fifteen seconds! Neither advice sequence has worked. Any ideas please Helen

JohnVo
Inspiring
February 16, 2016

hi

6. right click node.exe and select Suspend

but does it suspend for ever ?

thanks

New Participant
February 16, 2016

I was able to get the popup to stop by letting node.exe run as an admin file:

1. Open Task Manager

2. Click the Processes tab

3. Right click on the "node.exe" process

4. Click Properties

5. Click the Compatibility tab

6. Click in the "Run as administrator" check box

7. Click Apply

8. Click Ok    

RdW
New Participant
December 11, 2015

Since the last update of Creative Cloud the error is gone.

Participating Frequently
December 10, 2015

I have the same problem still getting the v8 error but do not have node.exe... what is the real solution? why in the world should I have to download the product AGAIN when I am paying a monthly service and it's supposed to be updated by adobe... can't they just put the fix on their panel for next update?

Wosik1
New Participant
December 11, 2015

As I wrote you should update the Creative Cloud Desktop to the latest version  x.4.1.181.

Participating Frequently
December 11, 2015

this did NOT correct my problem as I am still receiving the messages after the update.

Wosik1
New Participant
November 27, 2015

The current update for CC Desktop app fix the problem. Please check if You have the version x.x.x.181

When not please download this version from here:

http://trials2.adobe.com/AdobeProducts/KCCC/1/win32/ACCCx3_4_1_181.zip

First start downloading a Trail of a product after signing in with the Adobe ID

1. Open the page

https://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html

and then click above link. You should see the download being started, as a ZIP, Extract the Zip, and run the setup.exe

Please, give a feedback if the update solve the issue.

Thank you in advance!

P.S.

I forgot. Here is the link for MAC OS X if needed

http://trials2.adobe.com/AdobeProducts/KCCC/1/osx10/ACCCx3_4_1_181.dmg

And do not worry, the update should appear officially on next Monday (30-12-2015)

Szymon Golis
New Participant
November 27, 2015

Confirmed, It works for me!

New Participant
November 27, 2015

The solution DLinder provided worked for the machines in our office. I do have to note that the node.exe files that we replaced were al located in Adobe installation folders and thus provided by Adobe. Blaming Microsoft (as was mentioned in another comment in this thread) by Adobe is therefore wrong and just a way of finding an easy scapegoat for their own failing. Adobe provided the files, therefore Adobe should fix this (and do better testing!).

Since we started using the Creative Cloud solution (you have no other choice by the way), we have seen more issues that Adobe blames on someone else his product, although the problem is in their own software (such as being unable to update the Creative Cloud desktop app, because it gets stuck after two percent and you need to download a full new version from the site).

Adobe fix this and please update your product testing before releasing software to the world!

RdW
New Participant
November 27, 2015

I also encountered this problem today for the first time. Seeing the timestamp of the TS, wich leads me to the question why Adobe let's this situation continue, I doubt Adobe will take action soon.

@Adobe, please fix this issue. It seems to look like the data that is being send by Node.exe is that much value it overrules the user experience. Too bad

Also nog have seen any comment on this from Adobe itself, on the forums of ADOBE itself!

New Participant
November 26, 2015

Hi!

@ Adobe, can you please answer this thread with your expected solution for this? Or are we left alone with own "hacks" to solve this? Its fantastic to se all the contribution by all kind people in this thread but this should come from Adobe, and not in the far future. Now! Its impossible to work under this since the popup blocks all other programs and its always on top.

Adobe?

New Participant
November 26, 2015

Today I had the same problem, so i searched for a solution and after this, it worked:

1. Open the "Task Manager" while the process of this problem report is running (otherwise you won't see it)

2. Click on "node.exe", open the file path (mine was C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary\libs).

3. Delete the programm while it does not appear on the screen.

And the problem is solved!

gert verrept
Inspiring
November 26, 2015

Tried that too, but afterwards the CC libraries don't work anymore. We merely work in Indesign and need the libs to work fluently. Replacing the node.exe with a newer version, doesn't do the trick neither, error is gone and CC libs do not work anymore.