Preview not working in Storyline 2


The preview functionality suddenly stopped working. It was working in the morning but suddenly the preview of all existing/new storyline projects show show a blank slide, irrespective of whether I preview a slide, scene, or project. Also the audio play function/preview is not working. Attached is a screenshot of what happens when I preview a slide. Also I have reinstalled Storyline 2 as well as flash player. Would be great if you could help.




305 Replies
Ashley Terwilliger-Pollard

Hi Cindy,

The fix isn't within Storyline, its within the different Windows updates related to Adobe Flash. If you're on Windows 8- you'll still need to use the rolled back Flash version, as they haven't released the update for that yet. If you're using Windows 7, Vista, 10 - you can update to the latest version following the steps here. 

Karen Drummey

I agree with Robby and Kris. I wasted time trying to figure out what was happening and if I had an email, I would not have. There are probably some people right now who haven't used their Storyline since this happened who are about wonder what's going on. I understand problems like this come up when it comes to technology, but not to get out in front of problems is not being transparent and not good customer service.

George Moureau

I agree with Robby, Kris and Karen, there should be an alert system in place for SL customers and perhaps that'll be a take away from this sordid little adventure...on the other hand, I also think Ashley and Leslie have done a great job working with us to resolve this problem, so I'll go half way and say customer service could add and alert feature, but I think it's been very, very good dealing with the immediate problem.

Ashley Terwilliger-Pollard

Hi all, 

We have shared that thought and idea with our team in regards to an alert and sending the info out to users. One thing is to ensure when you activate your software, that you choose the button to register it - as that allows our team to keep track and be able to contact users using that information. Lesson learned across the board here - and we're continuing to look at ways to improve our software based on your feedback and our communication in regards to updates, fixes, or known issues. If you have any other advice or feedback to share, please feel free to do so here in the forums or send along to our product team using the form here. 

Lizzie Angell

Hi Ashley

It is good how communicative people are on the forums, and I agree the service on here is great, but I would like to know what happens to the information put in to the 'feature request' forms, as I have filled out a few, and had nothing happen. - No feed back or response, may be just a comment that someone will look into it.

What is your process for looking through the 'feature requests' ?


Ashley Terwilliger-Pollard

Hi Lizzie, 

That's a great question - and one we hear a lot. The feature requests go to our team and they categorize and review them, but due to the volume received they are only acknowledged with an automatic response letting you know it was submitted and received. If there were additional questions or information needed, that may be when you'd hear back from them. Having them go through this system, while it may seem impersonal, does allow for us to track, categorize and keep them in a centralized location vs in a number of different threads or product sections. Once our product team has them, they keep them as they look towards working on updates and new product releases and determine how requests fit in with the road map (which we don't share publicly), and value/impact across our user base. 

We receive thousands of feature requests every year, so as you can imagine, not every feature request can make it to release. Many of the added features in Storyline 2 came about as a direct result of customer feedback.  Creating a public facing feature request page is something a number of users have asked about before, and there are many reasons we haven't done it yet but one is simply that features get added/removed/delayed throughout the development cycle. We continue to have this discussion in the forums and internally in terms of making this process a bit more visible, so our team is also looking into what that would look like and how we'd do so.  

Hope that helps bring a bit more clarity to the situation!