Data Recovery Case File · Formatted Drives · The Installer's Target

"I did not know the process would format my drive": the media-creation trap decoded, the bounded footprint mapped — and ten years of images recovered, RAW and PSD first

His accident is one of the most quietly common in this archive's formatted-drive genre, because the tool that causes it is official, helpful, and clear only in its small print. "I was making installation media for Windows 10 by using the space on my drive. I did not know that the process would format my drive." The drive: a 3TB Buffalo external. The cost: "more than 10 years of photos, uni work and videos." His attempts since: paid recovery software, "to no avail." And his priorities, stated with a photographer's precision: the .PSD files and camera RAW images are the bulk of the drive and the point of the recovery. All of it addressed below — including why his paid software failed where the format itself hadn't actually destroyed much at all.

The decode: what the media tool did, what it spared — and why his formats were the friendly kind

The trap, named: media-creation utilities need a drive to turn into an installer, and they take the job seriously — the selected target is formatted as step one, its old contents' index swept aside for the new bootable structure. The interface asks which drive; it does not linger on what "which drive" costs, and a 3TB archive offered as scratch space is exactly how a decade disappears into a tool doing precisely what it said, quietly. The honest map of the damage, though, is far kinder than the loss felt: the format erased the index, and the installer then wrote its actual payload — a few gigabytes — at the drive's start. Everything beyond that bounded footprint, across nearly three terabytes, remained physically present; months on the shelf since cost nothing further. Why his paid software still failed: post-format recovery lives or dies on reconstruction depth — and a big, old, well-filled archive defeats shallow tools two ways: the swept index leaves them guessing, and large files stored across years of allocation need either filesystem-trace mapping or genuinely format-aware carving. Which is where his own priority list becomes the case's good news: camera RAW files and PSDs are among the friendliest cargo in the formatted genre — big, strongly structured, internally signposted formats whose headers, layer tables and embedded metadata make them carve and verify beautifully, and whose typically contiguous storage (written once, archived, never churned) keeps fragmentation low. His tools weren't wrong that the job was hard; they were just standing at the shallow end of a deep, and unusually well-organised, pool.

The recovery — mapped, carved, verified as images

The drive was imaged once, write-blocked, and the reconstruction ran both roads on the copy: the original filesystem's surviving traces mapped first — recovering the archive's real names, folders and dates wherever the format's sweep had left them legible — with format-aware carving filling the gaps for the RAW and PSD populations his enquiry had headlined. The bounded losses fell exactly where the installer had signed: the few gigabytes at the drive's start, itemised, with a decade of everything else rising around them. Verification ran a photographer's standard: RAW files opened and rendering, PSDs opening with layers intact, the university work and video sampled and confirmed across the years — and delivery went out organised by the recovered structure on new media in duplicate, with the report's closing doctrine earned twice over by his months of waiting and his tools' failure: the format took the map, the installer took a corner, and the archive itself was never more than one properly-deep read away.

Outcome

The decade home — RAW rendering, PSDs layered, the installer's corner honestly itemised — and the filings his common accident deserves. Know the media-creation trap: installer tools format their target as step one — give them an empty stick bought for the purpose, never "spare space" on a drive that holds anything, and read the drive-selection screen as the destructive commitment it is. Read "months ago" and "software failed" correctly: neither hurts a formatted drive that's sat unused — shelf time is free and shallow tools' failure is a depth report, not a verdict. And let his priority-stating be the template: naming the formats that matter (.PSD, RAW) let the recovery aim its depth and its verification exactly where the decade lived. The process did what processes do. The archive did what archives on unused platters always do: waited, complete, for someone to ask properly.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.