SSD data recovery: an honest assessment

Hard drives leave deleted data physically in place until something overwrites it — that grace period is what all file recovery relies on. SSDs work differently. They cannot overwrite a block directly; it must be erased first. To avoid doing that erase at the moment you are waiting to save something, the operating system sends a TRIM command telling the drive which blocks are no longer in use, and the SSD clears them in the background.

On a modern Windows, macOS or Linux system with TRIM active — which is the default for internal SSDs — deleted data can be physically erased within seconds to minutes. Not marked free. Erased. When that has happened, no software can bring it back, because there is nothing left on the flash to read.

TRIM is not universal, and these cases come up often enough to be worth checking:

• External SSDs over USB. Many USB-to-SATA and USB-to-NVMe bridges do not pass TRIM through. Deleted files on an external SSD frequently survive exactly as they would on a hard drive.
• The file was lost by formatting rather than deleting. A quick format does not necessarily TRIM every block, so a scan is worth running.
• TRIM is disabled — some RAID configurations, older systems and certain enclosures never enable it.
• You are scanning within minutes. TRIM is fast but not instantaneous, and the drive processes the queue in the background. Immediate action occasionally wins.
• The partition was deleted, not the files. The data blocks were never marked unused, so nothing was TRIMmed.

1. Stop using the computer if the loss was on the system drive. Background writes keep the TRIM queue moving.
2. Check the obvious first — Recycle Bin, cloud version history, application autosaves. On an SSD these are more likely to succeed than a scan.
3. If the SSD is external, disconnect it and scan it from another machine.
4. Run a scan and see what is actually there. RecoverHelper's scans are free to run, so you can find out before committing to anything else.

If files appear with intact previews, TRIM had not reached them and recovery will work normally. If the scan finds filenames but every preview is blank or corrupt, that is the signature of TRIMmed blocks — the file table entry survived, the data did not. That result is disappointing but it is real information: it tells you to stop trying to recover and start looking for a backup.

We would rather tell you this plainly than sell you on a scan that cannot succeed. For SSDs, the honest advice is that backups and version history matter far more than recovery software — and that is as true of our software as anyone else's.