Deleted Years of PC Photos Across an SSD and HDD: What Is Still Recoverable?
TL;DR:
If recovered JPG files show intact names but fail to open in viewers like Windows Photos or Photoshop, the underlying image data has likely been overwritten or permanently wiped by Windows TRIM, meaning you must immediately stop writing to the drives and identify whether the original files resided on the NVMe SSD or the HDD to prioritize remaining recovery options.
● On an NTFS NVMe SSD, Windows TRIM is enabled by default and permanently frees deleted storage clusters, meaning recovery software cannot restore usable image data if the PC has been actively running for weeks.
● If the missing photos were stored on the mechanical HDD and it has not experienced heavy new writes, immediately image the drive and run a controlled recovery to a separate physical destination.
● Stop cycling through additional recovery apps like DMDE or Recoverit Data Recovery if initial scans yield unopenable files, because surviving directory metadata cannot reconstruct overwritten image bytes.
Ask AI for a summary
ChatGPT
Perplexity
Gemini
Claude
Grok
If a recovery scan shows old folder names and JPG files but the pictures will not open, do not count those files as recovered yet. First identify which physical drive originally held the missing photos. An NVMe SSD and a mechanical HDD have different deletion behavior, and a month of normal computer use can change what remains recoverable. Minimize new writes to any drive that may still contain the originals and save every usable recovery to separate storage.
That is the real blocker in this Windows photo-recovery case on Reddit. About 15 years of photos disappeared while the user was reorganizing drives during a Windows boot change. The user was no longer sure whether the originals had mainly been on the NVMe SSD or the HDD. DMDE could see photo folders and recover JPG files, but the recovered files failed in Windows Photos, IrfanView, Paint, and Photoshop. Recoverit Data Recovery for Windows found only some usable photos, Recycle Bin recovery restored a few others, and the user later said an external backup drive had also been overwritten.
Identify the Original Source Before Running More Scans
Do not keep scanning every drive as if they have the same recovery chance. Use the surviving folder paths, old library locations, Recycle Bin entries, cloud history, application settings, and any recognizable DMDE directory records to work out where each photo set originally lived. A folder name found in a scan proves that some metadata was found on that drive; it does not prove that the full photo payload is still intact.
Do Not Save Recovery Results Back to a Possible Source
Microsoft's Windows File Recovery guidance says to minimize computer use after deletion because new writes can overwrite space that held deleted files. It also requires recovery to a different destination drive.
Treat the NVMe SSD and HDD as Different Recovery Branches
Which Source Held the Photos?
- NVMe SSD: Windows documents delete notifications, also called TRIM or UNMAP, as notifications that storage clusters have been freed after deletion. For NTFS, Microsoft says TRIM notifications are enabled by default unless an administrator disables them. If the deleted photos were on the NVMe system SSD and the PC has continued to run for weeks, software recovery may return file records without usable image data. No recovery program can reverse SSD blocks that are no longer returning the original content.
- Healthy HDD: If the photos were on the HDD and it has not been heavily written since deletion, a controlled recovery attempt is still more reasonable. Stop writing to that HDD, image it first when practical, and recover to another physical drive.
- External drive already overwritten: Treat that copy as a lower-priority source. Overwritten image bytes cannot be reconstructed just because an old filename or folder entry remains.
For the SSD branch, Microsoft's TRIM documentation explains the delete-notification behavior. Recoverit's broader SSD deleted-file recovery guide also separates readable logical-loss cases from data that has already been trimmed or overwritten.
Why DMDE Can Show JPG Names That Still Will Not Open
A filename, folder path, or file extension can survive even when the sectors or SSD blocks containing the actual JPEG body do not. That is why a recovery tool can list .jpg files that fail in several independent image viewers. The useful test is the recovered file itself: confirm that it has a plausible nonzero size, try a preview, and open it outside the recovery program. If several viewers reject the same result, do not assume that photo-repair software can recreate missing image bytes.
If the files came from a stable HDD, one additional recovery from a disk image using a different recovery method can be justified. If multiple competent scans produce the same invalid files, stop cycling through general recovery apps. Repeated scans do not restore data that has been overwritten or discarded.
Choose the Next Step by the Best Remaining Source
- Step 1
Preserve every intact copy first: Recycle Bin results, cloud copies, old exports, messages, external backups, and any photos that already open normally.
- Step 2
Map the missing folders to the NVMe SSD, HDD, or external drive as accurately as possible. Do not spend the same recovery effort on a heavily used system SSD and a relatively untouched HDD.
- Step 3
If the HDD is the best remaining source and stays stable, image or scan it and save results elsewhere. If the only remaining source is the actively used NVMe SSD and scans already return invalid files, set expectations around surviving backups and usable copies rather than buying more software on the assumption that another scan can reverse TRIM or overwrite.