Running a capacity test takes minutes. Understanding the result correctly is what makes those minutes worthwhile — and in that sense the log is the product of the test. This guide explains what a FakeFlashTest pass actually proves, what a failure is telling you (including the real capacity hiding inside the log), and the one habit that turns a test into evidence: screenshotting the result.
If you have not run a test yet, start with our step-by-step guide on how to test a USB flash drive for fake capacity, and get the tool itself via the download page. If your drive has already failed and you want the action plan, go straight to Fake Drive Confirmed: What to Do Next after reading what the failure means here.
What a pass means — and what it does not
A pass means the test completed and the data it wrote was read back correctly: for the Quick Size Test, the 512-byte marker blocks at intervals across the reported capacity, starting from the end, all verified; for Test Empty Space, the test files written into the free space verified at their interval checks. In plain terms, the drive behaved consistently with having the capacity it claims, at the points actually tested.
A pass does not mean the drive is perfect. The developer is explicit that FakeFlashTest is a quick screen: it does not thoroughly test all of the memory and does not check for faults everywhere. A defect sitting between two sampled points, or a weakness that only appears under sustained heat or months of use, can survive a pass. That is why a full write-and-verify test such as H2testw, which can take hours, remains the thorough reference — and why backups matter even for drives that pass every test you own. Read a pass as “no sign of fake capacity in a fast screen,” which for a newly bought drive from a reputable seller is normally a reasonable basis to proceed.
What a fail means: read the real capacity in the log
A failure means data written to the drive could not be read back correctly — markers mismatched, test files corrupted, or errors once writes passed a certain point. On a fake drive, that failure point is the story: it indicates approximately where the real storage ends and the fiction begins. A card sold as very large that starts failing at a small fraction of its claimed size has been caught with a much smaller real chip inside.
Do not reduce a fail to “it didn’t work.” Note the details the log gives you: which test you ran, the reported capacity, where errors began, and any real-capacity figure the tool states. Those details distinguish a fake-capacity verdict from a generic fault, and they are exactly what a marketplace dispute reviewer needs to see. If every drive fails on your PC — including a known genuine one — suspect interference on the computer instead, and use Safe Mode as the developer advises; that specific pattern signals a software problem, not a drawer full of fakes.
Screenshot the log before you do anything else
Before you format, retest, or remove the drive, screenshot the result window and save the image somewhere safe — not on the tested drive. That screenshot pairs the drive’s claimed capacity with the test’s measured verdict in a single piece of evidence, and it takes five seconds to capture.
The payoff comes if you need your money back. Our complete walkthrough, How to Get a Refund for a Fake USB Drive, is built around this evidence: test first, document the gap between advertised and real capacity, then open the dispute as a counterfeit or falsified-specification claim. Sellers and platforms respond differently to “the test tool says this 512 GB drive fails at a fraction of that” with a log attached than to “it doesn’t work properly.” Keep the screenshot until the refund is resolved, even if you reformat or return the drive.
Borderline and confusing results
Sometimes the picture is mixed: a Quick test pass but errors in Test Empty Space, a test interrupted by a disconnect, or a very slow run you stopped early. Treat interrupted tests as no result at all — reconnect the drive directly (no hub), run as administrator, and complete a full run before concluding anything. Treat any completed test with genuine read-back errors as a failure to trust the drive until a clean, complete retest on a known-good setup says otherwise, ideally on an emptied drive.
If results differ between two computers, believe the pattern, not the single run you prefer. A drive that fails cleanly on a second PC is telling you something. A drive that only fails on one PC, alongside other known-good drives failing there too, is pointing back at that PC’s security software or drivers.
Deciding what to do with the verdict
Pass, from a reputable purchase, tested on arrival: format the drive, use it, back up elsewhere as normal. Pass, but the deal was suspiciously cheap or the seller unknown: consider the overnight full test before trusting it with anything irreplaceable. Fail, at any point, with errors in the log: stop writing to the drive, keep the screenshot, salvage anything that still opens if the drive held data, and pursue the refund route while you are inside the return window.
The result screen is not the end of the process; it is the decision point. FakeFlashTest gives you a fast, honest screen — what protects your files and your wallet is reading that screen accurately and acting on it the same day. The tool is on the download page whenever you need to test the next drive, and the next one deserves the same five minutes.