Data Recovery Case File · Deletion & Formatting · The Wrong Target
A new operating system where seven years used to be: the installer's footprint measured, and the archive carved back from around it
The accident in this enquiry is one of computing's classic wrong-turns, told with disarming candour. Setting up a new PC — and preferring an older Windows to the one it shipped with — he reached the installer's disk-selection screen and pointed it at his 8TB external: the "big boy hard drive," as he put it, where the system could live "forever." The installer obliged. What it replaced was seven years of photos, videos and creative work — including, the part his enquiry singled out, his game-development projects, the ones he most wanted back; the 3D-modelling assets he could live without. He was shopping around, he said, to learn "what if and what can be recovered." A precise answer requires measuring exactly what a Windows installation writes — because it's far less than seven years' worth.
| Device | 8TB external hard drive — long-term archive: ~7 years of photos, videos and game-development projects |
| Reported events | Windows installer directed at the archive drive during a new-PC setup → drive repartitioned and a fresh operating system installed → prior contents no longer listed; owner's priority stated: the game projects above all |
| Fault class | Installer-driven repartition and OS install — a bounded overwrite footprint on a vast, otherwise-untouched estate |
| Equipment used | Write-blocked imaging · ACE Lab Data Extractor (prior-filesystem reconstruction; signature carving; project-structure reassembly) |
What the installer actually did to eight terabytes
The screen makes it look total — drive selected, partitions deleted, new system installed, old contents gone — but the arithmetic is the case's whole hope. A Windows installation writes its partition scheme at the drive's opening territory and then lays down some tens of gigabytes of operating system: on an 8TB drive, a footprint in the low single digits of one per cent. The "deletion" of the old partitions was the familiar front-page swap this archive documents from every angle — the prior filesystem's paperwork replaced, its data left lying — and the install itself then genuinely overwrote only where it landed: the beginning of the drive, plus scattered system files. Seven years of archive doesn't live in the first forty gigabytes of eight thousand; the overwhelming bulk of his photos, videos and projects sat exactly where they'd always been, unlisted but untouched, in the vast territory the new operating system had claimed on paper and never visited. The recovery question was therefore never whether — it was how much of the old structure survived beyond the installer's stamp, and what the footprint had happened to land on.
The recovery — priorities honoured
The drive was imaged once, write-blocked — the new Windows never booted again — and the archaeology ran on the copy. Beyond the installer's opening footprint, substantial remnants of the prior filesystem survived and were reconstructed first, restoring folder trees, names and dates for the majority of the estate; where the new partition scheme's writes had cost the old paperwork, the contents were carved whole from the untouched territory and re-filed by type and date. His stated priority ran the queue: the game projects were located, reassembled as projects — source, assets and folder structures validated together, since a game that opens in its tools is the deliverable, not a soup of loose files — and verified before anything else was finalised. The wider archive followed: photos and videos across the seven years, recovered in bulk; the honest ledger confined the losses to what lay directly beneath the installation's actual footprint — a bounded, itemised population, weighted (by the luck of geography) away from the folders he cared most about. Delivered on new storage, projects front and centre.
Outcome
The seven years substantially home, the game projects — the ask behind the ask — recovered and opening, and one of computing's classic accidents measured honestly for the next person mid-panic: an operating system installed on the wrong drive is a bounded wound on a big disk, not an erasure. The response that keeps it bounded: power down the moment the mistake registers — every boot of the new system writes more (updates, caches, page files, all landing on the old estate) — and let nothing "set up" further. And at the disk-selection screen, where this page was really written: unplug every drive except the target before installing. The installer lists disks by size and number, not by sentiment; the big drive that looks like the obvious home for "forever" is usually the one already holding it.
Installed the OS onto the wrong drive?
Shut the machine down now — the install's footprint is bounded, but every boot of the new system grows it with updates and caches. Don't start "moving what's left," don't let Windows finish setting up, and don't reinstall again elsewhere with the archive drive still connected. Note roughly what lived where, and which folders matter most — priority carving is real, as this case's game projects prove. And before any future install: one cable's worth of prevention — unplug everything but the target.
Most of it's still under there — call Bristol Data Recovery on 0117 332 1137 before the new system boots again.
Request a quote online →
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.