Share this post

Link to post

Share on other sites

On a TRIM-enabled SSD there should be little difference between a normal and deep scan, as a deep scan runs a normal scan first, and the deep scan component should find no, or very few, additional files (TRIM causes the deleted pages to be 'emptied' of all data). If a significant difference is found then a wfs could be run, say once a year or so.

The file names you are seeing are in the MFT, which is unaffected by TRIM. Except for small files held entirely within the MFT, the file data has gone. Unfortunately CC does not offer a wipe MFT as a stand-alone feature (I wouldn't expect Recuva to offer it). Some users ger round this by running a wfs from Drive Wiper and then cancelling the job when the wipe MFT has completed, but whether you do this or not is up to you.

Share this post

Link to post

Share on other sites

I think it would still be pretty write intensive, although not as much as a complete wfs (which includes a wipe MFT if run from Drive Wiper).

A wipe MFT creates enough small files to fill all the unused records in the MFT, and then deletes them, leaving only the ZZZ filenames. On a decent sized and well-used device that could mean many tens of thousands of files to be created. Each file creation will mean a write to a new SSD page of:

The MFT record

The MFT bitmap

The root directory

The journal files

Anything else I've not thought of

Some of these operations - adding many thousands of files to the root directory for instance - may require multiple pages to be updated.

And on file deletion there will be - you've guessed it - exactly the same number of writes to delete the files. I don't know whether some of these writes can be amalgamated before actually writing the page, as in the case of the MFT bitmap, but probably not in the more widely distributed MFT records.

So an MFT with say 25,000 spare slots could require as many as 250,000 writes to fresh pages. Probably not a lot in the overall scheme of things, but not something you'd want to inflict on your SSD too often.