Home / Case Studies / Formatted & Logical Faults
Formatted & Logical Faults · case file

I Thought It Would Add, Not Overwrite

His words carry the exact moment of realisation. He tried to use his external drive to reinstall Windows, not realising "all my data all family pictures video and thousands of th music tunes have all been deleted" — the drive "now has the Microsoft 10 data only and all my original data has been overwritten." His honest misunderstanding: "I thought it would add the Microsoft data not overwrite everything." Creating install media overwrites only the front of the drive, not all of it — so despite how final this feels, most of his data very likely survives, provided he has stopped using the drive.

External DriveDeleted / Formatted
// case at a glance
MediaExternal hard drive turned into Windows 10 installation media — family photos, video and a large music collection replaced by the installer at the front of the drive; the original data believed overwritten.
Reported situationDrive used to create Windows install media · original data — photos, video, music — no longer present · drive now showing the Windows installer files · owner's assumption that installer creation adds rather than replaces · recovery sought.
Fault classPartition and filesystem replacement by installer-media creation — the previous structures overwritten at the front of the drive, the bulk of the data area intact behind them, recoverable if the drive has not been written to further.
Equipment usedDrive imaged under a hardware write-blocker before anything, all work off the image · the previous partition and filesystem structures located on the image and compared with their backup copies in R-Studio · original directory tree reconstructed from surviving structures to restore names and folders · signature carving in PhotoRec for photos, video and music where structures did not survive · recovered data validated by rendering and playback.
// the decode

The decode

His misunderstanding is completely reasonable, and the reality is far kinder than it looks. "Add the Microsoft data, not overwrite everything" is what anyone might expect. But creating install media reformats the drive and writes the installer onto it — replacing the drive's structures rather than adding to what was there. That is why his data vanished. The important corollary, though, is that this operation only touches the front of the drive, not the whole surface, so "overwritten" is far less total than the empty drive suggests.

The installer occupies only a few gigabytes at the front, leaving most of the drive untouched. Making a Windows installer writes a new, small partition and a few gigabytes of installation files near the start of the drive. The rest of the drive's capacity — where his photos, video and music lived — is not overwritten by that process. The index that described his files was replaced, so the drive looks empty, but the file data itself remains physically present across the majority of the drive.

Recovery restores the structure, not just scattered files, which matters for a collection this size. Because installer creation only overwrote the front, the previous filesystem's own structures often survive in large part behind the new partition. Reading files through those recovered structures returns them with their original names, dates and folders — so his photos and music come back organised rather than as thousands of anonymous fragments. Where structures did not survive, carving recovers the file data directly by type.

Whether he has stopped using the drive is the decisive factor now. The surviving data stays recoverable only until new writes land on it. If he set the drive aside after realising, the overwritten region is confined to the installer's footprint and the rest is intact. Continuing to use the drive — or booting from it — would erode both the data and the surviving structures. Stopping is the single most important thing, and it should happen immediately.

The honest outcome is strong on the bulk, with the installer's footprint the caveat. The data outside the small region the installer overwrote is recoverable, and where the previous structures survive, it returns organised. The genuine loss is confined to whatever sat exactly where the installer wrote — a small fraction of the drive — reported by what is missing rather than found later. The realistic result is the great majority of his photos, video and music, back with their folders.

// on the bench

On the bench

The drive was imaged under a hardware write-blocker before anything, all work done off the image. The previous partition and filesystem structures were located on the image and compared with their backup copies in R-Studio, and the original directory tree reconstructed to restore names and folders. Signature carving in PhotoRec recovered photos, video and music where structures did not survive, and the recovered data validated by rendering and playback.

// the outcome

The outcome

Drive imaged, the previous structures located and the directory tree rebuilt, and the collection returned organised rather than as fragments. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: making install media replaces the front of the drive rather than adding to it — which is why your data vanished, but also why most of it survived. Rebuilt from the surviving structures, your photos, video and music come back with their folders.

A drive accidentally turned into Windows install media

Stop using the drive immediately and don't boot from it — installer creation only overwrites the front of the drive, so most of your data survives, but every further write erodes it. It replaces rather than adds, which is why your files vanished, but "overwritten" is far less total than the empty drive looks. Don't run consumer tools that write to it. Set the drive aside and have it imaged, and expect your folder structure back rather than a heap of nameless files.

Sending this in from Swansea? Every case opens with the free diagnostic — completed within 2 working days of your media arriving — and one fixed written quote before any work: logical jobs run no fix, no fee; invasive drive-opening work takes 50% of the quote upfront; forensic-classed work is payable upfront in full. If the data is inside a laptop, PC, Mac or server, remove the hard drive or SSD and send us just the drive; we don’t provide an internal drive-removal service, and we don’t recover storage soldered to a motherboard (e.g. Apple Silicon Macs) — only drives that can be removed and sent to us. Post or courier tracked and insured to Bristol Data Recovery, Castlemead, Lower Castle Street, Bristol, BS1 3AG — full sending instructions and the shipping form are here.
Start a free diagnostic

Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.

// related case files

More cases like this one

Browse all case studies →

Got a device with a story like this?

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.