I got this exact same problem after installing CS5-app.

I hope de-installing CS5-app reverts to the previous behaviour

Thanks for trying to help Rick,

Unfortunately, after removing Flash Pro CS5, re-installing Captivate, removing all Flash Players and installing the only Flash Player I could find (10.1), the problem remains.

I find it very hard to ignore this, I need the slide to look like what it will do when I publish as I am building the slide ..

This was working fine until yesterday .. there *must be a way to revert.  I guess I did not follow your instructions to the letter .. you said to install an *older version of Flash .. Do Adobe have an archive page? .. I couldn't seem to find it.

I really hope this gets sorted out soon.  I cannot log a Bug because I am only evaluating the software at the moment.  I want to put something really nice together to justify purchasing the software but this is going to make achieving that a lot more difficult - perhaps it is easy for some people to visualize what the slide will look like when it is published but I find this very difficult.

I have been really impressed with the usability of Captivate.  I tried Articulate and, although I am sure it is probably a decent tool, found it very hard to pick up and run with so I tried Captivate and found it very easy to hit the ground running.  This problem however presents a major hurdle .. especially since it was working fine previously

Got it working ..

The trick was to install an older version of Flash Player.

To do this I had to:

1. Follow the instructions in: http://kb2.adobe.com/cps/402/kb402435.html to de-install Flash Player

2. Get an archived version of the player from http://kb2.adobe.com/cps/142/tn_14266.html

I used version 10,0,45,2 and it worked for me

Thanks dparkeruk, your instructions worked for me too.

I am in the same situation and have been able to resolve.  Even saved ppt back to earlier MS version to see if that would make a difference.  No luck.

I tried uninstalling and installing 10.0.xx.xx but there's nothing there, no

Flash. Is there a doc that describes how to install, step by step, an

archived version?

I went back to 10.0.45.2 as Alan Partridge suggested. Uninstalling the 10.1 went ok due to the availability of the Flash uninstall pgm. however, installing a downversion was not painless. Based on something I Googled, I deleted all the references to Flash in the Registry which seemed to make the downversion install work.  Nevertheless, I'm back with 10.0 and Captivate is working as expected.

I am also experiencing this. The project publishes OK but affects my ability to create highlights and such on the slides prior to publishing. I installed the latest Flash Player, am using Windows XP Service Pack 3, Office 2003, and Captivate 4.

We are trying to go back to the previous version as indicated in this blog, but after we remove the new version and reinstall the old version, and then try to open Captivate, there is some sort of Flash player version check taking place. Since we do not have the latest version, Captivate 4 is no longer opening for us. We are all on Windows XP SP3, IE8, Captivate 4.0...

Anyone have any suggestions?

A very special thank you to dparkeruk for providing this solution.  It worked for me!  AMEN!! For complete success I recommend that users dowload the Adobe Flash Uninstaller and follow the directions to the "letter" ... making sure to RESTART your computer BEFORE attempting to install an earlier version of Adobe Flash.  NOTE: Adobe Flash Player version 10.0.45.2 worked for me.  My OS is Windows Vista Home Premium 6.0 (Build 6002: Service Pack 2).  For ever thankful for saving me from a complete meltdown ;-)  Pamela

Thank You!!!!

It worked!!!! 

I can see the slides again!!

Again, many thanks!   - Arnold

I followed the steps to uninstall 10.1 and reinstall 10.0.45.2 and it all now works fine. Thanks for the workaround.

This is also an issue with my IT. I keep getting 10.1 pushed out to my machine so I have to uninstall and reinstall the previous version on a daily basis. Has anyone heard any plans for a fix to this issue?