Data Recovery Case File · Mac & Apple Ecosystem · Guided and Destructive
Setting the Machine Up Again Is Not the Same as Getting It Working Again
Her enquiry describes a support call that succeeded at what it set out to do. A machine that crashed and would not get past sign-in, so she called the manufacturer: "with support we got my machine up and running through recovery mode using an external hard drive. Once I had set up my machine again, support took me" through the rest. The machine works. The phrase in the middle is the one to look at, because setting up again is what you do to a device with nothing on it.
| Media | Internal drive from a desktop machine — guided recovery-mode reinstallation performed with manufacturer support; volume reinitialised as part of the process |
| Reported situation | Machine crashing and not progressing past sign-in · manufacturer support contacted · guided recovery performed via recovery mode using external media · machine restored to working order · machine subsequently set up as new · previous content required |
| Fault class | Volume replacement during guided reinstallation — previous content present beneath a fresh installation pending overwrite; continued use the principal ongoing risk |
| Equipment used | Machine taken out of service immediately · installation write extent measured against capacity · imaged write-blocked before any reconstruction · previous volume structures located from surviving copies · files validated by opening |
The decode: what the guided process was solving, and what it was not
What support was asked to do: make the machine work. That is the whole scope of the call, it is what the process is designed for, and by that measure it succeeded — she has a functioning computer.
Why the fastest route to that is reinstallation: a machine that will not start has a system problem, and replacing the system resolves it reliably without needing to know what was wrong. Guided recovery procedures reach for it early because it works, and because diagnosing the actual fault over a telephone is not practical.
What the phrase reveals: setting up a machine again means creating an account, choosing settings, and starting fresh. That is what a device does when its volume has been erased — a machine whose files survived would have come back to her own desktop with everything where she left it.
Why nobody stopped to say so: the process does say so, usually, in a confirmation nobody registers during a long troubleshooting call. By that point the objective has become getting the machine to start, and consenting to whatever achieves that feels like progress rather than a decision.
Why this is not a criticism of support: they were asked for a working machine and they produced one, quickly, at no cost. The gap is that nobody's job during that call was to ask what would be lost — and the person who could have asked was in the middle of the problem.
Now the position, which is better than it sounds: erasing a volume writes new structures and marks space available. It does not visit the files, and a fresh installation occupies a bounded fraction of a modern drive. Most of what was there is still physically present.
Why it is urgent anyway: she has a newly set-up machine that she is presumably using. A new installation writes continuously — updates, indexing, caches, applications — and all of it lands in the space holding her previous content. Each day of use costs more than the reinstall did.
What must happen now: stop using the machine. Not after finishing something — a system volume is written to by the act of being switched on, and unlike an external drive it cannot be unplugged.
On the bench
The machine was taken out of service immediately — a newly installed system writing continuously through updates, indexing and caching into the space holding previous content. Installation write extent was measured against capacity, volume erasure replacing structures and marking space available without visiting files, and a fresh installation occupying a bounded fraction of the medium. Imaging ran write-blocked with previous volume structures located from surviving copies.
The outcome
The machine removed from service, the installation extent measured, and previous structures recovered from their surviving copies. 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: support was asked for a working machine and produced one, which is what they are there for. Setting up again is what a device does with an empty volume — but erasing writes structures rather than files, so most of your content is still there.
After a guided recovery that set your machine up as new
Stop using it today — that matters more than anything else, because a newly installed system writes continuously through updates, indexing, caches and applications, and all of it lands in the space holding your previous files. You can't simply unplug a system volume. The position is better than it feels: erasing a volume writes fresh structures and marks space available without visiting the files themselves, and a new installation occupies a bounded fraction of a modern drive. If you're ever on a support call about a machine that won't start, ask one question before agreeing to anything: will this keep what's on it?
Stop using it — call Oxford Data Recovery on 01865 593000; write extent measured against capacity, imaged before any reconstruction, previous volume 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.