Corrupted all files within same folder

Hi, I'm hoping there's a fix to this but all the storyline 360 files within my project folder bring up the invalid or corrupt prompt when I try to open it. I saved it a few weeks ago and now it's impossible to open. Ive rebooted my computer and storyline is up to date. Even my backup file (within the same folder) is corrupted.

Please help!

6 Replies
Katie (Gokhshteyn) Riggio

Really sorry you're running into that error message, Jodie!

Let’s talk about some next steps to try:

  • Could you make a copy of one .story file in File Explorer, rename it, and then try to open it? Also, if it isn't saved somewhere on your C: drive, try copying it over to that local drive.
  • If that doesn't help, a simple repair of Storyline 360 should help.

While it's hard to nail down why files become corrupt, these tips can help mitigate the risk in the future. Additionally, there may be working versions of your courses in your temp files. Here's how to check and here's a quick Peek on the steps below for a visual guide: 

  1. Open this folder in Windows Explorer: %appdata%\Articulate\Storyline 
  2. Scan the contents of this folder for files that start with the name of your projects. If you find any, copy the latest versions 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.

Let me know if any of those ideas make a difference; I'll be here!

Ashley Schwartau

Has anyone noticed that Storyline freaks out and corrupts files that are a couple years old and maybe havent been used in a long time? It's happened to us on more than one occasion, that we'll go to open a client file from 1-3 years ago, to make some changes for them, and the file is corrupted, saying it may have been created with an earlier version of Storyline. DUH it was created by an earlier version. Why would it not work?? Are these files not forwards compatible?? 

Ashley Terwilliger

Hi Ashley, 

That definitely sounds odd, and I'm sure frustrating. You mentioned adhering to all our best practice guidelines, which is a good first step! And it sounds like from your other discussion, importing into a new project didn't fix it either? 

Are these files being opened in the same version of Storyline, and a new update? Or an entirely new version, i.e., Storyline 1 to Storyline 3? 

Everything should be forwards compatible, so it would help to take a look at one of your files and continue testing. If you need to share privately, send along to our team here and I can follow along!