I just noticed that your copy logs show that F is quite limited on free space (in the first log, only about 1GB free). And as stated, SafeCopy will temporarily require space for two copies of the file being copied right then. For large files, this may mean Windows has to search the Destination for every nook & cranny of free space to fit the temp file in, then patiently rename every fragment of it to the real target file name afterwards once the temp-file copy completes/succeeds. Of course, the free space afterwards goes back up, but it may be getting very limited during the actual copying.
Try turning off SafeCopy, or freeing up space on F, or getting a bigger F...
Otherwise, I don't think we can help you. If there are no errors, all we can say is 'yes that is slow: I wonder why?'. It's either something to do with those files specifically, or something about them that doesn't mesh nicely with your system. My guess is it's related to the high(er) size-per-file versus the free space (plus, the SafeCopy temp double-space requirement)
Try turning off SafeCopy, or freeing up space on F, or getting a bigger F...
Otherwise, I don't think we can help you. If there are no errors, all we can say is 'yes that is slow: I wonder why?'. It's either something to do with those files specifically, or something about them that doesn't mesh nicely with your system. My guess is it's related to the high(er) size-per-file versus the free space (plus, the SafeCopy temp double-space requirement)