Copy Files Often Receive error code -50

There wasn't a parameter being used. It was simply drag and drop with the finder UI.

This is further evidenced to be a bug because I can use the terminal EVERY TIME without this matter

The error regarding a parameter would be a software bug in Apples side because they are creating parameters not me. Every thing I am doing is a drag and drop.

This is incredibly time consuming for people especially if they rely on the Finder UI because they have to then go in an undo the resumable copy settings after all the problems. I would guess that about 50 percent of the time I can reproduce this issue.

BUG

In fact windows & linux have been most reliable with copying using the UI and macbook is about as useless as wings on a donkey

If a third party add on is the culprit, remember I was using apple software. Also remember that cp commands works flawlessly. This is not a memory issue, not an ntfs drive matter, not a third party add on issue, it's a bug somewhere under the hood of finder. I wouldn't even be convinced it was a driver issue given the solid workaround.

I spent more than 2 decades working as a tester and developer. My hunch is usually correct with this much evidence.

It's obviously a bug with underlying use of Finder not the drive configuration since I can reliably use terminal to copy. Therefore all that advice about troubleshooting drives and posting their configuration is a waste of time and energy

I didn't start using software and operating systems last week and if I was to go to that length in order to provide useless information I should get paid. Someone should test the software thoroughly before it goes public

Video of experience and some details of system and overview of drives as well as source and destination file systems

https://youtu.be/805XaqjQSQo

Additional Txt has diagnostics log

I have already discovered that useless information online.

There were no user parameters as I just used the graphical user interface which came with the operating system. It's called Finder

Anyway, all of the usual troubleshooting steps are not solving this. And since we have an error that doesn't match up with anything that I am doing that error is pointless and useless.

What's more, is that this experience leaves the file system in a state where the user cannot use some of the files that have landed in the destination during the copy. You essentially end up in a resumable copy state. That's fancy but it gets worse from here. At this point you would think a simple resume would make some incremental progress. However it immediately has an other error of the same type. Meanwhile I can continue copying other files without error.

Once I clear the resumable copy flags I can continue copying but if you have a significant number of directories to copy this can be a huge effort to overcome. It's obvious that the copy on the operating system has some holes in it's robustness. Instead of resuming an entire operation it should be easier to incrementally achieve this without having to copy and paste all kinds of directory structures into a termal window after setting flags on folders.

I don't know who came up with this experience but it's about the worst you can ask for.

I am going to provide some video next. If someone works for Apple and wants to tell me how we can get them some verbose logging or other sort of information on the system related to my software that is fine.

But since the hard drives work on every other system I previously mentioned and now mentioning also my phone, a third operating system named Android, it is obviously an Apple matter.

Since I just captured footage of this problem a couple of times in short order it will give insight to how bad this experience is , to some degree, as well as how easy it is to reproduce. I am not going to display how I overcome the directory or folder being in a peristent state of "resumable copy" because that is clearly documented elsewhere.

I should be able to make a video and post it on Youtube within an hour or two.

Wrong - Either MacOs Supports it or it doesnt' And it is a read operation on NTFS to a write on ExFat.

This isn't a test. This is a real live issue. I am not going to format and lose 3tb of data. Is that a joke?

Copying less than 15gb of data is going to put it tight on memory? Is this another joke? I have had it repro copying less than 1gb of data

This is all speculative and worth ignoring. Just like most of the previous comments. Especially since the error doesn't indicate any of your speculation as a root cause.

It is an error on parameters. Which is a bug in something.

I managed to get everything off the disk by now. But it looks like during the saga my operating system crashed.

Apple should really get to work on fixing the experience in several ways

1. Resumable copy if it isn't achievable then disable it on a disk or disks and present some documentation for other options and troubleshooting.

2. The actual underlying reason for that error should be presented. If Apple creates a parameter internally that is implicit it could present more information about the bad parameters in case the user can help themselves if possible. If for example it can't read something on source just say that. It it has a permission issue say that. If it has a driver issue present that.

3. Assuming my unexpected system restart was an os crash I should be presented with an Option to send info to Apple anonymously. Again not certain that was why system restarted but it did so without user input or acknowledgement.

Super bad experience I have read others report symptoms. Most likely they get frustrated and work around and never fully report.