Cannot delete mac files windows server

Sometimes, if the reason for the file hangup is a Finder crash or anomaly of some type, this Secure Empty Trash process will also hang. The way to get out of this and back to work is to Relaunch the Finder, which if the Finder has hung up will be an option on the popup menu if you hold down the Command key while using the Right Mouse Button on the Finder icon in the Dock.

Obviously, the old standard fallback ploy of rebooting your machine will sever any ties to any running program no matter how tenuous, so restarting your machine can also do the job. The files may still be in the trash after restart, so restart and then go back and empty the trash again and the files should be gone. Most of the above options will usually do the job in the vast majority of cases.

How to Unlock a Hard Drive on macOS

If the files still persistently refuse to be deleted, it may be that their permissions have gotten mixed through some accident of machine storage timing. Use Disk Utility to check and repair permissions on the offending disk. And if all that fails to turn up any anomalies and fix the problem, you also have the ultimate nuke button option of going into Terminal and deleting the files with a UNIX command. Navigate to the directory concerned using the cd command. Use ls to list each directory until you find the file. Then type:. The rm command ReMoves the file. UNIX has no trash bin, so use this command wisely.

If you empty the Trash, the file will be deleted. Occasionally, you may find that a locked item made it into the Trash and now refuses to be deleted. In such a case, you may not even be able to drag the item out of the Trash. Apple claims that pressing and holding down the Shift-Option keys while selecting to Empty Trash should work here.

However, I have been unable to confirm this. If you put a locked file in an unlocked folder, you can drag the folder to the Trash and usually delete the folder and its contents, including the locked file, even though you could not delete the locked file by dragging it to the Trash directly. This method is a trick way to delete a group of locked files without unlocking each one individually.

Alternatively, if you select several files and then choose the Show Info command Command-I , you will get one Show Info window for all the selected items. The top of the window will say " of items are selected. When they are unlocked, the files can be deleted. Although the Locked checkbox appears, it is dimmed and cannot be selected.

So you cannot lock Mac OS X applications that are packages, because a package is actually a special type of folder as I explain in Chapter 2. Neither can you lock certain types of documents, including. You can still lock folders without needing to resort to Terminal, however. The shareware utility XRay allows you to enable the Locked option as well as the invisible and package attributes, also not available in the Show Info window.

Your Answer

The graphics and text are combined into a single document that is really a package. TextEdit saves files in this format automatically if you have a document that combines text and graphics. If you have too many alias files in the Trash at one time, you may be unable to delete them. The solution is to drag the alias files from the Trash and return them in smaller groups one at a time, if necessary. Then delete each group separately. You may get an insufficient-privileges or similar error message when you try to place an unlocked item in the Trash. Or you may succeed in placing the item in the Trash, but an error message appears when you try to empty the Trash.

The causes.

Subscribe to RSS

Some of the specific causes are similar to the ones that can prevent a file from being moved. After all, placing an item in the Trash is just a special case of moving the item. These causes can include not having write access for the file, as follows:. Having read-only access for a folder that contains the file you want to delete. This setting prevents you from moving the file from the folder. Note: Having read-only access for the file itself will not prevent you from deleting it. The settings for the containing folder matter more.

Similarly, if the sticky bit is set for a folder, and you are not the folder's owner, you will likely not be able to move items within it to the Trash. Regardless of what the permissions settings are, how the settings came to be that way, or why they cause trouble, your goal is the same: Delete the file. Usually, you can ignore the settings and focus on the delete task. The following procedures assist in this task.

Can't delete file/folder via Mac Finder | iXsystems Community

At least one of them will surely delete a problem file. Again, be wary of trying to delete system files that refuse to delete; usually, you want to leave them alone. Empty the Trash. If you try to drag a file to the Trash when a file with the same name is already in the Trash, the Finder usually renames the file that's already in the Trash such as adding a 1 to the name so that the new file can be added.

But the Finder may balk at doing this and block you from adding a file with the same name. If so, the solution is to empty the Trash and then drag the file to the Trash. Rename the volume or folder. The solution is to change the name to remove the characters. Further, if the volume that a file is on contains these characters, the file may also refuse to delete.

The solution here is to change the name of the volume.


  • freddie mac vs fannie mae vs ginnie mae.
  • windows 7 iso usb for mac.
  • How to Overcome the “File in Use” Error.
  • mac laptop buy now pay later.

If needed, you can change the name back after deleting the file. Create a new folder. Create a new folder, place the uncooperative item in it, move the folder to the Trash, and empty the Trash. Boot from Mac OS 9. Boot from Mac OS 9, and delete the file there.

