Greyed out Project file in Finder (MacOS)

[RogerAtCat]

My entire team is experiencing an issue seen before here on the discussions. Premiere Pro and Finder are greying out project files as if they are in use. You cannot open them nor copy/move them. It's maddening.

It only happens when Premiere Pro is saving to an external disk. 

The only solution I've found after hours of research is to release the files via Terminal.

Open Terminal and type: "xattr -d com.apple.FinderInfo dragged-and-dropped-file" and return. Bam, file is released and behaves normally. We're all on 14.4 Sonoma (and now 14.5) and Premiere Pro 24.3, 24.4, 24.5.

[Kevin-Monahan]

Hi Roger37563951vlpj,

Thanks for filing this bug report. Please check Privacy & Security System Preferences and check to see if the external drive needs to have its permissions adjusted in Files & Folder.

I hope that might help solve your issue. Let the community know.

Thanks,
Kevin

[Kevin-Monahan]

The status of this bug report has been updated.

[RogerAtCat]

I was on the road last week and I wanted to confirm with my team. We've all given Adobe applications full disk access and this is still happening across the board. Maybe it's auto-save holding onto the file?

Finder gives me the following error when I try to access these greyed out Adobe project files:

“MY PROJECT FILE” can’t be opened right now because it’s being used by another task, such as moving or copying an item or emptying the Trash. Try again when the current task is complete. 

[Kevin-Monahan]

Hi Roger,

Something is going wrong with Finder and interaction with these files. Are you using network storage or anything? What more can you tell me that would differentiate our workflows? I am on a similar Mac, with the same OS and version, but I do not see this. Let me know. I hope I can help.

Thanks,
Kevin

[RogerAtCat]

This is on my 2022 MacStudio M1 Ultra with GRAID 36TB SSD formatted APFS. I cannot speak for the rest of teams specific drives and laptops at the moment, only that this happens to us all when the Premiere Project files are located on an external drive and we are actively using the project file (it becomes grey and doesn't release, even after all adobe products are exited).

[Kevin-Monahan]

Hi Roger,

Are you in an enterprise or educational environment? If so, is the software installed by you or a network administrator? Let me know. I hope I can help.

Thanks,
Kevin

[Kevin@Caterpillar]

Kevin, 

We are in an Enterprise enviroment, and we are able to install our own software. We are thinking this might of become an issue with an update. We have FULL access to all of our drives at this point. This is more than one user having this issue also. I hope this helps. 

[RogerAtCat]

Enterprise maganaged Adobe login but we have full permissions and install our software on supplied macs.

When I run xattr in Terminal, I have uncovered the following which sent me down a rabbit hole.

xattr -pl com.apple.FinderInfo /Volumes/SSD/ASSETS/Questions.prproj

com.apple.FinderInfo: brokMacs000000000000000000000000

Finder labels the Premiere Pro projecrt files extended attributes as "busy being copied" by setting their file type and creator to "brok" and "MACS", making them inaccessible and grayed out. This label should be removed after the copying, but it persists. Erasing the com.apple.FinderInfo attribute removes this label, but the underlying issue is the unknown recurring reassignment of this label.

We are not using Finder when these files grey out; we are saving (or auto saving) within Premiere Pro. Does Premiere Pro utilize Finder for it's saving process? Kevin@Caterpillar tagging you too! 

[Kevin-Monahan]

Hello @RogerAtCat and Kevin@Caterpillar,

Thanks for the replies. Can you please connect with Enterprise support to get the support you are entitled to? I will move the issue to the Discussions forum for further troubleshooting. Sorry for the problem.

Take Care,
Kevin

[odedia]

This is not limited to Premiere, I just exported a Final Cut Pro X XML file from DaVinci Resolve 19 to an external drive and had the same issue. The command you shared solved the day!

[RogerAtCat]

Oh thank you! We've not seen the behavior elsewhere but I wil certainly try to trigger it so we can get Apple to do something about it. I've been going nuts trying to figure it out.