Mac why are files locked

May 21, About the author. View All Posts. Jessica Thornsby Jessica Thornsby is a technical writer based in Sheffield. Add Comment. Click here to post a comment. Leave a Reply Cancel reply. We value your privacy We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. However, you may visit "Cookie Settings" to provide a controlled consent. Cookie Settings Accept All. Manage consent.

Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website.

We also use third-party cookies that help us analyze and understand how you use this website. If the box is not greyed out, simply uncheck the box and try deleting the file again. If the box is greyed out it means you do not have the proper permissions for the file. Access the inspector. Unlock the options. From here you can view the file permissions, but to change them you need to press the lock icon. This will prompt you for your administrator password.

Change the permissions for unlocking. Deselect the checkbox and delete the file like normal. Method 3. Launch the terminal. The terminal allows you to execute commands to the operating system with code. Change the lock status.

This should force toggle the files locked status. You can also drag and drop the target file in the terminal window to automatically enter the file path. Force delete the file. If all else fails, another terminal command can force file deletion. In most cases, this command will delete the file once granted administrator permission with the password.

Did you know you can get expert answers for this article? We have been manually kicking the out of the files to allow them to save. Its a bug in finder.

Kill finder and restart it and magically your locked files will no longer be locked. There are a few things at play here, one actually ticked me off a few weeks back as I have a bunch of users with the same issue with Creative Suite's files with Adobe Support pointing me to this article in terms of support. Basically they state that they support working on files locally and the rest is at our risks and peril,. The other factor is related to Mac OS's Finder, when users set finder to display a preview of the file, it gives the signal to Windows servers that the file is opened, thus causing a bunch of locked files.

I found that shifting the selection from the file to a folder after seeing the preview, will release the file. I do try to encourage our users that Adobe best practices are to copy the files local, do the work and then copy back to network drive. Not intuitive and adds extra steps.

Also leaves a few places for problems, like forgetting to put back on network or data loss on local systems. The preview has been a problem in the past but this is beyond that now. We may have it licked by turning off IPv6 on the fileshare server, but now time will tell. Oh boy. This morning I am getting reports that users are experiencing whole system lockups from Finder.

The Share was made read only on TFNas1, but they were still named the same. Late yesterday due to some confusion from linked files I decided to rename the share on TFNas1. See man SetFile — l --marc l. To definitely unlock a file, you would have to execute chflags nouchg,noschg FILE as if both flags were set and you remove only one of them, it will still be locked.

Mecki Mecki 4 4 silver badges 8 8 bronze badges. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end.

Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Linked 2. Related Hot Network Questions. Question feed. Super User works best with JavaScript enabled. Accept all cookies Customize settings.