Skip to main content
Participant
November 25, 2008
Question

"Adobe Captivate has stopped working"

  • November 25, 2008
  • 2 replies
  • 785 views
In April I download, paid and installed Captivate 3. The next five month I used Captivate, and most function worked as expected. The last month I have not used Captivate.

Today I needed to do some work for a client - and suddenly Captivate is unable to start. I just get the message: "Adobe Captivate has stopped working. A problem caused the program to stop working correctly. (...)". No splash screen.

OBS: This is NOT the "Licensing for this product has stopped working" case.

I have tried
* to re-downoad and repair the installation
* to go through all services and check that all relevant services are running.
* following the instructions found in http://kb.adobe.com/selfservice/viewContent.do?externalId=kb401528
* searched for more solutions

The only changes in my PC's configuration are the Windows automatic updates - and possibly a Flash update.

Working environment: Vista Business english w. all updates incl. SP1 on a Dell Precision M90.

A solution is urgently needed!

In the meantime I have to use Camtasia Studio!

Bent
    This topic has been closed for replies.

    2 replies

    Bent_EAuthor
    Participant
    November 27, 2008
    Hi susannetic

    Thanks for the suggestion. I have disabled the Vista UAC a while ago because it drove me crazy: Every time I started Powerpoint (2007) I was prompted by the UAC. This started after I installed Captivate / Camtasia / Wondershare. I don't know which one caused the problem, but none of the vendors are able to explain why.

    I will return IF I find a solution sometime.

    Bent
    Known Participant
    November 26, 2008
    It may or may not have anything to do with your problem , but make sure that your user access control in Vista is disabled. I can't remember what the exact message was when I had a similar issue, but a clue would be a little vista shield on your shortcut. There is a thread that suggests going into the program file and starting from there, which worked until I figured out the UAC had been changed by my security program. I tried all of the things that you tried to no avail. There is a related thread somewhere in the forum that put me on the track for my issue. Hope your fix is that easy...