Data Recovery Case File · Formatted & Logical Faults · A Fresh Install Writes Less Than You Think
The Destination Was Never Verified and the Source Is Now the System Drive
His enquiry describes a migration undertaken carefully and completed in the wrong order. "I recently formatted my computer, placing important files onto an external drive to transfer onto my fresh installation. I made a horrible oversight." The oversight is almost always the same one — the destination was trusted rather than checked — and the recoverable news is that a fresh installation writes far less than people assume.
| Media | Internal system drive formatted and reinstalled — files believed transferred to external media prior to the wipe; transfer not verified |
| Reported situation | Machine formatted deliberately for a fresh installation · files intended to have been copied to an external drive beforehand · transfer not confirmed prior to the format · files subsequently found absent · fresh installation completed · original content required |
| Fault class | Deliberate format followed by bounded system write — prior content substantially unoverwritten; continued use the principal ongoing risk |
| Equipment used | External destination examined before any work on the source · installation write extent measured against capacity · machine taken out of service immediately · imaged write-blocked before any carving · previous filesystem structures located from surviving copies |
The decode: check the destination, then stop using the machine
The first thing to establish, and it costs nothing: what is actually on the external drive. The commonest version of this is that the copy partly succeeded — one folder transferred and another did not, or a transfer reported completion while some files failed silently. It is worth examining properly before assuming nothing arrived.
Why the order was the mistake rather than the format: formatting a machine you are replacing is entirely normal and correct. What makes it safe is verifying the copy first — opening files at the destination, not watching a progress bar reach the end. A transfer that reports success and produces unopenable output is a failure mode this archive meets constantly.
Now the encouraging arithmetic. A fresh operating system installation writes a bounded quantity — the system itself and its supporting files. On a drive of any modern capacity that is a fraction of the total, and it is written from the beginning of the free space rather than spread across the whole surface.
What follows: the great majority of what was there before is still physically present. A format writes an index and marks space available; the installation then occupied part of that space and left the rest untouched. The previous filesystem structures frequently survive in their backup locations too, which is what makes a structured reconstruction possible rather than only carving.
What is genuinely urgent, and it is not the recovery: the machine must come out of service. A freshly installed system writes continuously — updates, indexing, temporary files, application installs, browser caches — and every one of those lands in the space holding the previous contents. Each day of ordinary use costs more than the format did.
Why that is worth stating so plainly: people who have just set up a machine want to use it, and the instinct after discovering a loss is to keep working while deciding what to do. That is the single most expensive thing available.
What to do if the machine is needed: use a different one, or start it from external media rather than from the drive being recovered.
The habit that prevents it entirely: copy, verify by opening, and only then wipe. Three steps in that order and none of them optional.
On the bench
The external destination was examined before any work on the source, partial transfer success being the commonest form of this situation. Installation write extent was measured against capacity — a fresh operating system writing a bounded quantity from the start of free space, leaving the majority of the surface untouched. The machine was taken out of service immediately, a newly installed system writing continuously through updates, indexing and caching. Previous filesystem structures were located from surviving copies.
The outcome
The destination examined first, the installation's write extent measured, and the machine removed from service before any recovery. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: check what actually reached the external drive, because partial success is the commonest version of this. Then stop using the machine — a fresh install writes a bounded amount, but continued use writes continuously into exactly the space you need.
Wiped a machine before checking the copy
Stop using the computer today — that matters more than anything else you do. A fresh installation writes a bounded quantity, the system and its supporting files, which on any modern drive is a fraction of the capacity, so most of what was there before is still physically present. What removes it is continued use: updates, indexing, temporary files, application installs and caches all write into exactly that space, so every day of ordinary work costs more than the format did. Check the external drive properly first, since partial transfer success is the commonest version of this. And in future: copy, verify by opening files, then wipe.
Stop using it now — call Oxford Data Recovery on 01865 593000; destination examined first, installation write extent measured against capacity, previous structures recovered from their surviving copies.
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.