Fake flash drives are sneaky. Windows may report a full 1 TB, small files save fine, and everything looks normal — until you fill the drive past its real capacity and older files start coming back corrupted. That is the classic fake-capacity trick: a small chip (say 64 GB) with modified firmware that reports 2 TB. The operating system believes the report, and the drive silently discards anything written beyond the real chip, without ever showing an error.
ValiDrive, a free portable tool from Gibson Research (GRC), was built for exactly this trap. It does not trust the reported size. Instead, it spot-checks 576 evenly spread locations across the whole claimed capacity. At each location it reads the original data, writes unguessable random test data, reads it back to confirm it was really stored, then restores the original data. The test is data-preserving, and the total test data is only about 2.36 MB (576 regions x 4 KB) — yet a fake drive can hardly hide, because the samples span the entire claimed range. Full step-by-step guide in Indonesian: https://www.miftahulrizki.eu.org/2026/10/cara-cek-flashdisk-palsu-pakai.html
Using it takes a few clicks on Windows: download it from grc.com (no installation), run it, plug the drive in again when prompted so ValiDrive identifies the right drive, and click "Validate THIS drive". A 128 GB drive took one tester about 15 minutes; cheap drives can be slower, because ValiDrive transfers only 4 KB at a time and constantly alternates reads and writes.
Reading the map is simple. Green means the location was validated. Blue means a read error, yellow a write error — both mean a troubled drive, but not necessarily a fake one; retry on another port first. Red means no storage: the test data was written with no error, yet did not read back correctly. A map that is green at the start and red after a certain point reveals the real capacity boundary — for example, green up to 64 GB and red afterwards means the real chip is probably 64 GB.
I simulated this spot-check logic on my own computer: 576 points on an image declared as 100 MB but really only 20 MB. Only 115 points validated and 461 reported no storage, with the first failure at about 20 MB — exactly the real boundary. This was a simulation in a VM, not ValiDrive on a physical drive, but the green-to-red pattern is exactly what a fake drive produces.
If your map shows red, stop using the drive for important data, rescue what you can still open, screenshot the map and report (declared size vs validated size), and file a return claim quickly — a "2 TB" drive validated at only 62 GB is not merely broken, it does not match its description. Do not try to fix it by formatting: formatting cannot add storage chips that do not exist.
One last caution: a small size difference is normal. Manufacturers count 1 GB as 1,000,000,000 bytes while operating systems count 1 GiB as 1,073,741,824 bytes, so 64 GB reads as about 59.6 GiB and 1 TB as about 931 GiB — roughly 6.9% less. Suspect a fake only when the gap is far larger.
Read the full Indonesian guide on my blog for the step-by-step walkthrough, the ValiDrive vs H2testw comparison, and the FAQ: https://www.miftahulrizki.eu.org/2026/10/cara-cek-flashdisk-palsu-pakai.html
Top comments (0)