Skip to main content
P
patrickhagot
Inspiring
November 6, 2011
Answered

The project could not be loaded, it may be damaged or contain outdated elements

  • November 6, 2011
  • 16 replies
  • 87975 views

Please I need Urgent help!

I was working on a project when i saved the project then while closing premiere pro the electricity went off with the UPS and the desktop turned off and when i wanted to launch my project back I have this message:

"The project could not be loaded, it may be damaged or contain outdated elements"

Please is there any solution for this problem. My project is very important.

Thank you all.

      Correct answer Kevin-Monahan

      Hi,

      This is a legacy thread and the OP has not returned.

      When you have a project that is physically damaged, there are few solutions to revive it. You must use a back up that you expressly saved or one from the Auto Save folder. Sorry.

      If you have this issue, please create a separate new post to describe your issues. This post is over 5 years old now and may not describe your exact issue.

      Note: If you are experiencing this issue with Premiere Pro CC 2016 (11.0 or 11.0.1) on Mac OS and are sharing projects, see the known issues document.

      Thanks,

      Kevin

      16 replies

      Show previous replies
      S
      serpentone
      Participant
      May 5, 2013

      Man, I wish I knew about this before leaving my project to render last night w/ autosave activated... coming back a few hours later to find that not only is my 100+ hour project corrupt, but all the autosaves are corrupt and even the one back up I made earlier in the day ... which was fine when I made it ... is corrupt. Nothing is working, short of stepping back a full day's work.  It seems like the further you get in a Premiere Project, the more likely something will go horribly wrong. I am going to turn off autosave in the future because I do think that it has something to do with the problem.

      M
      miorta
      Participant
      May 5, 2013

      I think this has to do with Colorista because I only get this problem when I use Colorista with premiere.

      The autosave feature will not restore the corrupted project. However I keep my Premiere projects inside a dropbox folder from which I can access every saved (or autosaved) version of the project. Restoring the project from the previous version in dropbox will load the project correctly.

      I think Colorista should not be used with complex Premiere projects. But it can be used in AFX and dynamically linked to Premiere.

      E
      excited_Genie16B8
      Legend
      May 6, 2013

      I've been using Colorista for years and have no issues with it.  If it is causing you an issue, it's not normal.

      A
      akkcorduroy
      Participant
      April 1, 2013

      I have had this happen to two projects so far with no explination whatsoever. 

      We have pluraleyes for premiere as an extension in premiere... perhaps this is responsible?

      R
      RZeemering
      Participating Frequently
      April 3, 2013

      This just happenend to me too
      I am not using Looks or Colorista. But i am using pluraleyes. Though not in this particular project. I have a lot of different Zoom audiotracks manualy under the videotracks.

      I will try to open in on another computer or open it on my backupsystem wich i saved yesterday.

      M
      miorta
      Participant
      December 20, 2012

      I'm having the same problems today each time I reboot my computer.

      This is what I noticed.

      1. My project contains dynamic links to AFX, so opening AFX to load the linked comps can help in some cases. Sometimes for some strange reason I need to relink some footage.

      2. My premiere project is placed in a dropbox folder. Luckily dropbox tracks every single saved version of the file on the internet. Restoring a previous version from dropbox works, while restoring from the premiere auto save folder doesn't work.

      N
      Neptunesalad1
      Participant
      January 19, 2013

      I have been having this problem routinely for a few months. I am running the newest version of Premiere Pro CS6, and I do use Colorista II for color corrections. I have gotten into a routine where I save multiple copies of every project so ONE will work. It's really annoying, because it often gives me this dialogue box after I've properly saved a project and then go to open it back up later that same day. Any advice to prevent this is greatly appreciated - but I hope I can still use Colorista II for color correction!

      P
      patrickhagotAuthor
      Inspiring
      January 19, 2013

      I sincerely from all my heart advice u to not use Adone Premiere Pro CS6.

      Go back to their best cs (5.5) and u can enjoy editing and enjoy colorista and enjoy saving. I have been using cs5.5 since it was launched and i never faced any bugues!! Finish ur last project and go back to it. Otherwise u can now in the middle if a project go back to the last version.

      Let me know of what u will do.

      Good luck.

      G
      Gahkue_NWT
      Participant
      December 19, 2012

      I had the same problem today - I'm using CS6 and I got that warning, I copied my project file on usb stick and re-opened in a different computer using CS5, it then gave me a few warnings about changing the name and saving it to auto save fault, I clicked away and said yes to each one, I re saved it to my desk top then copied that new file to my usb stick then brought it back to my main computer with CS6 and it opened and I was able to finish my work hope this helps  


      R
      RZeemering
      Participating Frequently
      April 3, 2013

      How can you open an CS6 project in CS5? My CS5.5 gives a warning that the projectfile i am trying to open is a newer one than i am working on. And sends me back to the open file window.

      I also tried opening the file on another computer. No succes

      I also tried to open the file on my back-up system. No succes.

      version 0.8 opens on both systems fine. But version 0.9 does not.

      I noticed one strange thing though: I went away from my studio at 19:45 and the corrupt file was saved on 20:05. I am absolutely sure i was not in the studio by that time. I did start a render before moving out of the studio.

      Could a self save from premiere cause the problem? By this i don't mean the autosave.

      edit:

      the last autosave was from 19:02 and openend fine! phew i only miss very few cuts...

      But it gets me very nervous, i think i will now double save different versions... not only 0.9 but also 0.91

      E
      excited_Genie16B8
      Legend
      April 3, 2013

      How can you open an CS6 project in CS5?

      You generally don't.  Project files are forward compatible, not backward.

      Could a self save from premiere cause the problem? By this i don't mean the autosave.

      Autosave is the only kind of 'self save', and is not likely to 'cause' project corruption.

      D
      dkaplowitz
      Inspiring
      November 8, 2012

      I've just had this problem as well, Premiere Pro 6.0.2. Not acceptable Adobe - this wasn't so bad as I've only lost 30 minutes of work and yes I should have had my auto save set to 5 min or something but for a project to just up and not open out of the blue? That's simply not falling into the "professional software" category, and combined with other problems I'm now having with Premiere Pro 6.0.2, I'm considering dropping the software altogether and just moving to Avid.

      N
      Nellyvader
      Participant
      November 29, 2012

      I just woke up this morning to the exact same problem. A project I was working on last night will not open this morning. I get the "damaged/outdated elements" dialog box. Thankfully I do have Auto Save turned on and I only lost a small amount of work but this is the second time that a Premiere project has suddenly become unusable.

      I do have a couple of factors worth mentioning here:

      -I downloaded trial versions of the following software and was using them last night:

      -Film Convert Premiere Pro plug in

      -Film Convert stand alone

      -Technicolor Color Assist stand alone

      -I have Magic Bullet Looks 2 plug in installed in full version and was using that too

      Thanks in advance for any feedback.

      Niels

      D
      dkaplowitz
      Inspiring
      December 3, 2012

      Nellyvader, I have a feeling you may be on to something there with the plug ins - i have a feeling it was a trial version of Magic Bullet Colorista that could have casued the problems. I have no proof however, just a hunch.

      Wil Renczes
      Adobe Employee
      Wil Renczes
      Adobe Employee
      November 6, 2011

      Have you looked for an autosave backup?

      C:\Users\<username>\Documents\Adobe\Premiere Pro\5.5\Adobe Premiere Pro Auto-Save\

        P
        patrickhagotAuthor
        Inspiring
        November 6, 2011

        Yes i did but the last autosave is too old. I must find a solution for the project that don't want to open!

        A
        Alan_Craven
        Participating Frequently
        November 6, 2011

        Try opening a new project with the same settings and then import the old project into that.  If that fails try to import just the sequence that you need to this new project.

        For the future, check that Autosave is turned on on the appropriate section of "Preferences" in the Edit menu.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices