How to abort Resume Copy on Monterey?

Sorry Apple is not being helpful. This is definitely STILL a problem in June 2022.

I put 400Gb on our work NAS, and then the file transfer failed at 90%. It may have something to do with how the NAS is set to handle permissions for file read/write/execute while transfers in progress. a paused transfer isn't marked as "complete" so its in sort of a permissions purgatory. That is quite a bit deeper than my understanding goes.

Simply, my option is 1-resume or 2-resume later. You cannot delete the paused download the easy way. The files that managed to copy are FOR SURE occupying space on your drive.

To DELETE it:

open a terminal window on your mac.

enter this information (but do not press enter yet):

sudo rm -r -f

then drag your useless paused download folder to the terminal window. This will insert its path into the command, and you won't have to figure that out yourself. Note: there should be a space between "-f" and the inserted file path.

Press return. You will be prompted for your password.

-------

If you need to access something in the folder, it is possible (before deleting of course).

To access content in the paused download folder:

Right click on it, select "make alias" and then open that alias that will appear on your desktop.

"If you need to access something in the folder, it is possible (before deleting of course).

To access content in the paused download folder:

Right click on it, select "make alias" and then open that alias that will appear on your desktop. "

Bingo. This solved my problem. I had a 1.2TB transfer that was 98% done that got interrupted, and when I tried to resume it either gave me an error code or tried to start over. Created an alias, which then gave me access to all the files. Moved them to a temporary folder, deleted the greyed out "resumable" copy and alias, and then manually copied over the remaining files. 10/10, would make alias again.

So I think I just solved this. After pulling out every last one of my hairs, having my case escalated to 3 different Apple tech support people, and spending HOURS on the phone with them, they basically said there was not a solution. However, I just stumbled upon one. I can't tell you how aggravated I am at the whole situation which has caused me to get to this place, but try this:

Take the Resume Copy folder and drag it to the trash. Once in the trash, do a Command-I to Get Info on the folder that has been paused. When the Get Info box comes up, click on the little lock on the bottom right to unlock it. Then, drag the folder out of the trash onto your desktop. It should, once copied/moved to your desktop, then actually show all of the files that had successfully copied to the folder because it was paused, and you can do with them what you wish.

Wishing I'd figured this out before I deleted several Resumable Copy folders that seemed otherwise absolutely useless, though they contained in some case hundreds of GB of data that I'd spent hours copying before Error Code: -36 rendered them all useless. The amount of hours I've spent trying to migrate data from one EHD to another because of 1.) the M1 chip not playing nicely with my ExFAT drive, 2.) Error Code: -36 and 3.) The lack of a solution regarding accessing the Resume Copy folders is absolutely obscene. Not a happy Apple camper right now.

Just had this happen to me. The "safer" way:

* Select the resumable copy of the file/folder in the Finder

* File -> Get Info for the item

* Check the little lock in the bottom right of the Info window

* Authenticate

* Close window

* Delete resumable copy of the file/folder using the Finder

* empty the Trash.

Seems weird to me, but it worked.

@NewCreationPhotography thank you for posting this! Apple is not the same company it used to be. I tried your fix and it didn't work for me at first. But I eventually got there. I had to LOCK the folder first, then drag to the desktop, then unlock. Then I double clicked the folder and it gave me an option for using the partially copied folder. Now I have access to the folder. Sheesh.

flashvenomdesign wrote:

WARNING

>sudo rm -r -f

Just seeing this command makes my hair stand up... I'm not an expert, so maybe someone will correct me, as I'm sure most advanced users know this, but just so everyone else knows, the "sudo rm" is a delete function that has the ability to completely delete ALL your files if you don't specify WHICH folder/file to delete, so use extreme caution. @longlegcraig should probably BOLD the "do not hit enter yet" or better yet put

sudo rm -r -f [dragandropfilepath]

As leaving that blank will delete whatever is inside the folder your terminal cursor is currently on, which by default is your home folder.... Many many stories of people typing in sudo rm -rf* and deleting all their files!

You are absolutely correct to the dangers of using the "rm" command with "sudo" (especially with the options used in the post). The "rm" command is dangerous enough as it is, but adding "sudo" gives it god like powers to potentially do even more damage if a user makes a mistake (even a seemingly innocent single character typographical error). People should never blindly enter Terminal commands found on the Internet without understanding exactly what the command does and the consequences of a mistake.

There are no safety nets when using the command line, so users should always be extremely careful since even veteran command line users can easily make a mistake with this command.

Dragging & dropping the item onto the open Terminal window as you suggested is the safest option to ensure the best chance of telling the command the exact folder (and subfolders) you want deleted. It minimizes the already great risk just a bit.

Thanks for taking the time to point this out since many users seeing this will not be aware of the danger involved.

I would suggest making sure to have a good backup before issuing any terminal commands, but especially the "rm" command.

Users should always have frequent and regular backups of their computer and all external media (including the cloud) which contains important & unique data.

I am being plagued by this mis-feature as well. Having the options "Pause" and "Continue" without "JustStopThis" as an option is a rather profound oversight. I'm migrating to a new Mac from a somewhat slow external drive. It seems that transferring many short files incurs a long "preparing to copy" stage which is not saved between a pause and resume. If anyone knows how to put an end to this madness, please share.

WARNING

>sudo rm -r -f

Just seeing this command makes my hair stand up... I'm not an expert, so maybe someone will correct me, as I'm sure most advanced users know this, but just so everyone else knows, the "sudo rm" is a delete function that has the ability to completely delete ALL your files if you don't specify WHICH folder/file to delete, so use extreme caution. @longlegcraig should probably BOLD the "do not hit enter yet" or better yet put

sudo rm -r -f [dragandropfilepath]

As leaving that blank will delete whatever is inside the folder your terminal cursor is currently on, which by default is your home folder.... Many many stories of people typing in sudo rm -rf* and deleting all their files!

I just stop the copying and delete the partially copied files. Has worked perfectly every time so far.

Just seeing this command makes my hair stand up... I'm not an expert, so maybe someone will correct me, as I'm sure most advanced users know this, but just so everyone else knows, the "sudo rm" is a delete function that has the ability to completely delete ALL your files if you don't specify WHICH folder/file to delete, so use extreme caution. @longlegcraig should probably BOLD the "do not hit enter yet" or better yet put

sudo rm -r -f [dragandropfilepath]

As leaving that blank will delete whatever is inside the folder your terminal cursor is currently on, which by default is your home folder.... Many many stories of people typing in sudo rm -rf* and deleting all their files!

Actually it just won't do anything as no file was specified. It won't delete unless they put a filename or * wildcard

I just tested it and can confirm it did nothing.

Did you ever figure out an answer for this?

Hello, I deleted the files on the drive where I wanted to copy them.

Wow, good to know! Wish I'd known that before I wasted hours and hours! Hope Apple is paying attention...thanks for your help!

Thanks!

Would be nice if Apple could tell us these things from the start and save us hours and hours, right?!?!