Hi everyone,

I have an issue where I am getting the following error when I save out files that have already been copied to a recovery (target) drive.

For some background to this problem, I have copied the data from the customer drive (on SATA2) to a recovery drive (on SATA3), both connected to the PC3K. I then work from copy and save the data to an external hard drive belonging to my customer via USB on my computer. The vast majority of files save without issue. However there are 10's of thousands of files that have this error. I have recently had this issue with one other drive (within the past week). I worked around that issue by saving the files on an internal drive, then manually transferring those to the customers drive. With this case, there are too many to do that. Also, I haven't installed new software or otherwise updated my computer recently.

Does anyone know what might be going on? I have included some additional information about my setup below.

Hardware: PC3K Express
PC3K version: 6.8.12
Data extractor version: 5.11.8
OS: Windows 10 Pro, ver 20H2, build 19042.867
Saving to: External WD HDD
Saving from: Recovery drive
Saving via: Data Extractor, explorer window
Memory: 32GB

Maybe file path name is too long?
Rename the external drive to just 1 character and see if that reduces the amount of files complaining.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Just a wild guess but might it be those files are cloud based?
I have had a similar problem with files in the One Drive folder. The files weren't on the drive but were only stored in the cloud.

Thanks for the replies labtech and dick, but it doesn't seem the path length is the issue. The files aren't cloud based or symlinks either.

Unsupported characters in the path or file names for the FS of the destination?

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

I have finished this drive and I wanted to follow up with the results. It looks like I was wrong and labtech was correct. The pathname length was the issue. To save the data, I made a separate top level folder for affected folders/files and saved the affected child folders to that top level folder. So with a patient path like I would be able to get to x, but not y and z. So I would save folder y to the top level output folder on the customer's recovery drive.

Prior to saving out the subfolders, I tried enabling long path names in windows by modifying the registry. This had no effect.

Hopefully, this will help someone out in the future!

Glad it came to a resolution. Long path file name problems are very annoying.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

LongPathTool handles problems when copying files with long paths.