There's a particular false hope in a USB stick that still makes the noise. This one, plugged into any machine going, behaved the same everywhere: "it makes the sound when a device is connected however it is not being recognised by the PC". The chime means the computer felt something arrive on the port — electrically, the stick is present. What never happens next is the introduction: the stick's controller, the small chip whose job is to stand up and present the memory to the computer, has stopped doing its job. The chime is the doorbell working; the controller is the one who no longer answers the door — and the Word and PowerPoint files sit in a different chip entirely, usually untouched. So we stop ringing the bell and read that chip directly.
| Media | A USB stick that sounds the connection chime on any computer but is never recognised — documents needed off it. |
| Reported situation | USB stick · connection sound on every machine tried · never appears to the PC · Word and PowerPoint documents wanted · recovery sought. |
| Fault class | Failing controller — the computer senses the connection (hence the chime) but the controller can't present the memory behind it. Data ordinarily intact in the NAND chip; reached by reading that chip directly. Repeated plugging-in is the risk. |
| Equipment used | Stereo microscope over the board first; the NAND chip lifted under hot air and read on a specialist programmer, bypassing the failed controller; the controller's scrambling reconstructed so the raw dump makes sense; documents carved by content in PhotoRec, opened and checked, then delivered on fresh media. |
A USB stick is two chips with one job between them. The memory chip holds your files; the controller manages that memory and speaks USB to the computer. When the controller sickens, you get exactly this presentation: the physical connection registers — that's the chime — and then nothing, because the introduction that should follow never comes. The computer heard someone at the door. Nobody came in.
The instinct everyone follows is to keep trying — this port, that port, the laptop upstairs. It changes nothing, because the fault travels with the stick, and it isn't free: a controller on its way out can behave less predictably with every power-up, and the failure mode you really don't want is the one where it starts making bad decisions about the memory it manages. A stick that chimes without appearing has told you everything it's going to tell you. Further plugging-in is just wear.
The route to the documents doesn't run through the controller at all. The memory chip is removed from the board and read directly in a programmer — the controller bypassed entirely. The raw contents come off scrambled, because every controller keeps its own private arrangement of the data, so that arrangement is worked out and reversed, and the files are carved from the reconstructed image by their content. The controller failed; its filing system can still be understood from the outside.
The stick opened and surveyed under the stereo microscope, controller and memory identified. The NAND lifted under hot air and read on the programmer — the whole chip, every page, into an image. The controller's translation reconstructed from that image, then PhotoRec set to carving: the Word and PowerPoint documents pulled out by content, opened one by one to prove they're whole, and written to fresh media for return.
Documents off the chip, controller left to its retirement. Finding out costs nothing: the diagnostic is free and comes back within two working days of arrival, followed by one fixed written figure. Chip-level work is invasive by nature, so half the quote is payable before it begins — the remainder stands or falls with the recovery, and a failed recovery is never billed for the balance.
Take the hint after the second computer. If two machines chime and neither shows the stick, a third won't break the tie — the controller is the problem and it's inside the stick. Stop plugging it in, resist the recovery-software downloads (software can't reach past a failed controller; it can only ask it nicely, and it isn't answering), and send the stick as it is. The documents are almost always sitting quietly in the memory chip, waiting for someone to come round the back.
Every case file on this site is written up from a genuine enquiry handled for customers across York and North Yorkshire, anonymised to keep client confidence. Each one sets out the diagnostic reasoning and the recovery method our engineers apply to that fault, on the equipment named.
The pin is the doorway, not the data — rebuilt where the board allows it, read at chip level where it doesn't
Half-seen is not half-recovered — the computer's nagging loop ends at chip level, past the broken part
Names without pictures means the index outlived the links — the photos are rebuilt from a read-only image
Free diagnostic inside 2 working days of arrival, one fixed quote, no fix no fee on logical faults — start online or ring the freephone.