This specific drive held my family pictures from about a decade ago. So when I got the “You need to format the disk before you use it” message, I started panicking. But with one free tool and about 90 minutes spent in uncertainty, I recovered 104,754 files. I realized the drive wasn’t empty just because Windows says it is.

The first photo gave me hope

Windows showed nothing while PhotoRec’s folder kept filling

The tool I fell back to was PhotoRec. I ran this scan for about ninety minutes on my drive (PhysicalDrive0 – 512 GB / 476 GiB (RO) – SanDisk SD8TN8U512G1001). I focused more on the recovery count than the progress percentage.

Before I started this process, Windows could not read the filesystem as a normal NTFS volume. When I looked at it in Disk Management, it showed up as RAW instead of a normal NTFS volume with my folders. This just felt empty even though I hadn’t deleted the files myself. Windows was seeing the drive without being able to tell me what was on it.

It was a specific family photo that convinced me this process would actually work. This JPEG didn’t have a recognizable file name because PhotoRec renames recovered files, but I recognized the face and background on sight. Once I opened it, the camera metadata was also instantly familiar.

While setting up the process, I configured PhotoRec to save the recovered files to a different drive, so I wasn’t writing anything back to the damaged filesystem. I also made sure the list of file formats to recover included just image formats. My greatest surprise was how quickly the folder started filling up with pictures, including several I had long forgotten.

Why PhotoRec worked when Windows couldn’t

PhotoRec wasn’t looking for my folders

The filesystem on Windows is essential in recognizing what files exist and where. If that is unreadable, a file that still has data can also seem unreadable.

PhotoRec works because it doesn’t depend on the filesystem’s directory structure. Instead, it scans the underlying storage for known file signatures, such as the markers that identify JPEG data, and uses the file format to determine what it can recover. This is known as file carving. That’s why it doesn’t need to know that a JPEG once lived in Pictures2023Christmas.

However, file carving also means you don’t get a folder structure or the original filenames. The results I got were named/formatted similarly to f123456789.jpg. I also experienced some fragmentation, with certain file fragments being incomplete. This happens when all pieces of the file aren’t exactly where PhotoRec expects them.

Also, because I was recovering from an SSD, I knew TRIM could make deleted or discarded data much harder or impossible to recover. I wasn’t expecting every photo to survive. In my case, the volume had gone RAW. I stopped writing to it immediately, and PhotoRec could still read real photo data from the drive. Recovery tools generally have a similar ceiling: once the underlying data has been overwritten or is no longer readable from the storage, software can’t recreate the original file.

The recovered folder

Generic names, no structure, and a lot of clutter

The recovery output filled up folders named recup_dir.1, recup_dir.2, up to recup_dir.210. Certain files started with “t”, which is PhotoRec’s prefix for JPEG thumbnails embedded inside other photos.

In total, I got back 104,754 files. But several of these included full-size photos, embedded thumbnails, fragments, and files I couldn’t use.

Amongst the clutter, I had duplicates, thumbnails, and just older images I didn’t care about. A bunch belonged to an earlier time in the drive’s life that I didn’t care about, and that’s what made this even more interesting, because according to Windows, this was an empty drive.

With the number of files it recovered, the only logical way I could make sense of it was to sort by file size. This gave a clean separation of tiny JPEGs from real camera originals. Sorting by date also helped because PhotoRec can extract timestamps or other metadata from some recovered files. These aren’t guaranteed to be accurate, but they were good enough to be treated as a clue.

The recovery may have taken under two hours, but making sense of it took far longer. I had to go through previews after sorting because the filenames offered no clues. It felt discouraging when I stumbled upon certain important photos that only opened as thumbnails, but there were enough perfect recoveries in the mix to make it worth my time.

The limits, and what “empty” really means

When I started this process, I was hoping for an outcome that would restore my collection. Several of the recovered files opened as proper full-size photos. The rest were thumbnails or incomplete data that couldn’t simply be rebuilt.

Fragmentation is the explanation for most of what I didn’t get back. Recoverable-looking data doesn’t always make the cut because PhotoRec checks recovered files for consistency when possible and can discard files that fail those checks.

I used QPhotoRec’s graphical interface for this recovery, but the same download also includes PhotoRec’s command-line interface. There may have been more options I could have tested there, but I didn’t, so I can’t say whether a different configuration would have produced better results. But what mattered most was that I got files from a drive that Windows saw as empty.

OS

Windows, Linux, macOS

Developer

Christophe Grenier

Price model

Free, Open-source

PhotoRec is a free, open-source data recovery tool that can restore deleted files from hard drives, SSDs, memory cards, and USB drives—even if the file system is damaged.