Community Manager

Premiere projects saved in v25.6.0 cannot be opened in other v25.x versions

Forum|Forum|2 years ago
September 5, 2023
168 replies
12054 views

We are aware that customers who saved projects in Premiere v25.6.0 may find that those files now open only in v26 (beta) and cannot be opened in v25 versions. We know this is disruptive, and we’re working on a fix.

What you need to know:

Projects saved in v25.6.0 save in the v26 version format.

Because of this, they can’t be opened in earlier versions, including v25.6.1 (even though it is the current generally available release)

We’re developing a tool that will let you convert affected projects back to a v25-compatible file.

Our Solution

We’re building a small app that will convert a v25.6.0-saved project back to the v25 format. We’ll share more information, including availability and instructions, as soon as the tool is ready in the coming days.

We know that there is nothing more important than the reliability of a project file, so we’re working with urgency to get this downgrade tool in your hands as quickly as possible.

We know there are a number of downgrading apps available online, but we strongly recommend utilizing our tool when it becomes available. Non-Adobe apps and scripts are often outdated and may cause crashes and data loss.

Further Details

A bug caused Premiere v25.6.0 to prompt customers to enable Object Masking even though it is not yet in full release. Object Masking (and our yearly major version update) changes the Premiere project file structure such that it can only be opened in v26, which is only available in public beta. Turning this on caused projects to save in the newer v26 project format, even though users were still technically on the v25 release line.

Opening an older project in v25.6.0 triggered a prompt to save a copy of the project with “_1” appended. We know that many customers upgraded the project and continued working in the new copy, potentially also deleting the original. This means the only active version became the file saved in v26 format.

Premiere 25.6.0 was only available briefly before being replaced by 25.6.1 and is no longer available to reinstall. This means impacted users who auto updated to 25.6.1 cannot open v26 formatted projects.

Show previous replies

MeKevinB

Known Participant

R Neil Haugen My guy, the reason I said rolling back to 25.5 is the easiest solution is BECAUSE IT WORKED!!! My project opened up as if none of this happened. Project files are zip files blah blah okay great, cool. Hacking header information will never be easiesr or more practical than simply rolling back to the previous version. And thanks for the permission to disagree with you.

federicovolter

Participating Frequently

I've been working with v25.6.0 and now I can not open my own project with v25.6.1. It says it was saved with a newer version. The only solution is to work with the beta version but this is outrageous!
Are they going to fix this or we lost the chance to work whith these project in the non-beta versions? HELP!

M

Melion

Participant

I have the same issue. I upgraded to 25.6.1 and the project can't open.

This message appears even when I try to open the autosaved versions.

Can you help me pls.

P

pranayrupani

Participant

I am getting the same error even thugh I updated to 25.6.1 (Build 2) I have lost access to all my projects and work as a result. Especially the ones I started working on yesterday, projects created in this new version.

A

ameer_1264

Participant

Hello to the entire Adobe community,

After updating from version 25.6 to 25.6.1, I am unable to open my previous work files in the new version. I have tried restarting the application and checking for any compatibility settings, but the issue still persists.
Could it be possible for Adobe to investigate and fix this issue as soon as possible?

Thank you in advance for your help.

C

chindhu_7290

Participant

Hello to the entire Adobe community,

This morning, when I opened Adobe Premiere Pro, none of my recent projects managed to open. Instead, an error message always appears. This issue occurred right after you performed the last update.

This bug completely blocks my workflow and literally prevents me from working.

This is all the more unfortunate in view of the new tariffs that have just increased.

Could it be possible for Adobe to investigate and fix this issue as soon as possible?

Thank you in advance for your help.
Yours sincerely.
CK

Alexander_DVA

Adobe Employee

Thank you for reporting this issue.

The cause of this is opening a project with the 25.6.0 version first and then with 25.6.1.

The 25.6.0 version had a problem where it prompted users to enable features that are still in beta - which caused a version update of the project.

As a workaround you can install the current Premiere beta version and open the project with it - then you can copy-paste your content from the beta to the 25.6.1 version.

Best regards,
Alexander

Y

Yks Yakusa

Participant

Bonjour à toute la communauté Adobe,

Ce matin, en ouvrant Adobe Premiere Pro, aucun de mes projets récents ne parvient à s’ouvrir. À la place, un message d’erreur apparaît systématiquement. Ce problème est survenu juste après avoir effectué la dernière mise à jour.

Ce bug bloque totalement mon workflow et m’empêche littéralement de travailler.

Cela est d’autant plus dommage au vu des nouveaux tarifs qui viennent d’augmenter.

Serait-il possible qu’Adobe examine et corrige ce problème au plus vite ?

Merci d’avance pour votre aide.
Bien cordialement.

R Neil Haugen

Legend

Disagree all you want, but you cannot simply use a project with a 26.x file number in the header in 25.x ... so how are you proposing to do so?

That header has to be changed. It takes about a minute or so to do so. Far less time than posting here about it.

I'm simply suggesting there is an easy, totally safe and fast way to get all your projects usable again. Do what you want, of course.

Everyone's mileage always varies ...

MeKevinB

Known Participant

R Neil Haugen I'm going to respectfully disagree with you. By far the easiest solution to this absolute dumpster fire is to simply roll back to the most recent stable version -- 25.5. Extracting project files and editing XML code is niche.

R Neil Haugen

Legend

Unzip the prproj file. Change the version number, it'sin the header section. Re-zip the project file.

There are instructions online for this and it's more reliable and a TON faster and easier than tge rigamarole they told you to do.

Everyone's mileage always varies ...

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded