Data Recovery Case File · Second Fixes & Trade Handoffs · The Application Is the Asset
Software Written for One Organisation Has No Installer to Fall Back On
This enquiry from a research laboratory names an unusual recovery target. A read error on a ruggedised laptop whose drive "contains some bespoke software that is critical to our work" — not documents, not records, but the application itself. That changes what has to be captured, because software written for one organisation exists in one place, and a recovery aimed at user folders would step past all of it.
| Media | Ruggedised laptop hard drive reporting a read error — holding bespoke application software critical to the organisation, with no vendor installer available |
| Reported situation | Ruggedised laptop in laboratory service · drive reporting a read error · bespoke application software held on the drive · software described as critical to the organisation's work · quotation requested for recovery · content beyond the application not specified as the priority |
| Fault class | Read error with application recovery as the objective — installed software distributed across system directories, configuration stores and registries rather than user folders |
| Equipment used | Recovery scope defined as the full installed application rather than user content · full-disc imaging performed write-blocked under strict per-sector timeouts rather than selective extraction · system directories, configuration stores and registry hives captured alongside program files · installed application dependencies enumerated from the image · content validated against a matching test environment |
The decode: where an installed application lives, and why the whole disc is captured
Why bespoke software is a different proposition: there is no fallback. Commercial software can be downloaded again; software written for one organisation exists only where it was installed.
Why the original developer may not help: time and circumstance. Bespoke work is frequently years old, and the developer may have moved on, closed, or no longer hold the source.
Where an installed application physically sits: in several places at once. Program files in one directory, configuration in another, registry entries in a system database, and supporting libraries in shared system folders.
Why that makes selective recovery the wrong approach: pieces would be missed. Capturing the program directory alone produces files that will not run.
Why a full image is therefore the right method: it takes everything. An image of the whole disc contains the application, its configuration, its registrations and its dependencies without needing to know in advance where they are.
Why that also protects against the unknown: nobody can list the dependencies confidently. A bespoke application may rely on components installed years ago and long forgotten.
What the image makes possible afterwards: reconstruction rather than reinstallation. The application can be brought up in a matching environment built from the image, without an installer existing.
Why the read error matters to the method: it constrains the capture. A drive returning errors is imaged with capped timeouts, healthy regions first, and difficult regions revisited.
Why that ordering is more important than usual here: the target is spread out. An application distributed across the disc needs a complete capture rather than a partial one.
What must happen now: the machine out of service. A drive reporting read errors is degrading, and continued use is spending capture time that has not been used yet.
On the bench
Recovery scope was defined as the full installed application rather than user content — bespoke software existing only where it was installed, with no vendor installer and often no surviving developer, and an installed application distributed across program directories, configuration stores, registry entries and shared system libraries. Selective capture of a program directory therefore yields files that will not run. Full-disc imaging was performed rather than selective extraction, with dependencies enumerated from the image.
The outcome
Scope defined as the full installed application, full-disc imaging performed under capped timeouts, and dependencies enumerated from the image. 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: an installed application is not in one folder. It sits across program directories, configuration stores, registry entries and shared libraries — which is why the whole disc is captured rather than a selection.
When the software matters more than the documents
Say so explicitly and ask for a full-disc image rather than selective extraction. An installed application lives in several places at once — program directories, configuration stores, registry entries and shared system libraries — so capturing the program folder alone produces files that won't run, and nobody can list the dependencies of years-old bespoke software confidently. A full image lets the application be reconstructed in a matching environment without an installer existing. Take the machine out of service now.
Ask for a full image — call Cambridge Data Recovery on 01223 655015; scope defined as the whole installed application, full-disc imaging under capped timeouts, dependencies enumerated from the image.
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.