Skip to main content
Christian Leibig
Inspiring
December 19, 2024

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

  • December 19, 2024
  • 15 replies
  • 1228 views

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.

    This topic has been closed for replies.

    15 replies

    Known Participant
    December 21, 2024

    I confirm it's fixed with the latest update. 

    Christian Leibig
    Inspiring
    December 20, 2024

    v25.2.0 Build 59 fixed this bug for me

    Known Participant
    December 20, 2024

    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. 

    Known Participant
    December 19, 2024

    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.

    Participant
    December 19, 2024

    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.

    Christian Leibig
    Inspiring
    December 19, 2024

    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

    Christian Leibig
    Inspiring
    December 19, 2024

    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.

    Bruce Bullis
    Legend
    December 19, 2024

    "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
    Inspiring
    December 19, 2024

    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".

     

    Christian Leibig
    Inspiring
    December 19, 2024

    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.