How can I verify my product is corrupted?

Help! 4 months' worth of work is showing signs of corruption, and I thought I was doing everything right. I'm at the point where I need to decide to: re build or continue and pray it works. What do I do? 


The ONLY thing I didn't follow from previous discussions about avoiding this, is I didn't use a proper naming convention. I've saved often, saved to a new name everyday, and saved to a local drive only. 

8 Replies
Ali Goulet

Hi Joanne,

What signs of corruption are you seeing specifically? Are you seeing these issues happen only with that one file in particular or are they happening with any .story file that you work on? Importing your slides into a new file may fix them if the former is the case, or you may need to repair your software to fix erratic behavior if the latter. 

joanne k

Last week, everytime I tried to copy a text box, to paste elsewhere, it would freeze up my project and shut it down (Storyline 2). 

Today, in the middle of making some changes, before I had a chance to save them, the project totally locked up on it's own. I couldn't even close it out, I had to open my task manager and shut it down from there. 

Is it possible to have a corruption just from improper naming? I had spaces and dashes in my names? 

And, I've got only one project going at the moment, so I cannot compare to other projects.

I just read the info regarding "repair": if I follow the instructions to uninstall Storyline, and then reinstall it, will I lose my projects saved on my hard drive?

joanne k

I'm hoping the uninstall/re-install with new update will fix the issue. I also was able to send in a help ticket to Articulate, to see if they are able to tell if my project is definitely corrupted. If it is, I have to start over from scratch....correct? I can't import any of the scenes/slides into a new storyline because I'd import the corruption, correct?

Leslie McKerchie

Thanks for mentioning that you are working with support as well. You are welcome to share the case number and I can follow along as well. Importing in a new file works for some and does not necessarily bring the corruption along.

Also, there may still be a working version of your project in your temp files. Here's how to check:

1) Open this folder in Windows Explorer: %appdata%\Articulate\Storyline
2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
3) Change the file extension of the copy on your desktop from *.tmp to *.story.
4) Double-click the file to open it in Storyline.
File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting). Consider using the preventative measures described in this article to protect your project files.
joanne k

Here's the case info: Case #00873171: My product may be corrupted, is there any ... [ ref:_00D30Txo._50033zQ2TJ:ref ]....I copied the entire Subject line!

Thank you, Leslie, for the information above. I've copied the latest version, from yesterday afternoon, to my desktop and will continue to work with my IT person here to ensure a full and correct update has been done on my computer as well.