It is the most upsetting outcome in this whole subject: you run a capacity test, and afterwards the drive is gone — not in Explorer, not mounting, apparently dead. Read this first, before blaming the tool or yourself: the test did not kill a healthy drive. The developer of FakeFlashTest explains this scenario directly, and his explanation matters both for your peace of mind and for what you do next.
If the drive is still partly visible or will not format, our companion guide on a USB drive that won’t format after testing covers the adjacent symptom. The testing guides themselves are the Quick Size Test guide and the main capacity testing guide, with the tool on the download page.
The developer’s explanation: writes to sectors that do not exist
A fake drive’s controller reports a large capacity backed by a small chip. Normal use, for a while, only touches real storage, and the hacked controller copes. A capacity test deliberately writes across the whole reported range, including sectors that do not exist in reality. Faced with sustained writes to non-existent addresses, the hacked controller can become confused, corrupt its own state, or stop responding to the computer altogether — the drive becomes unformattable, undetected, or both.
That is a consequence of the fraud, exposed by the test, not damage inflicted by a legitimate test on a legitimate product. The developer’s framing deserves repeating because it is the honest one: the same failure would have happened in normal use, later, the moment your ordinary files grew past the real capacity and the controller faced the same impossible writes. The only difference the test made is timing — it happened now, on an empty or backed-up drive, inside your return window, instead of months from now with your files inside the blast radius. A genuine drive does not die from having its advertised capacity written to; that is what advertised capacity means.
First checks: is it really gone?
Work through the visibility ladder calmly before concluding anything. Check File Explorer, obviously — but then open Disk Management, where a drive can be present as a device or volume even when Explorer shows nothing, for example because it lost its drive letter or its volume is damaged. If Disk Management shows the device with unallocated or raw space, it is not dead; it is a formatting and partitioning problem, and an empty drive in that state can be reinitialised — although, if it is a confirmed fake, read the verdict section below before investing effort. If Disk Management shows nothing, open Device Manager and look under disk drives, and try the physical checks next.
Those physical checks are quick and worth doing properly: a different port, directly on the computer rather than through a hub; for a card, a different reader; and ideally a second computer entirely. A second PC rules out your machine’s ports, drivers, and security software in one move, and a drive that appears there was never dead — it was a local visibility problem, and our guide on FakeFlashTest showing no drives covers that family of fixes.
If it is truly gone: a paperweight, and a claim
If no computer, port, or reader can see the device at all, accept the practical verdict: it is a paperweight. There is no software resurrection for a controller that no longer enumerates as a device, and a drive in this state held no trustworthy future anyway. Do not let the loss of the object distract you from the claim: a fake that dies under a capacity test is a counterfeit that failed in the most demonstrable way possible, and your evidence — the purchase record, the listing’s claimed capacity, your test screenshots and notes of what happened — supports a refund claim on exactly that basis.
Follow the evidence-based route in our guide on how to get a refund for a fake USB drive: dispute as counterfeit or falsified specifications through the platform, attach the documentation, and let the platform’s process handle any question of returning a dead item, rather than paying privately to ship it. Note clearly in the claim that the drive ceased to be detected during a standard capacity test, which is a documented behaviour of fake controllers, not misuse — testing a storage product’s stated capacity is a normal, reasonable use of it.
What about the files that were on it?
If the vanished drive held files, let the visibility checks finish before you grieve them. A drive that reappears on another computer may still hold readable data, and your priority then shifts immediately to copying — verified copies, newest and most irreplaceable files first, with no further testing until salvage is complete. A drive that remains invisible everywhere, on the other hand, offers nothing to salvage from, which is precisely why testing on arrival, while a drive is still empty, is the discipline this site keeps returning to. The disappearance is worst when it is also a data loss; on an empty new drive it is only a refund errand.
The lesson to keep
Every part of this outcome argues for the habit this site repeats: test on arrival, on an empty or backed-up drive, inside the return window. A fake that will die under testing will die under use; the only variable you control is whether it happens as a refundable event with no data at stake, or as a data-loss event later. If your drive disappeared, you have — despite the frustration — landed on the right side of that trade. Document it, claim it, replace it through a genuine channel, and test the replacement on day one with the tool from the download page. The next drive’s test will take five minutes, and this time a quiet, boring pass is exactly what you want.