Before switching to Mac OS 9, remove the problem file from the Trash and place it in a location that you can view easily when you're booted in Mac OS 9, such as the root level of your Home directory. Thus, if you do not remove the file from the Trash in Mac OS X, you will need to locate and move the file with a utility such as File Buddy that allows you to view and manipulate invisible files.

The Trash folder is called. Trash and is located at the root level of your Home directory. In the unlikely case that Mac OS X does not permit you to remove the item from the Trash, deleting the file in Mac OS 9 will again require accessing the invisible Trash location.

Use XRay or a similar utility. If you cannot delete a file because you do not have the needed permissions, open the file with XRay and change the permissions. Make yourself the owner of the file, for example, and make sure that the owner has both read and write access. Now you should be able to delete the file. BatChmod includes a Force Empty Trash command that automates this process and appears to work well in most situations. Use a delete utility. All my Macs are on High Sierra.

No issues. I have not tested this part out, but supposedly Might want to play with that. Apple doesn't play well with others period, they play by their own think different rules. That said, have not seen the issue you're reporting rgerman outside of one caveat. If people on Mac use cover view, having a file selected or previewed in any way is the same as having it open. We found this a couple years back and had to advise all users never to use cover flow because of that issue.

Temporary items hidden folder at the root of the share, that shld resolve it also. Its down to the cached fkle excel creates. You wouldnt have issues saving it as an non xlxs file.. Temporary Items folder. The issue seems to be tied to. Oncve the error comes up, the user is unable to save the file to the server or even locally. The only way to save the file is to change the save format to. Since, then I have not had any reports of the xlsx issue. Seems to be the only solution until Apple fixes the SMB issues.

There's a long list of incompatible characters that are allowed on the Mac, but not Windows that may be the cause here. One of the most insidious, is a space at the end of the filename or folder name. Some users just get into a habit of typing a space after everything they type, including when naming a file.

The following file names are also reserved under Windows: com1, com2, com3, com4, com5, com6, com7, com8, com9, lpt1, lpt2, lpt3, lpt4, lpt5, lpt6, lpt7, lpt8, lpt9, con, nul, aux and prn in upper or lowercase. Keep your filenames and folders to a reasonable length and be sure they are under 31 characters. Some operating systems are case sensitive; always use lowercase to avoid confusion.

Don't change the files extension ie. Please let me know if you have found any other examples or characters to avoid, or weird situations where normally legal characters cause issues. I had this problem the last 2 years and it is now solved!!! My configuration : - synology nas with smb, afp disabled - problem : sometimes i cannot drag and drop files and folders around from 2 of my mac's, sometimes I cannot delete files or folders - setup of the macs : latest version of Mojave So I made a test setup with a new synology share with a few folders, subfolders and files and tried to repeat the problem.

This share is on a newly installed synology nas, so there is no problem to be expected from that side.

No Really; Delete It

Trying to drag around files and folders I discover that I have the drag and drop problem on 2 macs but not on a third mac. The mac where everything works flawlessly is configured exactly like the other 2 : Mojave On this third mac I can drag and drop files and folders on an SMB share without any problem. So I thought : maybe I should reinstall the mac and I reinstalled but the hard disk was not formatted so my user and files were still present. Dragging and dropping files is working perfectly now. I will now let this newly installed mac run for a week and if no problems surface, I will also reformat and reinstall the other bad mac.

Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. Learn more about JNUC. Like Comment. Order by: Most Likes Oldest Newest. We're having exactly the same issues. This is a drama, as most of our users are not local administrators of the machines. Anyone out there have any ideas? I bet someone has the files or something within the folders open when these issues occur. Although individual users cannot set or alter ACLs, server administrators can do so. Administrators can use the SMB server command line to manipulate ACLs, but only if both the client and server are bound to the same Active Directory domain.

However, enforcement of permissions is done only on the server, not on the client. I know this is ages after the problem But I have a answer. My fix. Set ownership on all drives. Problem solved. Hope this helps good luck to everyone else. It's down to the fact that someone has something open right enough! Thank you. Is disabling the Preview the only fix for this. Open that file from one Mac client 1 in Preview. Open the same file in Preview on your other Mac client 2. From client 1 go into the Finder and delete the file.

Finder will not complain and the file will be deleted. On Isilon, you'll see that the file has been renamed to. On client 1 close Preview.

LockHunter is a foolproof file unlocker

On client 2 close Preview. And thus you now have an orphaned. The only way to close the open files is to dismount it on the Mac. Not saying this is the only cause for this type of behavior, but something to be aware of.