• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Error: "Evented I/O for V8 JavaScript has stopped working"

New Here ,
Nov 23, 2015 Nov 23, 2015

Copy link to clipboard

Copied

Has anyone had this issue? Does anyone know what is causing the error?

TOPICS
Creative Cloud

Views

34.6K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Nov 24, 2015 Nov 24, 2015

This has been going on for the past couple days now.  There are a number of forums posts about this with no fix from Adobe yet.

Re: Indesign: evented I/O for v8 javascript has stopped working

I've seen this when indesign or photoshop is open and problem started when updating the Adobe Creative Cloud app.  This is affecting hundreds of users spread across multiple companies I manage.

I've managed to stop the error by doing the following

renamed node.exe to node.bak in the following locations:

C:\Progr

...

Votes

Translate

Translate
replies 124 Replies 124
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Hi,

I have the same problem.

Does anyone have a solution ?

Thank you

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Just happened to me this morning as well once I opened up InDesign. Hopefully they will have it fixed soon.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Same issue here also (InDesign) after Creative Cloud was updated today.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Might have found a temporary solution.

Open Task Manager, Check box for "Show processes for all users" and end process for "AdobeUpdateService.exe"

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Ending AdobeUpdateService.exe doesn't work for me. Seems like CCLibrary.exe keeps re-opening and throwing this error constantly as long as InDesign is open.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Ending AdobeUpdateService.exe doesn't work for me too...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

What I have find out is just a temporary solution.

- msconfig  - turn off all Adobe services

- restart

- rename - C:\Program Files (x86)\Adobe\Adobe Creative Cloud -> Adobe Creative Cloud_old

- msconfig - turn all Adobe services

- restart

You don't have access to CC, but you can work with apps. For some time I assume.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

I have started having the same problem the last 2 days as well. Open any Creative Cloud program and the error window continually pops up.

ERROR Evented I-O for V8 JavaScript has stopped working.jpg

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

I am having the same issue after Creative Cloud updated.

Photoshop is now also being effected by this issue.

None of the temporary fixes seem to have worked for me either

Doc1.jpg

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Hi All,

I apologize for the inconvenience caused. Could you please confirm whether the issue is specific to any one particular Adobe Application or all of them.

Regards,

Anupriya Khare

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

This has been going on for the past couple days now.  There are a number of forums posts about this with no fix from Adobe yet.

Re: Indesign: evented I/O for v8 javascript has stopped working

I've seen this when indesign or photoshop is open and problem started when updating the Adobe Creative Cloud app.  This is affecting hundreds of users spread across multiple companies I manage.

I've managed to stop the error by doing the following

renamed node.exe to node.bak in the following locations:

C:\Program Files\Adobe\Adobe Photoshop CC 2015\
C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCLibrary\libs\
C:\Program Files (x86)\Adobe\Adobe Creative Cloud\CCXProcess\libs\

Waiting for appropriate fix from Adobe as this is a wide-spread issue.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 25, 2015 Nov 25, 2015

Copy link to clipboard

Copied

Thank you, that worked for me.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 29, 2015 Nov 29, 2015

Copy link to clipboard

Copied

This fixed my issue as well. however the file was not located in program files\ folder but was in the both x86 folders.

Thanks

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

My issue is basically all programs associated with Creative Cloud - Indesign, Photoshop, Illustrator, Muse etc.

It started occurring after the Creative Cloud application updated this morning.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Please try the steps mentioned in Evented I/O for V8 JavaScript, is it safe?

Hope this will help you.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Hi Anupriya,

You are Adobe staff.  Do you know when Adobe will be releasing a patch for this issue?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

Well I have already escalated this issue to the concerned team. Will update here soon with the solution.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 25, 2015 Nov 25, 2015

Copy link to clipboard

Copied

I did the instructions in this thread Evented I/O for V8 JavaScript, is it safe?

Seems to have worked! Thanks.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 25, 2015 Nov 25, 2015

Copy link to clipboard

Copied

Hi,

What's the estimated time for the update?

Jaakko

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 24, 2015 Nov 24, 2015

Copy link to clipboard

Copied

I'm still getting this error. I updated CC on Tuesday. Followed these steps:

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

But after a few hours of working in either Photoshop, InDesign or Illustrator - I'll get the error again (less frequently though), and if I reboot I get the error message every 20secs-3mins, until I follow the steps again.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 25, 2015 Nov 25, 2015

Copy link to clipboard

Copied

For me it worked this way. Hopefully not only temporarily.

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

I was told that it´s a windows problem ?! ... I´m also using CC2015 on a Win 7 machine.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 15, 2016 Feb 15, 2016

Copy link to clipboard

Copied

Well that workaround worked when I first had the problem but today when Adobe CC updated, the problem returned and that fix NO LONGER works!

Adobe can you please provide a fix?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 09, 2016 Apr 09, 2016

Copy link to clipboard

Copied

I just this again today and the old suggested fox doesn't resolve it. Are we going to see a fix sometime soon?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 18, 2016 Apr 18, 2016

Copy link to clipboard

Copied

It's back and worse than ever, and nothing fixes it now. I've uninstalled, reinstalled, updated, everything.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines