Firewall exception each time Captivate 8 is launched

[Cozmicone]

Every time I launch Captivate 8 I get a Windows Security Alert asking me to add an exception to my Windows Firewall for Captivate. The details of each exception point to a location inside my appdata\local\temp directory.

C:\users\mstephens\appdata\local\temp\cp3916420360387session\cptrustfolder3916420360387\adobecaptivatews

C:\users\mstephens\appdata\local\temp\cp8020420386985session\cptrustfolder8020420386985\adobecaptivatews

C:\users\mstephens\appdata\local\temp\cp11584515494399session\cptrustfolder11584515494399\adobecaptivatews

I have the main executable added as an exception already but I get the prompt for new temp folders on each launch.

[jsmeng]

I'm having the same problem.  I'm assuming it's a bug as it is noted as a top issue by Adobe.

http://helpx.adobe.com/captivate/kb/top-issues-captivate-8.html

[Barbara Ash]

It's definitely a bug. I contacted Adobe directly about this and they confirmed it is a bug and the representative said that Adobe is working on it.

[Guest]

We also experienced the same issue with Captivate. Glad to see Adobe's aware and working on it. For users with local admin access this isn't a problem but in our environment users do not have local admin rights so this poses a problem. Fortunately it seems there's a simple workaround: Just wait for Captivate to finish loading completely before click on the Cancel button on the Windows Firewall prompt. If you wait until Captivate loads, clicking Cancel will not terminate the program and seemingly all functionality remains intact. If you click Cancel before Captivate is finished loading it will terminate Captivate. Hope that helps!

[Marcuse601]

In my case I am working at a home computer, no issues with local admin rights. I have tried out you solution, but it doesn't work. When I wait for Captivate to load I get to see the opening screen for a few seconds and then it suddenly disappears. Cancel or no cancel.

[Guest]

That's unfortunate . Curiously do you have Run As Administrator checked? Maybe that'll make a difference and sorry if it seems obvious but in my experience sometimes the most obvious solutions are overlooked. If it isn't, try checking it and then hitting Cancel on the WIndows FIrewall prompt after Captivate loads. Otherwise it seems the only thing to do is for Adobe to fix it.

[Marcuse601]

Thanks for your reply. Have done everything you mentioned without success. I guess it comes down to waiting for Adobe.

[Captiv8r]

Hi there

Until Adobe addresses the issue with a service release, it won't matter if you have Run As Administrator enabled or not (And you should ALWAYS be running as Administrator).

Cheers... Rick

[ryan_schar]

What would happen if we just deleted that folder or that file?

[David_Suter]

Also having this problem in my organisation.

[DarrelTenter · Accepted solution]

I was having this same issue with Cp8 in Windows 7. I contacted TCS support and they helped me solve it for me. I asked if they would be willing to reply here with a link to download the fix, but they said "We don’t know, when we will be providing the link to the file, however we will be updating about the same on our forum and hopefully can come up with the link to the file shortly."

However they don't have an issue with me posting it, so here it is.

1. In C:\Program Files\Adobe\Adobe Captivate 8\SWF_Components\ws rename CivitWEb.exe to CivitWeb_bak.exe, or move it to your desktop.
2. Download CivitWeb.txt from my Dropbox.
3. Move the .txt version to the \ws folder above and change the .txt extension to .exe.
4. Launch Captivate.

Once I placed the file, I no longer got the firewall warnings, and no more buildup of cp session folders. I was also having an issued with browser previews not working. That issue was solved also. They said that with this file in place, Edge Inspect preview wouldn't work, but it is working for me.

Hopefully this will help others until Adobe has an official update or fix. Of course this is at your own risk. Good luck.

[AdobeUserT]

I'm surprised they have not released this yet or updated the software with the fix. Thanks for sharing!

[Kvanwem]

Thanks, worked perfectly!

[jsm201]

This looks like a good fix.  Who is "TCS Support"?

[Captiv8r]

Likely simply "Adobe Support". Captivate is part of a bundle known as the "Technical Communication Suite" (or TCS).

My guess is that this is what was being referred to.

Cheers... Rick

[DarrelTenter]

Yes, that's what I mean. We use the the Tech Comm Suite. Adobe's TCS support is a different department than FrameMaker, Captivate, or Robohelp support.

[Sean_Aikins]

Cheers! Thank you for the CivetWeb fix!

[eldhosejacob]

Thanks. Its worked for me !!!..

Regards

Eldhose Jacob

www.webshore.biz

[GreenTeamTek]

DarrelTenter Thanks for your fix! I no longer get this pop-up, but my browser previews are now maximum size and are not responsive (they don't resize to the window). I like to have the preview fit in the window so that I can see everything that's going on. Any ideas on this? Anybody else have any ideas?

[Julie88]

I am having the same issue.  Has this been fixed yet?

[THuckabay]

I too am having this issue, and to date, Adobe has NOT fixed it!

[Cozmicone]

Not yet, but I found that just by renaming the CivitWeb.exe file to a .bak extension you're never prompted about the firewall. I haven't noticed any effects from doing so that cause Captivate to function incorrectly.

EDIT: Don't do this if you want to use the preview to HTML5. Removing the file causes this ability to no longer function.

[Cozmicone]

If anyone is wondering, this issue also exists with Captivate 9 but can be resolved using this same method.

[donalall]

I installed the fix and it worked. But i now cannot Preview a responsive project. When i click the windows yellow bar message to remove it, the loading icon stays onscreen and nothing else happens. I have reinstalled captivate (9.0.0.223) - preview works but i still get the firewall exception message. Do back to square one. Regards Donal.

[Cozmicone]

Don't follow my suggestion to just delete or rename the civetweb.exe file. Doing so means you won't be able to get results from SCORM Cloud if you use it for testing purposes.