Principal Product Manager

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

Forum|Forum|2 years ago
September 5, 2023
172 replies
20354 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

B

Brentfilms

Participant

Autosaves are not working any better than the original project. However, I was able to open my project in Premiere Beta 26.0.0 (Build 31) and saved with a new name. Then tried to open in 25.6.1. I still get the "newer project" error and can't open. Would be nice to work in a version that's not Beta, but I guess beggers can't be choosers.

Peru Bob

Community Expert

You're welcome.

S

Sertão Play

Participant

Preciso de ajuda. O meu premiere está apresentando erro ao tentar abrir a versão de um projeto que salvei ontem a noite. Ocorre que não houve atualização de dowgrad, entretanto o porjeto informa que foi criado em versão mais recente.

R Neil Haugen

Legend

I'm assuming you had installed 25.6.0. Then perhaps tried to use 25.5 or the replacement 25.6.1. And got this message.

The problem is that 25.6.0 changed the project file header number for Premiere version from 25.x to 26.x ... which is only available at this time in the public beta version. Which anyone can install alongside the 'normal' release.

So you have three practical options:

1) Install the 26.x public beta, and work the project in that.

2) look in your autosaves for one that will work in 25.6.1 , and hopefully you don't lose too much work, or ...

3) look online for the process to manually change the project version in the project file header. Which is actually very easy and fast to do.

Project files are zipped files, and if you unzip them, you can actually read the data there. Near the top is a number that is to Premiere the major version number. Change that to the number for the 25.x series, re-zip the file, and it will work in any 25.x build.

There are specific instructions online for which number on which line to change. Takes a minute or two.

Everyone's mileage always varies ...

M

mattlth

Participating Frequently

@Peru Bob: Thank you! Installing the beta got me working again, which means the 12 hours I spent editing over the past two days weren't wasted.

Also, for anyone following, my Workspaces didn't come over in the beta, even with the Import Workspaces from Project option enabled. I'm on macOS, so I had to copy the ArchivedLayouts (folder), Layouts (folder), and LayoutsWorkspaceConfig.xml file to:

[drive name]>Users>[username]>Documents>Adobe>Premiere Pro (beta)>26.0>Profile-[Workspace name].

That way, I didn't have to rebuild a new Workspace.

Thanks!

Peru Bob

Community Expert

@mattlth

Try installing the Beta version.

M

mattlth

Participating Frequently

I just installed 25.6.1 (build 2) on two different machines, and neither will open the projects I worked on yesterday in 25.6.0. I also tried opening the most recent auto-saved project, and those won't open either.

R Neil Haugen

Legend

Note, that I'm another user like unto thee. 😉

Everyone's mileage always varies ...

A

Agrarvolution

Inspiring

I continued to work with 25.6, cause I didn't think it was such a big deal until I found the above statement. After I downgraded back to 25.5 I also downgraded one of my projects. I could work with it in 25.5 but after updating to 25.6.1 I can't open it anymore. If I open it with the Beta 26.0 it just works.

It's great that this was a known issue and you just didn't push an alert to everybody via the Creative Cloud app who has installed 25.6. Shouldn't this be super easy since we are forced to use that Create Cloud thingy anyways. Would have saved a lot of headaches instead of somehow getting wind of it in the forums, where only the die hard users look.

R Neil Haugen

Legend

Did you open this in the initial 25.6.0 release of a couple days ago? If so, that's the problem.

Everyone's mileage always varies ...

L

Lawrence_Chok1670

Participant

Just updated to the 25.6.1 update, and now I can't open any of my projects!

Doesn't help when you are working on urgent client work!
This keeps popping up.