Data Recovery Case File · Formatted & Logical Faults · Whose Problem Is Being Solved
Software Recommends Whatever Makes the Software Work
His enquiry describes an instinct fighting a prompt, and asks for confirmation he is right. A drive not being recognised and crashing his file browser, where "my photography software is recommending I reformat the disk, which I don't want to do until I can be sure that the data on the disk can be recovered." He is right, and the reason is worth stating plainly — an application suggesting a format is solving its own problem, because it needs usable storage and has no means of caring what is on it.
| Media | Portable external hard drive — not enumerating reliably; causing host file browser to terminate; application prompting for reformatting |
| Reported situation | Drive not being recognised by the host · host file browser crashing when the drive is connected · photography application recommending the disk be reformatted · owner declining pending assurance · contents required |
| Fault class | Device returning malformed responses — host software failing rather than reporting; format neither appropriate nor likely to complete |
| Equipment used | Application prompt assessed for whose requirement it serves · browser termination interpreted as malformed device responses rather than clean errors · no format permitted · device addressed through hardware with imposed timeouts · imaged write-blocked under strict per-sector limits |
The decode: what the prompt is for, and what the crash tells us
Why an application offers to format: because it has encountered storage it cannot use, and formatting produces storage it can. From the application's position that is a complete and correct solution — it will have a working drive, which is the only thing it was designed to want.
What it is not doing: assessing whether the contents matter. It has no way to, and no mechanism for weighing what would be lost against what would be gained. It is not being careless; the question is outside its scope entirely.
Why this generalises beyond his case: every prompt in computing offering to repair, initialise, prepare or reformat comes from software whose objective is a functioning device. The question worth asking of any of them is whose problem is being solved — and the answer is almost never the user's.
Why his instinct deserves the confirmation he asked for: declining a destructive prompt until the position is established is exactly right, and it is the single behaviour that most often preserves a recovery.
Now the crash, which is the more informative symptom. A file browser terminating is not the same as a file browser reporting an error. An error means the device answered and said no, which software handles routinely. A crash means it received something it could not process — a malformed response, or a hang the handling was not written for.
What that indicates about the device: it is not failing cleanly. A drive returning proper error codes is a drive whose electronics are working and whose surface is not; one producing responses that break the software above it has a fault at the controller or the interface.
Why that means the format would not have helped anyway: formatting requires sustained writing to the device. A drive that cannot survive being listed is unlikely to survive being written across — so the operation would probably fail partway, having destroyed the structures without producing the working drive the application wanted.
What must not happen: no format, no repair utility, and no further connection to machines being used for anything. A device that crashes host software should not be introduced to a working system.
On the bench
The application prompt was assessed for whose requirement it serves — software encountering unusable storage and offering the operation that produces usable storage, without any mechanism for weighing existing contents. Browser termination was interpreted as malformed device responses rather than clean errors, an error being handled routinely while a crash indicates responses the handling was not written for, which points at controller or interface rather than surface. No format was permitted.
The outcome
The prompt assessed for whose problem it solves, the crash read as malformed responses, and the device addressed through hardware with imposed timeouts. 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: you were right to refuse. An application offering to format wants usable storage, which formatting provides — it has no means of weighing what is on the drive. And a format would likely have failed partway anyway.
Software recommending you reformat a drive
Refuse it, and ask whose problem the suggestion solves. An application offering to format has encountered storage it can't use, and formatting produces storage it can — which is a complete solution from its position, because it has no mechanism for weighing what's on the drive against what it needs. That's true of every repair, initialise or prepare prompt in computing. If your file browser is crashing rather than reporting an error, that's worth knowing too: an error means the device answered and declined, while a crash means it returned something the software couldn't process, which points at the controller rather than the surface.
You were right to decline — call Oxford Data Recovery on 01865 593000; prompt assessed for whose requirement it serves, crash read as malformed responses, device addressed through hardware with imposed timeouts.
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.