Copy link to clipboard
Copied
Everytim i open captivate 9 i get asked to allow access for adobecaptivatews ..... is ther a way to stop this? seems every session opens a new temp file ..... why?
Copy link to clipboard
Copied
I will second this.
The new patch for 9.0.1 has not resolved this issue.
Copy link to clipboard
Copied
No way to keep it from appearing. Also, not sure why it appears, but it started doing this with version 8.
Copy link to clipboard
Copied
I'm getting the same error. Any solutions found?
Copy link to clipboard
Copied
Follks, I'm not convinced it's an actual "error" but more of an "advisory". I'm not sure I've ever seen anyone from Adobe tell us exactly why we see this. So all we really have to go on is sort of "educated speculation".
This began to appear when Captivate began offering the "new kid on the block" output known as Responsive. I know that when we preview a Responsive output, it generates output to a temp folder and opens the browser to show us the results.
I just now checked and here is the address I see in my browser address bar:
http://localhost:5387/HTML5Temp24776308120078Pre/rindex.html
And here is a screen capture of my own firewall advisory:
I suspect that it's the preview mechanism for the Responsive output that is triggering the Windows firewall message as it's coming from the "localhost" which I believe is kind of a personal web server.
I found another thread (linked below) where folks are stating that Adobe acknowledges it is a bit of a bug in the way they are handling things.
Firewall exception each time Captivate 8 is launched
Anyhoo, for me, I just know I click Allow access and it's typically all good.
Cheers... Rick
Copy link to clipboard
Copied
Rick,
You are correct that the adobecaptivatews file is being targeted by the firewall because it thinks it is some kind of security risk. The ws characters on the end of the filename stand for Web Server.
I had the same issue for some time with my Norton antivirus software picking off this file every time I opened Captivate. Eventually Norton seemed to work out it wasn't a virus and now leaves it alone, but it took months.