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

[antonellaa87642179]

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

[Drt_Harrie]

Thanks for the info Mark!

[jeppejesus]

Thanks.

It is for now almost impossible to use Adobe programs. The error comes app. every 10 sek.

[Drt_Harrie]

Hi Jeppejesus,

Did you try the suggestion provided by DLinder:

1. Download node.exe from the nodejs.org website (32-bit | 64-bit) Tested successfully with the 32-bit
2. 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)
3. Copy over the downloaded node.exe to the same folder (See Step 2)
4. Add the exe to the windows firewall (Start Menu - Search "Allow a program through windows firewall")
5. Click on "Allow another program..."
6. Click "Browse..." and then navigate to the path in Step 2. Select node.exe and click "Open"
7. Click "Add" to add the program to the Allowed programs list.
8. Make sure all required boxes are selected. For me I just needed to make sure Domain was selected.
9. Open your Adobe product to verify the error popup no longer appears.

This should at least help you to work with it. For the moment that would be a great workaround for the issue.

Until a new update or solution is provided for the current issue.

[SusLin]

The mentioned workaround worked for med - just tried it with help from our IT department! Now it's possible to work in InDesign CC2015 again which is my main working programme:-)

[mvoogt]

Thanks, I had the same error but the workaround works fine for me! Do we have to change anything back when Adobe launches the patch?

[DLindner]

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.

[maria_tzumpi]

The workaround didn't work for me.

I have excluded Adobe Creative Cloud from msconfig and it seems I don't receive the error anymore. I have Photoshop open for more than 30 mins and no error.

If i open Adobe Creative Cloud, the error reappears, regardless of me quitting the application afterwards.

[Drt_Harrie]

Using MSCONFIG to Stop Creative Cloud from being started at launch of the OS,

As soon as you launch Creative Cloud the issue starts, as the Libraries are being loaded as well.

But most likely the Patch for the issue will be released within a few hours.

The issue will be patched before the end of the week.

[Rayyann]

Hi Maria,

**** Kindly check Private message / Email

Rayyan

[maria_tzumpi]

Problem solved with Adobe Support. Thanks a lot guys!

[Laran70]

Hi maria,

How did you solve the problem?

What did you do?

[Rayyann]

Hi Lars,

We have identified the issue and Adobe will  begin globally rolling out updates soon.

Many Thanks !!

Rayyan 

[federicos59270443]

Hi! Any news Rayyan ?

[Rayyann]

Hi Fedrico,

We are working on rolling out updates as soon as possible. We appreciate your patience and cooperation

Many Thanks,

Rayyan

[Richard Galambos]

Any idea of a ball park?  Days or weeks - hours would be nice. 

[a.h17614220]

Are there any news about the problem? I can't use InDesign for about three days now and it'll be great to fix the error!

[maria_tzumpi]

Hi laran70‌,

I was contacted by rayyana32305846‌‌ from Adobe Customer Care and went through a remote session. With this occasion I wish to thank him once more for the help provided. Thumbs up!

[cindyd1645190]

Hello,

I have the same problem !

[oscarn38384209]

Where can the fix be found?

[Drt_Harrie]

When you Contact Customer support (over Phone or Chat) then they should be able to run the Patch on your system to resolve the issue.

As Patch isn't released yet, it might help for getting the patch also pushed live.

Hope this helps

[Rajashree Bhattacharya]

I would like to also state the same that we are awaiting the fix with bated breath as this issue is of considerable momentum.

It will taking place soon.

Regards

Rajashree

[nexbyte]

If Adobe already has a patch, they should at least help out everyone in this thread if, for whatever reason, they need to postpone a widespread update to everyone.

Is a roll-back to the previous CC app possible if this won't get fixed over the weekend?

[Drt_Harrie]

They are investigating with the patch to see if that fully resolves the issue before enrolling this as a new update. Hence the contact to support might help for the investigation of the Patch. Once there are enough successful results i guess the patch will be released.

Rolling back, i don't believe is possible to the previous Desktop update. Currently other then the patch are several suggestions mentioned on this topic. Renaming Node.exe, rolling back the version of Nodejs, or just allowing it for the firewall. Mostly when you change this, it results in issues with the Libraries as this is used for the CC Libraries.

I trully hope the patch will be released over the weekend, Lets keep our hope high

[Leigh Loubser]

I apologise but this is insane. We are not able to work...

For those that don't utilize their CC Libraries - There must be a way to block CC with the Firewall - Please let me know if there is a way to do this.

[Drt_Harrie]

I am sorry, I don't think i fully understand your request.

- You want to Fully Block Creative Cloud in your firewall?

When you block CC with the firewall, it will not have access anywhere and the Desktop Application.

Then you might also consider using Adobe Application manager, without the desktop application from Creative Cloud.

To Block the application from firewall, this is usually done within the firewall.

Select the application in the list of the firewall, and deny access.

I have don't really know what firewall you are using and how to manage that.