Data Recovery Case File · Solid State & Flash · It Answered and Said Nothing Is Here
Enumerated, Initialised, and Reporting Zero Capacity
His enquiry quotes the message exactly, which makes it answerable. A 64GB stick "that is coming up on the file manager, but when you click on it, the dialogue box is asking me to insert a disk into the drive. It only stopped working yesterday and I have tried different ports on different computers." That message is not the same as a device failing to start — it means the stick got all the way through its introduction, was brought into service, and then told the computer it contains no media at all.
| Media | 64GB USB flash drive — enumerated and presented as a drive letter; host reporting no media present on access; behaviour consistent across ports and machines |
| Reported situation | Stick appearing in the file manager as a drive · host prompting to insert media when the drive is opened · failure occurring the previous day · multiple ports tried · multiple computers tried · behaviour unchanged |
| Fault class | Controller reporting zero-capacity media — translation layer or configuration read failure; memory readable past the controller |
| Equipment used | No repeated connection attempts · enumeration and reported capacity read write-blocked under strict timeouts (DeepSpar USB Stabilizer 10Gb) · chip-level read past the controller · translation layer reconstructed in software · files validated by opening |
The decode: what the message means, and why it is a specific finding
Why the stick appears at all: because it completed everything a device has to do to be usable. It drew power, announced itself, stated what it is, and was brought into service by the host — which then assigned it a drive letter. All of that succeeded. A device that failed earlier would either be absent or reported as unable to start, and neither is what he is seeing.
What "insert a disk" actually reports: the host asked the device how much media it holds, and the device answered zero. That phrasing exists for removable-media drives — a card reader with no card in it produces the same message, quite legitimately. Here it is a stick reporting that it contains no memory, which is not a state it can be in, and therefore a report about the controller rather than the truth.
Why the controller says that: a flash controller reads internal configuration on start-up — the capacity, the geometry, and the tables mapping logical addresses to physical memory locations. When it cannot read those, it cannot state a capacity, and reporting zero is what its firmware does in the absence of an answer. So the message is the device saying I cannot describe my own contents.
Why the memory is untouched: a controller that cannot read its configuration has not written to or erased anything. The memory holds what it held. The component that knows how to interpret it has stopped working, and that is all.
Why more ports and more computers cannot help, and this is worth saying because it is the natural next step: the fault is inside the device, so every host will get the same answer. His testing was worth doing once to eliminate the machine, and it has done that thoroughly. Further attempts change nothing.
Why this is a good position on a stick specifically: a flash drive holds a single memory package and a comparatively simple controller, and the pattern linking addresses to physical locations can be reconstructed from the memory contents themselves. So the memory can be read directly through the manufacturer's test points, bypassing the failed controller entirely, then descrambled, error-corrected and reassembled in software. Controller failures on sticks are routinely recoverable — which is not true of the same fault on a solid-state drive.
What not to run: anything offering to format or initialise it, since the host sees a drive with no media and will suggest exactly that.
On the bench
No repeated connection attempts were made, the fault being internal to the device and every host returning the same answer. Enumeration and reported capacity were read write-blocked under strict timeouts behind the DeepSpar USB Stabilizer 10Gb — confirming that the device completed its introduction and was brought into service before reporting zero capacity, which places the failure at the configuration read rather than at initialisation. The memory was read at chip level past the controller, the translation layer reconstructed in software, and files validated by opening.
The outcome
The failure located at the configuration read, the memory recovered past the controller and the contents reconstructed and validated. 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: that message means the host asked how much media the device holds and got zero. A stick cannot actually be in that state, so it is a report about the controller — which reads its capacity and mapping tables on start-up and, unable to read them, reports nothing. Your memory is untouched behind it.
Stick that appears as a drive and asks you to insert a disk
Stop trying other ports and machines — the fault is inside the device, so every computer will give you the same answer, and your testing has already eliminated the host thoroughly. That message is more specific than it looks. Your stick completed everything needed to be usable: it drew power, announced itself, was brought into service and given a drive letter. Then the host asked how much media it holds and the device answered zero. A stick can't genuinely be in that state, so it's telling you the controller couldn't read its own configuration — the capacity and the tables mapping addresses to memory. Your data is untouched behind it. Don't accept any offer to format or initialise.
Don't format it — call Guildford Data Recovery on 01483 901310; enumeration and reported capacity read under strict timeouts, memory read at chip level past the controller, files checked by opening.
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.