Duplicate Finder - why

a little history....

a friend of mine had a hard drive what was windows 7. it started a windows 10 upgrade and she turned it off in mid stream. she then turned the system back on and it started installing XP. that is when i was called to rescue her files and family photos

i moved her HD to my main system along with a 2TB empty HD. I used Recuva and minitool revovery to recover any and all files i could. as i recall there were over 2 million recovered files and 350 GB of data.

now for the problem.

i am using CCleaner to find the Duplicate files with the SIZE and CONTENT flags checked. i let it run and select the DELETE - this has left the last file in each of the groupings. so far so good.

the problem is i have done this over 20 times. it completes Finding Dupes so I rerun it. it finds more... never are they the same files?? why did it not find them the first 19 times i did this?

is there a limit to the number of compares it can store? my system has 32G ram.

UPDATE - in making the screen shots (attached) you will note there are lots of 0.81KB and 18.1KB files, among others. these are the ones i am questioning. i guess maybe the program can only handle one file of a size and it compares against that one?

thoughts? i still have 220 GB of data and 669,321 files, 31,086 folders - fun fun - right??

thanks

george

post-79406-0-21076200-1499230886_thumb.jpg

post-79406-0-88158200-1499230886_thumb.jpg

post-79406-0-48878700-1499230887_thumb.jpg

post-79406-0-08600800-1499230888_thumb.jpg

George,

I deleted the double post of this topic you posted again today.

feel free to add things to this thread but please don't double post. :)

if someone knows the answer and wants to share, they will.

after re-reading my message/ question - i felt it was not a 'bug report' and did not find a way to delete it fron this area.

that is why i re-posted it under the general CCleaner area. i also thought it would get more response.

what is your thought - here or there?

george

can't rule out the possibility of it being a bug, so I'm happy to leave it here.

regardless, it'll still be seen by all, especially the Dev/Admin Team.