Data Recovery Case File · Formatted & Logical Faults · It Names the Layer
Decoding a Very Specific Message
His enquiry quoted the error rather than paraphrasing it, which makes this one of the more precisely answerable cases in the archive. A pen drive holding all his working data: "it doesn't work any more. The message when I try to open it says 'The file or directory is corrupted and unreadable.'" Most error messages in computing are generic and cover a dozen causes. This one is unusually specific and it names the layer that has failed — which is good news, because that layer is small, it sits over data that is entirely intact, and it is exactly what a reconstruction rebuilds. The bad news is what Windows will suggest doing about it.
| Media | USB pen drive holding professional working data — volume mounting with directory access returning a corruption message |
| Reported situation | Drive connecting and being recognised · attempts to open returning a specific filesystem corruption message · working data held · no impact or liquid reported |
| Fault class | Filesystem structure damage over intact content — directory records unparseable while the device enumerates and reports capacity normally |
| Equipment used | No repair command run · imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · directory and allocation structures reconstructed on the image from backup copies · files verified by opening |
The decode: what that wording means, and the command to refuse
Why the message is informative: for Windows to produce it at all, a great deal has already succeeded. The drive received power, enumerated, identified itself, reported its capacity, and was recognised as a volume with a filesystem Windows knows. It then tried to read the structures describing the contents and could not parse them. That is a failure at a very specific layer — the directory records — and everything above and below that layer is working. Compare it with a drive that produces nothing at all, or one that offers to format because no filesystem could be identified: this message means the filesystem was found and one part of it is unreadable.
Why "file or directory" is the useful phrase: the system is reporting that the entry it needs — either the record describing a file or the record describing the folder containing it — cannot be interpreted. Those records are small, concentrated, and heavily referenced, which is why damage there stops access to a great deal while the actual file content sits untouched across the rest of the device. His working data is physically present. Nothing currently describes where it is.
Why this is among the most recoverable situations: filesystems keep backup copies of their key structures at known positions, precisely because this kind of damage is anticipated. Reconstruction locates those, rebuilds the directory from them and from the allocation records, and returns the folder tree with filenames and dates intact — rather than a carve producing unnamed files.
The command to refuse, and Windows will suggest it: the standard advice for this exact message is to run a disk check with the repair option. That is a write operation. It examines the damaged structures, decides which records to trust where they disagree, discards what it cannot reconcile, and writes its conclusions back — frequently moving orphaned content into a recovery folder with generic numbered names. On a lightly inconsistent volume it works. On this fault it can overwrite exactly the records a reconstruction rebuilds from, and it strips filenames along the way. For a customer whose working data is at stake, that is the difference between getting his folders back and getting a numbered heap.
What to do instead: stop connecting it, run nothing against it, and refuse any offer to check, repair or format. The elimination is complete — the message itself has already established more than further attempts can.
On the bench
No repair command was run, since the standard remedy for that message writes its decisions back to the device and can overwrite the very records a reconstruction reads. The drive was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb, so that everything afterwards happened against a copy. On the image the directory and allocation structures were located — including the backup copies the filesystem maintains at known offsets — and reconstructed until the volume mounted from the copy with its folder tree, filenames and dates intact. The files were verified by opening.
The outcome
The structures rebuilt from their backup copies on a write-blocked image, with folders and filenames returned intact. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone seeing that exact message: it is unusually specific and it is good news — the drive powered, enumerated, reported its capacity and had its filesystem recognised, and what failed is the small layer of directory records describing where things are, with your data physically intact underneath; filesystems keep backup copies of those structures, so they can usually be rebuilt with filenames and dates. But the standard advice for that message is a repair command that writes its decisions back, and on this fault that is the destructive step.
Getting "the file or directory is corrupted and unreadable"
Don't run the disk check that everyone will tell you to run. That message is more encouraging than it sounds: for Windows to produce it, your drive has powered up, identified itself, reported its capacity and had its filesystem recognised — what's failed is the small set of records describing where your files are, and the files themselves are sitting intact underneath. Filesystems keep backup copies of those records, so they can usually be rebuilt with your folder names and dates intact. The standard remedy is a repair command, and repair means writing: it chooses between records that disagree, discards what it can't reconcile, and dumps orphaned content into a folder full of numbered files. On this particular fault that overwrites exactly what a proper reconstruction reads. Stop connecting the drive and refuse every offer to check, repair or format it.
Don't run the repair — call Newcastle Data Recovery on 0191 406 1051; imaged write-blocked, directory rebuilt from the filesystem's own backup copies, folders and filenames returned.
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.