He was mid-task when the stick shut its doors. A USB stick of music that "plays fine" was going to be copied to a microSD for his MP3 player, but "the stick will not open up to see the files on it" — on the same Surface laptop he "always" uses. He has an older backup stick, but it holds "only 80% of the files", so he would rather not fall back to it and re-rip his CD collection. A stick that plays but will not open its file list has a logical fault, not a dead one — and because the backup is incomplete, recovering this stick is the only route to the missing 20% he cannot otherwise get back without the discs.
| Media | USB flash stick of music files — content still plays but the drive no longer opens to show its files; an older backup stick exists holding roughly 80% of the collection |
| Reported situation | Stick's music reportedly still plays · drive will not open to display its file listing · same trusted laptop used as always · a backup stick available but only 80% complete · reluctance to rebuild the missing files by re-ripping CDs · recovery of the full current stick preferred |
| Fault class | Filesystem or directory corruption on flash media — the file structures damaged so the listing will not open, with the music data largely intact behind them; card health to be confirmed |
| Equipment used | Stick imaged under a hardware write-blocker before any interpretation · filesystem and directory structures parsed from the image in R-Studio, FAT/exFAT backup copies compared · audio files the damaged directory no longer references carved in PhotoRec · controller and flash health checked on the bench · recovered music validated by playback and reconciled against the incomplete backup to confirm the missing 20% is captured |
A drive that will not open its file list usually has damaged structures, not damaged data. The listing comes from the filesystem's directory records; when those are corrupt, the drive fails to open even though the files themselves sit intact in the data area. That music on the stick reportedly still plays in some contexts is consistent with the data surviving while the structure that indexes it has broken — the files are there, but the catalogue describing them is damaged.
The same trusted laptop failing points the fault at the stick itself. Opening the stick on the Surface he always uses without trouble rules out a sudden software or driver change on his side. This is not a compatibility hiccup; it is the stick's own structures that have gone wrong.
The incomplete backup is what makes recovering this stick genuinely matter. An 80% backup means 20% of his collection exists only on the faulty stick — files he would otherwise have to recreate by re-ripping CDs, the very work he is trying to avoid. This is not a case where a good backup makes recovery optional: the stick holds the only current copy of a fifth of the music, so it is worth recovering properly.
Two routes cover the recovery, and the backup helps verify it. Where the directory structures rebuild from their backup copies, the music returns organised with its folder layout; where they cannot, audio files carve cleanly from the data area by signature. Crucially, the incomplete backup serves as a reference — comparing the recovered set against it confirms the missing 20% has actually been captured, so he knows the recovery genuinely closes the gap.
Everything is done on an image, which protects a stick in an uncertain state. The stick is imaged first under write-blocking and recovery runs on the copy — so no repair attempt writes to a device whose structures are already damaged, and if the stick is physically failing rather than just logically corrupt, imaging captures what is readable before any further deterioration.
The stick's health is checked, and the forward advice follows from it. Most such faults are purely logical, but a failing stick corrupts the same way, so its condition is assessed. Either way, the recovered full collection deserves to live somewhere more durable than a single flash stick — and keeping a complete copy in more than one place is the fix for the 80% problem for good.
The stick was imaged under a hardware write-blocker before anything interpreted it. Filesystem and directory structures were parsed from the image in R-Studio with the FAT/exFAT backup copies compared, and PhotoRec carving run for audio files the damaged directory no longer referenced. The controller and flash health were checked on the bench, and the recovered music validated by playback and reconciled against the incomplete backup to confirm the missing 20% was captured.
Stick imaged, structures rebuilt and the data area carved, and the full collection recovered and checked against the partial backup. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: the stick won't open because its directory is damaged, not because the music is gone. And because your backup is only 80% complete, this stick holds the only copy of the rest — recovered and verified against the backup, the missing fifth comes back without touching your CDs.
Stop writing to the stick and don't run repair utilities against it — a drive that won't open usually has damaged directory structures with the files intact behind them, and repair attempts write to the very device you need preserved. Hold onto your partial backup; it's useful as a reference to confirm the recovery captures what the backup is missing. Recover from an image rather than the stick itself, and once you have the full set back, keep a complete copy in more than one place.
Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.