Data Recovery Case File · Cameras, Drones & Cards · The Amateur's Thousand

"I'm wary of attempting it, as my IT skills are limited": wariness as wisdom, not weakness — a thousand RAW-and-JPEG photographs assessed and recovered without gambling the only copy on a self-repair

His enquiry showed the good judgement that most protects data: knowing the limits of one's own. "I have about a thousand files on a microSD card that I can't open — image files in RAW and JPG format, copied from a professional card onto the micro." The symptom: opening them in his editing software shows "the icon for each and the file size under properties, but an error states the file is currently unsupported or corrupt." The wisdom: "I know the software offers advice on fixing this, but I am wary of attempting it, as my IT skills are limited — I'm an amateur photographer, not an IT professional." The logistics: housebound with a broken foot, so the card would come by post or upload. His questions — the chances, and the cost — get answered below, but the headline is a defence of his instinct: on a sole copy with no backup, wariness is the correct response, not a failing. The self-repair he declined could, if it went wrong, have written over the very files he's trying to save.

The decode: visible-but-won't-open, the copy as suspect, and why his caution was right

What the symptom means: files that show correct icons and correct sizes but won't open are the signature of data that is present but structurally broken — the filesystem still lists each photo with its real size (so the bytes are there), but something in the file's internal structure, or the filesystem's description of it, is damaged enough that the software refuses to interpret it. This is emphatically not empty or destroyed; it is intact content behind a broken doorway, which is a recoverable condition. His careful observation — noting that size and icon survive while opening fails — is exactly the detail that distinguishes recoverable corruption from true loss.

The copy step, under suspicion: the clue in his account is that the photos were copied from a professional card onto the microSD, and that's where the fault likely entered. Card-to-card and card-to-microSD copies can corrupt if interrupted, if the microSD was faltering, or if the transfer didn't complete cleanly — leaving files that look copied (right size, right name) but carry damage from the journey. It means the professional source card may still hold clean originals, a possibility worth raising with him — but the microSD's thousand can be addressed directly regardless.

Why wariness beats bravery here: his instinct deserves full endorsement, because the software's self-repair path — sound as it may be in capable hands — carries a specific danger in his situation: many repair routines work in place, modifying the original files, and a repair that goes wrong on a sole copy with no backup can convert recoverable corruption into permanent loss. "Limited IT skills" plus "no second copy" plus "in-place repair" is precisely the combination where attempting the fix is the gamble and declining it is the skill. He read his own risk correctly. The professional difference is simple: we work on a write-blocked image, so every repair attempt happens on a copy and the original is never at stake — the safety net his solo attempt would have lacked.

The recovery: imaged first, repaired on the copy, delivered remotely

The card arrived by post and was imaged write-blocked before anything — the sole copy made safe, exactly the protection his instinct had been reaching for. On the image, the corruption resolved as predicted: the photographs present, their structures damaged in the pattern an imperfect copy leaves. Repair ran on the copy across both formats — JPEG and the camera's RAW files reconstructed and validated — with the professional source card's potential clean originals noted as a corroborating avenue. The thousand were recovered to the extent each allowed, verified by opening, and returned remotely to the housebound photographer.

On the bench

His wariness about in-place repair was, on this bench, made structural: the posted card was imaged behind the DeepSpar USB Stabilizer 10Gb before any tool touched a photograph, so every repair attempt in the workflow ran against a copy with the original never at stake — the safety net his solo attempt would have lacked, formalised in hardware. OSForensics profiled the estate — signatures versus extensions, structures versus sizes — locating the copy-introduced damage, and the RAW and JPEG files were reconstructed on the image and verified by opening, a thousand at housebound remove.

The outcome

The photographs recovered and delivered on new media by his preferred remote route — his two questions answered in the honest form: the chances assessed for free before any commitment, the cost as one fixed written figure including VAT, no recovery, no fee. And his instinct formally commended: knowing not to attempt an in-place repair on your only copy is not a gap in IT skill — it is the single most important data-protection judgement there is, and he made it.

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.