The drive "appears on Control Panel with the path intact, but it does not appear in My Computer". He had worked through the obvious avenues himself — the command line, Device Manager, and "ImageUSB (to clone it)" — and none of them produced a usable drive. What he has found is the boundary between two layers: Windows can see the hardware perfectly well, and cannot make sense of the volume on it. Device enumeration and filesystem mounting are separate jobs, and a device that enumerates but will not mount has a broken filing structure or a controller that has begun to falter. Cloning it in place was the right instinct, and it failed for a reason worth explaining.
| Media | A USB drive that Windows enumerates and lists in Control Panel with its path intact, but which never appears in My Computer and cannot be opened. |
| Reported situation | USB drive · recognised by the computer · listed in Control Panel with path intact · absent from My Computer · command line, ImageUSB cloning and Device Manager all attempted without success. |
| Fault class | A volume that will not mount — the device is detected but a damaged filesystem, or a controller that is failing to sustain reads, stops Windows presenting it. Files generally intact, reached by imaging read-only on equipment that copes with unstable reads and rebuilding the structure from the copy. |
| Equipment used | Read through a hardware write-blocker on equipment built to handle unstable reads · the flash read directly, or at chip level under hot air where the controller is failing · imaged out to DeepSpar with PC-3000 UDMA behind it in controlled passes, good regions first and weak regions gently · the filesystem read out in R-Studio from the image, the structure rebuilt, files carved by content where references had gone and validated. |
Windows does two separate things with a storage device and it is easy to mistake them for one. First it enumerates: it notices a device on the bus, identifies it, loads a driver and records it in Device Manager and Control Panel. Second it mounts: it reads the partition table and the filesystem and, if both make sense, gives you a drive letter. This drive is passing the first stage and failing the second, which is why it is simultaneously visible and useless.
That narrows the fault to two candidates. Either the filing structure on the flash has been damaged, which is common on a stick pulled out mid-write, or the controller has begun to falter and cannot sustain the reads Windows needs to make sense of anything. The second explains why a straight clone did not work. Consumer imaging tools ask for the whole device in order, at speed, and abort or hang when a read fails — precisely the wrong behaviour on hardware that needs coaxing.
Bench imaging is built the other way round. It reads what is reading well first, secures that, then approaches the difficult regions carefully with retries limited so the flash is not hammered. What comes off is an image, and every attempt at rebuilding the filesystem happens on that image rather than on the original. Which also answers the question of whether he made things worse: a read-only clone attempt does no harm, and stopping when it failed was the right call.
It was read behind a hardware write-blocker in line on equipment designed for unstable media, rather than by asking a general-purpose tool for a straight copy. Imaging ran on DeepSpar behind PC-3000 UDMA in controlled passes — the cooperative regions taken first and secured, the awkward ones approached gently with retries capped. The filesystem was then parsed in R-Studio from the image, the damaged structures rebuilt on the copy, and files whose references had gone were carved by content signature and checked before they went to fresh media.
Imaged read-only in controlled passes, the volume rebuilt from the copy, and the files put onto fresh media. The diagnostic cost nothing; the figure that followed was fixed, written and inclusive of VAT. This one came off through the controller rather than needing the flash worked directly, which kept it on no fix, no fee terms. Had the memory itself needed reading at chip level, half the quote would have been payable in advance against parts and bench time, with the balance only on success — and that distinction is made before the work, never after it.
You have already found the useful clue: something that shows in Control Manager or Device Manager but never in My Computer is being detected as hardware and refused as a volume, which puts the fault in the filing or the controller rather than in the cable. Stop the tools that want to fix it. Anything offering to initialise the disk, assign a partition or repair the filesystem will write to the flash, and every write lands on the structures a recovery would rebuild from. Cloning it read-only was a reasonable idea and doing no harm; the reason it failed is that consumer imagers demand a clean run from start to finish, while failing media needs the awkward regions approached last and gently. Leave it alone and let it be imaged properly.
Every case file here is written up from a real enquiry handled for households and businesses across Norwich and Norfolk, anonymised so that nobody is identifiable. Each sets out the reasoning behind the diagnosis and the method used on that particular fault, with the equipment named.
Diagnosis costs nothing and takes up to 2 working days from arrival, the quote is fixed in writing, and logical work runs no fix, no fee — start online or ring the freephone.