All existing projects suddenly locked, cannot save new projects (probably since v25.2.0 Build 58)

[Christian Leibig]

First experienced in Premiere v25.2.0 Build 58, might have been introduced a build or two sooner.

Steps to reproduce:
- Open any project or production

- [Open any project in that production (Note: the projects are not displayed as locked by any user)]

- Try changing anything in that project

Result:

The project panel has a small lock next to the name in the header, as do all sequences you open within that project. You can't create any new sequences or assets or change anything in existing sequences. Tried across multiple productions and project files on multiple backends (network share and local drive).

Everything works fine in release v25.1.0, as did it a day or two ago in v25.2.0 beta when I last tested a previous build.

Furthermore:
Creating a new (local) project file without any production gives me the following error message about permissions:
https://imgur.com/a/dRXI6AA
I can then make changes to that test project, but cannot save them, getting the same error message each time.

So it seems Premiere lost all write functionality to projects...great.

I know this is beta, but this is a complete showstopper and such basic functionality that I cannot wrap my head around how this can have happened again. The bugs you keep introducing every couple of builds are so catastrophic that they halt all testing and work. I swear if I had not started some test projects with the new color workflow I would have bailed on 25.2 by now.

[Bruce Bullis]

>So it seems Premiere lost all write functionality to projects...

PPro never alters OS-level user permissions, or storage read/write access.

The fact that no one else has reported this problem, and that thousands are using the same beta build without issue, makes us hopeful that the problem is specific to your system...

Confirming: You see this access failure in independent projects, not just projects within a Production, yes? 

Confirming: Same behavior, when attempting to save on local drives, or network drives, yes?
Confirming: Same behavior, when attempting to save to your OS User's home directory (to which you're pretty much guaranteed to have write privileges), yes?

Are you perhaps logging into that editing system, with a different OS User account (with fewer privileges)?

What else might have changed about your system, between the last time you were able to save PPro projects, and now?

[Bruce Bullis]

[updating status]

[Christian Leibig]

I'm not saying Premiere alters OS-level permissions, just that it is unable to write to any project, new or old. Maybe permissions was the wrong word, let's go with "ability".

Again, everything works fine in 25.1.0 release, so it isn't some general permission problem on my end. It's possible for another version of Premiere on my system to create and change projects, just not the latest v25.2.0 Build 58.

Yes, the issue is present in productions and existing independent projects. I described above what happens if I try to create a new independent project (unable to save). And yes I tried on local drives as well as network share. No difference.

I have full write access to the paths I'm trying, I'm the only user on this system. And again, 25.1.0 behaves correctly in the same environment.

A couple builds ago it was working fine, since then no change to my system other than updating the Premiere beta.

[Bruce Bullis]

Interesting!

Sorry for the verging-on-pedantic confirmation request below, but...is the following true?

1. Launch PPro 25.1 official release.

1. Create test.prproj in OS user's home directory (~/). 
2. Save project.
3. Close PPro 25.1.
4. Launch latest PPro 25.2 beta.
5. Open ~/test.prproj.
6. Add a bin or something; make test.prproj 'dirty'.
7. Save ~/test.prproj.
   
   Result: Failure?

[Christian Leibig]

Curious behavior, everything in the same session without closing Premiere beta:

If I reset Premiere completely (delete user folder and clear everything with shift-click on start), then I can create and save new (single) projects in my home folder and D:\Videos.

I then open a (local) production in D:\Videos and a random project in that production, and that project is locked completely as described above.

I then close that production completely, then try to create a new single project in my user folder or D:\Videos again (same as before) and it suddenly FAILS with the error from the screenshot above.

I then close and re-open Premiere and still cannot create/save new single projects with the error from the screenshot above.

Edit:
As for your scenario:
Opened 25.1, created a new project C:\Users\Christian Leibig\Documents\PremiereTestProject.prproj, saves fine.
Opened the same project in 25.2.0 beta and I canot make changes to it, it has a lock symbol in the header of the Project tab and won't let me make changes.

[Christian Leibig]

Continuing from your scenario:
- If I reset Premiere beta app preferences with ctrl-click I can open and save the test project fine.

- I then close Prermiere, open it again, works fine.

- I then open a Production (without touching a project within), and then load the test project from above again, and now it shows a locked symbol in the header and I cannot make changes anymore.
- Then closing and reopening Premiere. Test project from above is still unable to be saved (locked)
- Reset app preferences again, can save the test project again.

This happens regardless which Production I open in between. I've tried only local Productions in D:\Videos this time.

[Christian Leibig]

And a new test:
- Resetting Premiere app preferences with ctrl-click open.

- Creating a new Production in ~\Documents\Productions\ called TestProduction

- No error message, but no Production is opened, I only get a blank Premiere screen. The "TestProduction" folder is created with no files inside.
- Trying to open a production in that folder gives me an error, that the folder is "not a production".

[Bruce Bullis]

"not a production"  makes sense, if PPro was not able to write a .prodset file.

I propose to leave Productions out of troubleshooting, for now; they have their own project locking behavior, distinct from the failures you're seeing with standalone .prproj files.

We'd like to get a copy of PPro Beta's preferences; one copy from when you cannot save changes, and another (after you've cleared them) from when you can. 

Are you launching PPro Beta 'as an Administrator', on that system? 

[Christian Leibig]

Email has been sent.

I'm launching Premiere as my own user with a local Administrator account. Tried launching as Administrator user, but no change in behavior.

[Christian Leibig]

Sidenote:
Hail-Marying the preferences file from 25.1.0 into the beta user folder (and renaming accordingly) also immediately gives me "locked" single projects, without ever touching a production in 25.2

[stephen_eckelberry]

I woke up to the same problem.  Thankfully I was starting a new project so I just created it the non-beta app. Hopefully someone fixes it soon.

[TomSzy]

Having the same issue with Build 58. Haven't tried as extensive troubleshooting as others yet, but it appears to be doing the same thing. I tried making a copy of the project in productions and the copy did the same thing. When I turned off locking in preferences and try to open the original project it says "This project cannot be opened due to a file permisisons error."

Thanks for looking into it, Bruce! I'm sure you guys will have a fix quick.

[lukeripa]

Same issues here, given the production and its projects work perfectly on the stable release this is not an OS problem.

It definitely is a bug. 

[Christian Leibig]

v25.2.0 Build 59 fixed this bug for me

[lukeripa]

I confirm it's fixed with the latest update.