Data Recovery Case File · Formatted & Logical Faults · Almost All the Way
A Movable Cursor Means Nearly Everything Loaded Before the Desktop Failed to Appear
His enquiry describes a failure precise enough to place almost exactly. A machine of around six years where the system will not start properly and "I only get as far as a blank screen with a mouse cursor that I can move about — no taskbar, icons or wallpaper" — and he asks whether recovering the files is worth the cost. That cursor is doing a great deal of work: it means the drive delivered nearly the entire system before anything went wrong.
| Media | Hard drive from a desktop machine of approximately six years' service — system loading to a responsive but empty desktop; no interface elements presenting |
| Reported situation | Desktop machine of approximately six years in service · system not starting fully · display reaching a blank screen · mouse cursor present and responsive to movement · no taskbar, icons or background presenting · transfer of all files to a replacement machine sought · cost proportionality queried |
| Fault class | Desktop shell failing after successful system load — drive delivering the great majority of the system before failure; user regions likely readable |
| Equipment used | Responsive cursor treated as evidence of near-complete system load · drive removed and read independently of the machine · imaged write-blocked at the block level under capped timeouts · user profile regions extracted from the image with system files excluded · content delivered ready for transfer to a replacement machine |
The decode: how far it got, and why that predicts an easy recovery
What has to happen before a cursor appears: almost everything. The drive is read, the system loaded, drivers initialised, the display configured and the input system started — a long sequence with a great many reads along the way.
Why a cursor that moves is the strongest signal in his account: it proves the input path is live. Movement means the system is running, processing events and updating the display — not frozen, not stalled, but working.
What that eliminates: the entire hardware chain and most of the software one. A drive that delivered the operating system is a drive that reads, and a machine that reached this point has functioning memory, processor, display and input.
What is therefore failing: the desktop shell. The program responsible for drawing the taskbar, icons and background is a single component loaded near the very end, and its absence produces precisely the empty screen he describes.
Why that component fails on its own: it depends on the user profile, and profiles are where damage tends to accumulate. A corrupted profile or a damaged shell registration stops the desktop while leaving the system beneath it working.
Why that is excellent news for his objective: he does not want the machine, he wants the files. A drive that loaded an operating system will image without difficulty, and his content sits in regions the system never needed to touch.
Why the answer to his cost question is favourable: this is at the straightforward end. No mechanical work, no board work, no reconstruction of damaged structures — a drive read on ordinary equipment and content extracted.
Why he should nonetheless not keep trying to start it: a machine repeatedly failing to start writes each time. Logs, temporary files and repair attempts all allocate space, and on a six-year-old drive that is unnecessary wear.
What he could try himself, and it is genuinely worth mentioning: the drive can be connected to another machine as a second drive. Content from a system that loaded is usually readable by simply plugging it in, at the cost of an adapter.
Why saying that is the right thing to do: he asked whether the cost is worth it. The honest answer is that he may not need to spend it at all, and that should come before a quotation rather than after.
On the bench
A responsive cursor was treated as evidence of near-complete system load — its appearance requiring the drive read, the system loaded, drivers initialised, display configured and input started, while movement proves the system is running and processing events rather than stalled. The desktop shell drawing taskbar, icons and background is a single late component dependent on the user profile. User profile regions were extracted from the image with system files excluded.
The outcome
The cursor treated as evidence of near-complete load, the drive read independently of the machine, and user regions extracted with system files excluded. Free assessment, one fixed written figure including VAT — and where a drive is this readable, the honest advice comes first. The decode: that cursor means nearly everything loaded. Your drive delivered an entire operating system before the desktop failed to draw, which puts this at the straightforward end.
A system that reaches a blank screen with a working cursor
Stop trying to start it, since each failed attempt writes logs and temporary files onto a drive you want to read. Then consider doing this yourself: connect the drive to another machine as a second drive using an adapter, because a drive that loaded an entire operating system is almost always readable that way. The cursor tells you why — it means the drive delivered the system, drivers initialised, and input is live, so what failed is the single late component that draws the desktop. Your files are in regions none of that touched.
That is a good sign — call Manchester Data Recovery on 0161 871 0788; cursor treated as evidence of near-complete load, drive read independently, honest advice given before any quotation.
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.