So I have Windows 8. I SHIFT+ENTER accidentally deleted all pictures instead of half. I used global purpose "File Scavenger 3.2" program, which was always working perfect for last 5 years to restore files & images on HDD drives (I never done this on SSD, through). So I used it this time as well, it quickly found all deleted files, all they were in "good" condition, and immediately restored them. The file sizes looked ok, but only 15 of 200 had thumbnails in Windows Explorer. I use "Irfan View" to view images, and only those 15 I was able to open, for all others, when I tried to open it said "unknown file format, file empty or not found". It is the same with Windows Image Viewer. I tried to used "Stellar Phoenix JPEG Repair" and "JPEG Repair 2". None of them repaired anything. Just showed "invalid". I did checked other threads related to this topic, but I did not found any answers I needed. So maybe someone had similar situation and can recommend exact software, which worked for you to get images back.
An important detail that hasn't been mentioned thus far is how file deletion is (usually) done on SSDs. It is different than the traditional, spinning-disk, hard disk drives (HDDs).
As mentioned in AJ's answer, traditionally when you "delete" a file the operating system (Windows 8 in this case) simply tells the hard drive that the file is no longer needed and the hard drive marks that file as unneeded but doesn't actually remove the data. This is a "logical delete." Actually removing the data is a "physical delete." With file-recovery software you can recover a "logically deleted" file because the data may not be gone yet.
However, SSDs have a featured called TRIM which immediately follows a logical delete with a physical delete. This improves the performance of the SSD, but comes with the cost of making file recovery impossible. I don't use Windows much, but from what I can tell this feature is enabled by default.
Because of this the "files" that were recovered are almost assuredly just filled with junk and there's no remnant of the original data left.
You can check if this feature is currently enabled on Windows 8 by opening a command line and entering the following:
fsutil behavior query disabledeletenotify which will tell you the value is either
0 means TRIM is enabled (the variable name is "disabled", so 0 is NOT disabled).
I've made this mistake too. It's a harsh lesson about the importance of proper backups.
For what you are saying it looks as if the recovery software didn't do his job properly and just recovered wrong sectors or data.
If I were you I would try a more professional recovery software. I been using "ontrack recovery professional" and it has done a perfect job for plenty of memory cards and hard disks ( ssd and sata ) and it has a trial version to test it. I really hope you can recover you data.
If you recovered to the same drive that you originally deleted them on, you probably corrupted them yourself. The reason you can undelete a file is that the drive is simply marked as the space being available, no other data is actually changed. Thus, if you read where the file had been, the data is still there.
The problem with recovery is that when you recover a file, it has to write it somewhere in a new file. If this new file happens to make use of the space marked as available from one of the other files that you were recovering, that other file will be corrupted.
On a normal HDD the risk isn't that high if you have lots of free space because HDDs try to group files in to contiguous blocks to reduce file seeks, and thus will generally try to avoid the holes left by recently deleted files.
On SSDs however, that is turned on its head. For SSDs, the primary concern is not contiguous blocks (there is no seek time for solid state drives) but rather how many times the value has been changed on a particular area of the drive (because SSDs have a limited number of writes on each bit). If the files had been around for a while and had kept that part of the drive from being changed, it likely is now seen as the most ideal spot to write new data, thus making it highly likely that any restoration operation will result in corruption to other files being restored.
Unfortunately, after the data is actually overwritten, there is no practical way to recover it and you are up a creek with no paddle. The data is gone. (There may possibly be some special forensic ways to do it by taking the drive apart, but that would require specialized equipment and would cost thousands of dollars+ if it is even possible on SSDs.)