Recently deleted files, healthy drive
The commonest case by a wide margin. The data is intact and only the index entry has gone. Install the tool to a different drive, recover to a third, and it frequently works first time.
On mechanically sound hardware that is exactly right, and free tools resolve a great deal. On a failing drive it is hours of precisely the load it cannot take. One question decides which situation you are in.
Rebuilding a file system or recovering deletions is exactly what these tools are for. Heads, boards, firmware and unresponsive controllers are not — and pointing a scanner at one of those does measurable harm.
Everything else — how much data, how important, how technical you are — is secondary to this.
Recovery software works by reading the drive. That is all it can do. It reads intensively, often for hours, looking for file structures and signatures in whatever the disk gives back.
On a mechanically sound drive that is exactly the right approach, and free or inexpensive tools resolve a great deal — deleted files, a lost partition, an accidental format, a corrupt file system. There is no magic in a laboratory that software cannot match on healthy hardware.
On a failing drive it is the worst possible approach, for the same reason: hours of continuous reading is precisely the load a deteriorating disk cannot take. Drives regularly die partway through a scan intended to save them, and they die having read the parts nobody needed first.
In order. The first one overrides everything after it.
Clicking, grinding, scraping, beeping, or a buzz with no spin. If yes, stop — software cannot address a mechanical fault and every minute of scanning costs you. This question ends the decision on its own.
Check with CrystalDiskInfo or DriveDx, installed to a different drive. Climbing counts mean the disk is deteriorating, and a deep scan will accelerate it.
If the hardware is sound and nothing has been written since, software has a genuinely good chance — and it is the sensible first move.
Employment disputes, insurance claims, anything legal. Then the question is not whether the files come back but whether you can demonstrate nothing was altered, and that needs write-blocked imaging and documented handling.
We would rather tell you this than take the work.
The commonest case by a wide margin. The data is intact and only the index entry has gone. Install the tool to a different drive, recover to a third, and it frequently works first time.
The drive is fine and the map is broken. Tools that scan for file system signatures rebuild partition tables reliably when the hardware is sound.
Cameras and Windows use quick formats, which replace the index and leave the contents. Carving photographs off a formatted card is well within what free tools manage.
Any noise, any climbing SMART counts, a drive that drops off mid-operation, or anything that may be examined later. In those cases scanning makes matters worse rather than better.
So the comparison is a fair one rather than a sales pitch.
It reads hardware software cannot. Imaging equipment controls the drive at a level an operating system does not expose — per-head targeting, timeouts measured in milliseconds rather than seconds, unreadable sectors logged and skipped rather than retried indefinitely. A failing drive that stalls every software tool can often be imaged completely.
It repairs the drive enough to be read. Donor head assemblies, board repair with the original ROM adaptives migrated, service-area rebuilds, controller access in vendor mode. None of that is available to any tool running on your computer, because the drive has to be working before software can begin.
Nothing it attempts makes matters worse. Everything runs against a read-only image, so a failed attempt costs nothing in recoverable data. Software running on the original drive has no such property — and that is the real difference, more than any technique.
Single drives in Manchester are from £300 +VAT after a free 48-hour diagnostic. If the diagnostic shows a healthy drive and a job software would handle, we say so — it costs us the work and it is the correct answer.
It turns on one question: is the drive physically sound? On healthy hardware, software often works and is the sensible first move. On a drive that is failing, scanning is hours of exactly the load it cannot take — and drives regularly die partway through.
Yes, on the right cases — recently deleted files, a lost partition, a quick-formatted card, all on mechanically sound media. Install it to a different drive than the one you are recovering, and recover to a third location.
Listen first: any new noise means stop. Then check SMART with CrystalDiskInfo or DriveDx and look at reallocated and pending sector counts. If either is climbing, a deep scan will accelerate the failure rather than beat it.
Read drives software cannot — per-head imaging with millisecond timeouts and unreadable sectors skipped rather than retried — and repair the drive enough to be read at all, with donor parts, board repair or vendor-mode access. And it works on an image, so nothing it tries makes matters worse.
Yes. If the free diagnostic shows healthy hardware and a job software would handle, we say so. It costs us the work and it is the right answer — there is nothing a laboratory adds to a drive you can still read yourself.
Then software is the wrong route regardless of the hardware. The question becomes whether you can demonstrate nothing was altered, which needs write-blocked imaging, cryptographic hashing and documented handling from the outset.