Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

SONOMA & recent FCPX update is CONSTANTLY crashing

I updated my Macbook to Sonoma last week and installed the latest FCPX update.


Since then I have had nothing but problems with ALL of my FCPX projects.


The error I am getting is - 'Final Cut cannot save changes to 'project name'. The storage location for one or more libraries is no longer available. the libraries will be closed so that no work is lost'


and then 'Permission error opening 'Project title''


None of my libraries have moved. I've tried changing the permissions for FCP and that has not resolved the issue. I've tried deleting all the render files, optimised files etc and I still cannot do anything within these projects'. It will allow me to open older back up files and work on them however then I lose all my progress and if I continue to work in that project eventually it happens again.


HELP WHAT IS GOING ON? It will be working without issue one minute and the next minute the whole project file is dead. The first time it was triggered by importing an .mp3 (from inside the project destination folder) into the project but I can't see any links between what is making the program crash. One project I have been working on all week and after exporting a copy tonight it's decided it's dead.


I can't keep working like this across all of my projects.

8 replies

First, whenever there is a crash or the application misbehaves, delete its preferences.

To delete preferences, hold down command and option while starting FCP X and click Delete Preferences. The application will start in a default state, and open an "Untitled" library. Reopen the library you were working on, set the preferences the way you like them, and try again.

If the problem persists:


1) Make sure that FCP has "Full Disk Access" in System Settings->Privacy & Security


2) Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

What storage location is it looking for and can you access it?


I'm not sure how much help this is but the only times I've seen that error is the result of a flaky cable (or connector) to an external drive, or when a drive has unmounted, or the permissions on a destination drive get messed up.


I have seen that error when switching accounts on client's Macs though not very often.


Just for kicks, I'd trying running repair permissions/first aid on drives to see what you see.

It sounds like the libraries are on external storage. How is this storage formatted? FCP and Motion need either APFS for SSDs or HFS+ for spinning drives.

Is Sonoma another MacBook? ?

Sonoma is the most recent OSX

The version number should be 14...

It is... Sonoma 14.0...?

Thanks Luis! Deleting preference worked! I re 00004000 ally appreciate it!