Skip to main content
Inspiring
December 3, 2017
Answered

Project could not be loaded, it may be damaged or contain outdated elements.

  • December 3, 2017
  • 11 replies
  • 70968 views

I've suddenly been receiving this error out of no where, on every single project file I have. I have not updated in the past few days, I opened projects just fine within the past day, and now I can't access anything.

Premiere 2018, v12.0.0

The only thing that I've done or changed in the past few days is logged into my creative cloud acct, and now I'm getting issues. Any help?

- Dan

    This topic has been closed for replies.
    Correct answer danj48796966

    No access to another computer at the moment, creating a new project and saving it allows me to open it again without issue.


    Found a solution for it, here's the steps I took.

    - Closed all adobe programs
    - Open Creative Cloud, sign out

    - Restart computer

    - Open Adobe Program, sign in on the prompt. Everything seems to be working now.

    Signing out/in in any other order didn't solve the issue. Not sure if there is some issue with file syncing, even though none of the files are pulled from my Library, but figured I'd share what I found.

    11 replies

    Kevin-Monahan
    Community Manager
    Community Manager
    January 28, 2022

    Hi Community,

    If you are getting this error, I am so sorry. For sure, upvote and comment on the following bug report to alert the product team.

     

    https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38198878-restored-premiere-pro-project-won-t-open-the-pro

     

    The issue is somewhat uncommon but can be triggered for various reasons. The errors are usually related to optimizing, organizing, and handling files. The OP, danj, solved their problem, so we will lock this post for now.

     

    If you have specific needs related to this error, please create a new post with detailed info about your system, your media, and screenshots of your project. 

     

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Participant
    January 28, 2022

    Older post, but just had this happen to me on PrPro 2022. I opened my most recent auto save from 5 minutes prior and everything opened okay. I had saved changes to a custom workspace and now am no longer seeing that workspace..I think that may have been the culprit.

    Inspiring
    July 31, 2019

    I have the same issue, I´ve tried all alternatives, please, Can you help me?. I use Mac OS X Sierra 10.12.6 on an iMac.

    I´ve tried the rename method of the Adobe Commons folders and the autosavings are so far away from my last result.

    Participant
    February 11, 2020

    I had the same issue after moving some linked video to an external harddrive. Updating Premier from v13.1.5 to 14.0.1 resolved the issue for me.

    Participant
    July 10, 2019

    On macOS, you could see an error message which says, "This Project contains outdated elements."

    Issue: When working on macOS, you could see an error message that says "The project contains outdated elements."

    Workaround: Rename the “Creative Cloud Libraries” folder located under User\username\ library\application support and load the project again.

    Known issues in Premiere Pro CC 2017

    jonathanb92735259
    Participant
    August 30, 2018

    I'm dealing with this same issue right now.  Last thing I did was add a morph transition effect and when rendering that, I got an error.  So I restarted Premiere, or tried to, but my project wouldn't open.  Adobe support had no solution for me.  Nothing is working.  I lost so much work and have to deliver today.  Did anyone have any other things I might try?

    Participating Frequently
    August 31, 2018

    The first thing I can think of at the moment is trying to open one of the auto-save versions of the project.
    Have you tried that?

    slowrider
    Participant
    August 11, 2018

    I am having this same issue, I've tried the following with no success:

    1) Tried different PCs and Mac - Error occurred.

    2) Turning Media offline - Error occurred.

    3) Last 5 Autosaves are corrupt.

    4) Tried importing sequences to a new project - No result, froze.

    I need this project out the door ASAP, and there is no time to redo the work and can't not call adobe support over the weekend.

    Anyone have a solution? I will transfer you money.

    Community Expert
    August 11, 2018

    Hi mikbrad,

    I see you have said you've tried different computers. However, if you'd like to contact me direct with the Premiere file, I can test if I can open it.

    Dean

    Participating Frequently
    April 5, 2018

    I found another solution!!

    Short answer: Don't use CC Libraries.

    Long answer:

    I had the project on my computer and it was possible to open it, but when I moved it to my external harddrive I couldn't open it.

    So this is what I did:
    I copied the whole folder to the external harddrive.

    I opened the project file from the external harddrive.

    I relinked all the files in the project file, from the computer, to the external harddrive.

    I selected all the objects in the "CC Libraries" folder (that was in my project folder on my external harddrive) and moved them into my graphics folder (which also is in my project folder on my external harddrive).

    I then went back to Premiere Pro and imported them from that graphics folder and manually replaced all the icons in the timeline that I originally downloaded from the CC Libraries.

    Then I deleted the CC Libraries elements in my project folder inside Premiere Pro.

    Then I deleted the project folder on my computer, then I closed and saved the Premiere Pro project.

    Hope it helps!

    danieli89270312
    Participant
    March 10, 2018

    I tried fixes suggested here and other places and nothing ever worked.  I finally installed a previous Premiere Pro version - 2017.1.2 Release - and my project opened with no issues (when you are in Creative Cloud looking at Apps - you can no click on the drop down menu beside each App and install "Other Versions").

    So... Adobe please make sure all future releases of Premiere Pro can open project files from previous releases. 

    No brainer, right?

    Participating Frequently
    March 27, 2018

    Hey there, if you open a new project and then go to File/Import and then select "sequences" it will let you bring in your old project piece by piece. You cannot import the whole corrupted project unfortunately. But at least if you have the sequences you will have all your "editing" work back.

    Participating Frequently
    March 28, 2018

    I tried that (create new project, import the old project and select sequence piece by piece) and I'm getting stuck at the import.

    It just freezes.

    How can Adobe even make an update without testing if you actually can open the project??
    This is just ridicoulus!

    Any other solutions found on this topic? I now have 93 projects I can't open...

    Known Participant
    February 5, 2018

    Problem NOT solved for me.

    macOS High Sierra V10.13.3

    PPro V10.12.01

    project started Feb 1st, now, Feb 5th, I receive the message

    Project could not be loaded, it may be damaged or contain outdated elements.

    Although I have followed all the steps as mentioned in the 'correct answer' reply, I even did reinstall HighSierra, those don't help me solve this issue.

    I don't have to add my mental status at this moment .... :-)

    Community Expert
    December 3, 2017

    Are you on Windows or Mac? How are you opening files?

    I experienced a problem with Windows Premiere saying the file is damaged when I opened my project file by double clicking it. However, it I opened Premiere first, then opened the file, it worked.

    Inspiring
    December 3, 2017

    Working off Windows 10, Just tried opening both ways with no success.

    Peru Bob
    Community Expert
    Community Expert
    December 3, 2017

    Just a long shot:

    Make sure that the file extension hasn't been changed somehow.