If you have landed here without a confirmed result, run the test first using our guide on how to test a USB flash drive for fake capacity and the tool from the download page, and read our explainer on how to read FakeFlashTest results so the failure is documented before you act. If the failure is confirmed and screenshotted, start at Step 1 — in order.

1. Stop writing to the drive immediately

Every further write to a fake drive risks overwriting more of what is already there, because writes past the real capacity wrap around onto earlier data. So stop: no more copying to it, no “let me just add this one file,” no using it as temporary storage while you sort things out. Safely eject it if you are not actively salvaging from it in Step 2.

Resist two tempting experiments. Do not reformat it “to see if it helps” — formatting will not restore capacity that never existed, and it destroys structure that salvage might have used. And do not re-run destructive tests for curiosity. You have your verdict and your screenshot. From here, the drive is evidence and a salvage source, nothing more.

2. Salvage what still opens — copies first, newest first

If the fake held real files, salvage methodically. Work from the drive to a folder on your computer — copies only, never moving or editing in place. Prioritise in this order: first, the files you cannot replace and have no other copy of; within those, start with the most recently written files, because they are the likeliest survivors. Wrap-around overwrites the oldest data first, so recent files often sit within the real portion of the chip and open perfectly, while older files are the most likely to be corrupt.

Verify as you go: open each salvaged file on the computer, not from the drive, and check it properly — play videos through, open photos at full size, open documents beyond the first page. A file that copies without error can still be corrupt inside. Keep a simple list of what verified clean and what did not; that list shapes Step 3, and it prevents the false comfort of a folder that merely looks complete. Work steadily and do not interleave salvage with any writing to the fake — reading is what you want, writing is what endangers the rest.

3. Consider recovery software — with honest expectations

Set expectations correctly before spending hope or money. Data-recovery software offers a chance — only a chance — to recover deleted or formatted files that have not been overwritten. On a fake drive, the central damage is overwriting: bytes replaced by later writes are gone, and no software can reconstruct data that no longer exists on the chip. Recovery tools cannot un-wrap the wrap-around.

Where recovery can legitimately help is the margins: files that were deleted but whose space was never reused, or a file system damaged while the underlying data in the real-capacity region remains intact. If your salvage in Step 2 left important gaps, a reputable recovery tool such as EaseUS Data Recovery via /go/easeus-data-recovery is a reasonable attempt on the files that were lost by deletion or formatting — with results that will vary and cannot be promised. Scan the fake (or better, an image of it) and save anything recovered to your computer, never back to the fake itself. If a tool or service promises to definitely restore overwritten files from a fake drive, that promise is the second scam.

4. Claim your refund with the test evidence

With your data secured as far as possible, turn to the money. You hold the strongest refund position a buyer can have: a capacity test log showing the drive failing at a fraction of its advertised size. Follow the full evidence routine in our guide on how to get a refund for a fake USB drive — screenshot of the log plus the listing, dispute opened as counterfeit or falsified specifications on Amazon, eBay, or AliExpress as applicable, and the platform’s own process for any return shipping rather than paying privately at a seller’s request.

Do this promptly even if salvage took a day; windows close. Keep the drive until the claim resolves, in case the platform asks for anything further, but keep it out of service. A refunded fake you continue to use for “unimportant” files has a way of ending up holding an important file on a busy day.

5. Replace it with genuine storage — and back up properly

Buy the replacement through a genuine channel — the brand’s own store or an authorised retailer — accepting that real capacity costs real money, and test the new drive on arrival just as you tested this one. Then fix the underlying vulnerability this episode exposed: the fake hurt most if it held the only copy of anything. Keep copies so no single drive can take the only version of a file — the familiar 3-2-1 idea of multiple copies, on different media, with one copy elsewhere. A cloud backup via /go/pcloud is one straightforward way to hold that off-device copy, so a future hardware lie or failure is an inconvenience, not a loss.

Finally, what about keeping the fake itself, reprogrammed to its true size? Our honest treatment in Can You Fix a Fake USB Drive to Its Real Capacity? explains the MPTool route — and why, with reject-grade flash inside most fakes, a “fixed” fake should never be trusted with important data. Tinkering is fine; reliance is not. Stop, salvage, stay honest about recovery, claim with evidence, replace and back up: five steps, and the fake has cost you an afternoon instead of your files. Keep FakeFlashTest from the download page in your routine, and the next fake — if one reaches you — will be caught on day one.

If you can run a tool, do — it is faster and gives you a log you can use as evidence. Our main guide on how to test a USB flash drive for fake capacity covers the tool route, with the software itself on the download page. Use this manual method when a tool is genuinely not an option, or as a first sanity check while a download is still in progress.

The principle: fill past the lie, then verify

A fake drive’s controller reports a large capacity while hiding a small chip. Writes within the real capacity succeed genuinely. Writes beyond it wrap around and silently overwrite earlier data, while the folder listing continues to look normal. So a manual test must do two things, not one: fill the drive well beyond any plausible real capacity for a suspicious bargain — ideally toward its full claimed size — and then verify the earliest files, because those are the ones wrap-around destroys first.

Simply copying files until Windows says the drive is full, and seeing no error, proves nothing. The copying can report success throughout, because the controller accepts the writes and discards or overwrites quietly. Verification — opening, playing, or hashing the files afterwards — is the actual test. Skipping it is the mistake that lets fakes pass casual checks in shops and in early use.

Method 1: Fill with large known files

Choose source files that are large, known-good, and easy to verify: video files you can play, large photo collections, or disc images whose behaviour you know. Keep them on your computer as the reference copies — never move the originals, always copy. Fill the suspect drive in batches, noting roughly how much genuine data you have written at each stage, and note which files went on first.

When the drive is as full as you can reasonably make it, safely eject it, reconnect it (a fresh connection prevents cached views from misleading you), and then verify starting with the earliest files you copied. Play the first videos from the start and from near the end. Open the first photos at full size. If the earliest files are corrupt while the most recent ones play, you are looking at the wrap-around signature. If you have files with known checksums, or you recorded hashes before copying, compare the hashes of the copies on the drive against the originals — a mismatch is unambiguous, and hashing is the most rigorous manual check available. Even a sample of the earliest files, fully verified, tells you more than a folder listing ever will.

Method 2: The developer’s folder approach

The FakeFlashTest developer describes a simple manual variant based on folders of known content — organising the fill into clearly labelled folders (the idea appears in his material as TESTDIR folders of photos). The structure is the value: fill the drive folder by folder, each containing photos or files you can identify at a glance, in a known order. Afterwards, open the earliest folders and check the contents display correctly.

Ordered folders make the failure point visible. If the first several folders are corrupt but the last ones are fine, you have not only detected the fake — you have estimated its real capacity, from the amount of data that survived intact. Label folders by cumulative size as you go and that estimate becomes reasonably concrete, which is useful information for a refund conversation even without a tool log.

The honest limits of the manual method

First, it is slow. Filling a drive that claims a very large capacity with real files, at real USB speeds, can take a very long time — far longer than a sampling test, which is precisely why tools like FakeFlashTest exist. Its Quick Size Test, explained in our Quick Size Test guide, checks marker blocks at intervals across the whole claimed capacity instead of occupying all of it, reaching a verdict without a full fill.

Second, it is imprecise unless you hash. “The videos seemed to play” can miss corruption near the ends of files or in files you spot-checked too briefly. Third, a manual fill gives you no standardised log to attach to a marketplace dispute; screenshots of failed files help, but a tool’s result window stating real versus claimed capacity is cleaner evidence. Fourth, like any fill, it stresses a fake’s controller for a sustained period — acceptable on a new suspect drive you may return, another reason to do it before loading anything precious.

When manual is enough — and when it is not

A manual fill test is enough to answer a personal, low-stakes question: “is this bargain drive obviously fake?” If the earliest files corrupt, you have your answer, and you should stop writing, treat the drive as a fake, and pursue the refund route with whatever screenshots you can capture. If everything verifies after a genuinely full fill and thorough checking of the earliest data, the drive has survived a stronger test than most fakes can pass.

For high-capacity drives, for evidence you intend to submit, or whenever time matters, use the real tool instead — that is the recommendation, not a footnote. Download FakeFlashTest from the download page, run it as administrator, and let the marker blocks interrogate the whole claimed capacity in a fraction of the time a fill would take. The manual method’s real value is that it works anywhere, with nothing: a borrowed computer, no download, just files, patience, and the discipline to verify the first files, not the last.

The testing step uses FakeFlashTest. If you have not run it yet, our guide on how to read FakeFlashTest results explains exactly what to capture and why, and the action plan in Fake Drive Confirmed: What to Do Next covers what to do with the drive itself. Everything here is general guidance about presenting a genuine counterfeit claim clearly — not a legal promise about any individual case, which will always depend on the platform’s policies and your circumstances.

Step 1: Run the test and fix the facts

Download FakeFlashTest via the download page, extract the official ZIP (extraction password fake), and Run as Administrator — the tool lists no drives without administrator rights. Back up anything on the drive first (one test mode is destructive), then run the Quick Size Test for the cleanest capacity verdict, and let it complete.

When it finishes, establish three facts before you contact anyone: the capacity as advertised and as shown by Windows, the behaviour the test found (where read-back errors began, or the real capacity the log indicates), and the purchase facts (order number, seller, date, and listing title showing the claimed capacity). A drive advertised at a huge capacity that fails at a small fraction of it is not a matter of opinion — it is a mismatch between the listing and the product, measured with a tool. Fixing those facts in writing before you open the claim keeps your account consistent at every step.

Step 2: Screenshot the log — your central evidence

Screenshot the FakeFlashTest result window showing the failure, and keep the listing page too: save or screenshot the product listing with its claimed capacity and the seller’s name before it can be edited or removed. Together, those two images tell the complete story in seconds — this is what was promised, this is what a capacity test measured.

Keep the screenshots somewhere safe that is not the fake drive itself. If the platform offers an evidence upload in the dispute flow, attach both. If a seller messages you asking for proof, send the same images rather than new descriptions. Consistency is persuasive: one test, one log, one clear gap between advertised and real.

Step 3: Open the dispute as counterfeit, not as faulty

Framing matters. A fake-capacity drive is not a genuine product that broke; it is a counterfeit or falsified-specification item — the capacity in the listing was never true. On Amazon, eBay, and AliExpress, use the return or dispute reason that matches that: item not as described, counterfeit, or falsified specifications, according to the options the platform presents. State the facts plainly: the advertised capacity, the capacity the test evidences, the tool used, and that files written beyond the real capacity are overwritten and lost.

Then keep communication factual and brief. You do not need to argue about intent or accuse the seller personally; the test log does the work. Decline detours that waste your return window — for example, troubleshooting rituals for a capacity lie, or replacement with another identical unit from the same listing. What you are owed is your money back for an item that was mis-sold; a replacement fake solves nothing.

Step 4: Handle return-shipping traps calmly

A common friction point is return shipping: a distant seller may suggest you post the item back at your own expense, which can cost a significant share of the refund. Handle it through the platform, not privately. Counterfeit and not-as-described cases are treated differently from change-of-mind returns on the major platforms, and the platform’s own process — including any prepaid label, refund-without-return decision, or escalation to platform support — is the route to follow. If the first response is an unhelpful template, escalate within the platform with the same evidence attached, rather than paying to ship a counterfeit at your own cost on a seller’s say-so. Keep copies of every message inside the platform’s system, so the record is complete if support reviews it.

Do not let the clock beat you. Return and dispute windows are finite, which is one more reason to test on arrival rather than on discovery months later. If you are reading this with a drive you bought some time ago, still open the case promptly with the evidence — a documented counterfeit claim is stronger late than a vague complaint would be early — but expect the process to be easier inside the standard windows.

Step 5: Replace it with a genuine drive

Once the refund is moving, replace the drive through a channel you can trust, rather than re-rolling the dice on another too-good listing. The official SanDisk store via /go/sandisk-store and a genuine Samsung BAR Plus via /go/samsung-bar-plus-amazon are the kind of routes that remove the impersonation risk: brand store, real product, real capacity. Apply the price sanity you have now learned — genuine high capacities are premium products, and a replacement at a fraction of the real price is not a saving.

And when the replacement arrives, test it too, on the day it arrives, before it holds anything. That five-minute habit is what turns this whole unpleasant experience into a one-off: evidence first, dispute as counterfeit, platform process for shipping, genuine replacement, test on arrival. The tool is waiting on the download page for the next drive as well — make the test part of every storage purchase from now on.

Testing takes minutes with FakeFlashTest, as our guide on how to test a USB flash drive for fake capacity shows, using the tool from the download page. Read this explanation first, though, and you will understand exactly what that test is catching — and why a drive can feel genuine right up to the moment it betrays you.

The firmware trick at the heart of the scam

Inside a fake 2TB drive there is not 2TB of storage. There is a small flash chip — commonly something like 8 GB or 16 GB of real capacity — and a controller whose firmware has been hacked, or clocked, to lie about it. When your computer asks the controller how large the drive is, the hacked firmware reports 512 GB, 1 TB, 2 TB, or an even larger fantasy figure, regardless of what is physically soldered inside.

Everything downstream believes the controller. Windows formats the drive to the reported size, shows the reported free space, and lets you copy files without complaint. The lie lives in the one component you cannot see, which is why visual inspection, packaging, and even the properties dialog in Windows tell you nothing. Only writing data across the claimed capacity and reading it back — a capacity test — can expose a mismatch between the report and the reality.

Context makes the claim itself a giveaway, once you know it: genuine USB flash drives top out at about 2 TB, and genuine drives at that level are premium products from major brands at premium prices. A listing offering that capacity, or far more, for a fraction of what the real thing costs is not selling the same product more cheaply. It is selling a tiny chip and a lie about its size.

Wrap-around: how your files actually get destroyed

The data loss mechanism is called wrap-around, and it explains the scam’s cruellest feature: the earliest files are destroyed by the newest ones. While total writes stay within the small real capacity, everything works. Once you write past that real limit, the controller has nowhere genuine to put the data, so addresses wrap back to the beginning of the chip — and new files silently overwrite the space where your older files live.

Critically, the drive’s directory is not honestly updated to show this destruction. The folder listing still looks normal: names, folders, and apparent sizes are all there when you browse. But opening those older files reveals garbage or errors, because their contents were overwritten. And overwritten data is usually not recoverable — the original bytes are gone, replaced by whatever was written later. This is not a deletion that recovery software can undo; it is replacement.

Fakes are usually formatted FAT32, which helps the trick survive. NTFS places its directory around the 3 GB mark and keeps a backup sector at the end of the partition — structures that would quickly run into the non-existent space and expose the lie. FAT32 avoids putting those tripwires in the faked region as aggressively, so the drive can pass casual use and even a format without raising the alarm. A drive that refuses an NTFS format is showing you a clue, not a quirk.

Why it looks fine at first — the timeline of a fake

Put the pieces together and the typical experience makes sense. Day one: the drive arrives, reports its huge capacity, accepts your test copies, and plays your test video — because you have written almost nothing. First weeks: light use stays inside the real capacity, so the drive seems like the bargain of the year, and the buyer may even leave a positive review. Later: cumulative writes cross the real limit, wrap-around begins, and older files corrupt silently. Discovery usually comes when an important file — often the largest or oldest — will not open, long after the copying that destroyed it.

This timeline is why marketplace reviews are such weak protection: they are written in the honeymoon period, by buyers who have not yet filled the real chip. It is also why speed of testing matters more than sophistication. A quick screen on day one interrogates the far end of the claimed capacity immediately, instead of waiting for months of use to wander there.

Where these drives are sold

Fake 2TB drives and their even more absurd cousins — listings claiming far larger capacities, or huge external SSDs at impossible prices — appear across online marketplaces and discount platforms, and in some physical bargain retail as well. The listings share tells: flagship capacity at a tiny fraction of the genuine price, borrowed brand imagery, and sellers with no real connection to the brand named. Genuine 2TB-class drives, by contrast, are sold at full premium prices through the brands’ own stores and authorised retailers.

How to protect yourself: test, then claim

When any high-capacity bargain arrives, do not use it — test it. Back up is unnecessary on an empty drive; simply download FakeFlashTest via the download page, Run as Administrator (required, or no drives are listed), and run the Quick Size Test, which samples the entire claimed capacity including its fabricated far end. Screenshot the result log.

If it fails, you hold a documented counterfeit. Follow our evidence-based walkthrough, How to Get a Refund for a Fake USB Drive, to turn that log into a refund: dispute as counterfeit or falsified specifications, attach the test, and replace the drive through a genuine channel. If it passes the quick screen and came from a reputable seller, you can use it with reasonable confidence — and with backups, as you should for any drive, real or not.

The scam is elegant only while it is unexamined. A hacked controller, a tiny chip, and a confident lie about size — against a five-minute test that writes to the far end of the claim and reads back the truth.

That habit is simple: whatever you buy, test it on arrival with FakeFlashTest, following our guide on how to test a USB flash drive for fake capacity, using the tool from the download page. Pre-purchase suspicion plus on-arrival testing is the complete defence; neither half is as strong alone.

Start with capacity reality

Genuine USB flash drives top out at about 2 TB, and a genuine drive at that top end is a premium product from a major brand, sold at a premium price through the brand’s own channels. That single fact disposes of a large share of fake listings on sight. Any listing offering capacities far beyond what genuine flash drives reach — enormous multi-terabyte sticks and external drives at pocket-money prices — is not a bargain technology you have not heard of. It is a small chip in a case, with hacked firmware reporting a fantasy number.

Learn the shape of the genuine market for the capacity you actually need. If the largest drives from the brands themselves are expensive flagship products, a no-name listing claiming the same or greater capacity for a small fraction of what the real thing costs is not undercutting the market; it is selling a different, much smaller product with a lying label. Fakes are usually built around tiny real capacities — chips of a few gigabytes dressed up as hundreds — because that is where the margin is.

Do the price maths, relatively

You do not need to memorise any price list, and prices move too much for that to work anyway. Compare relatively, within the same marketplace, on the same day. Find what the recognised brands charge for the capacity you want, in their official stores. Then look at the suspect listing. A modest discount is normal commerce. A price that is a tiny fraction of the genuine article — the kind of gap that makes you wonder how it could possibly be profitable — is the signature of a fake, because the seller’s costs are those of the small chip actually inside.

Be especially wary of combinations: very high claimed capacity, very low price, and urgency tactics (“almost gone”, heavy discount badges) together. Each alone can have an innocent explanation in rare cases; together, they describe the standard fake listing almost exactly. The scam depends on the buyer doing the exciting comparison — capacity versus price — and skipping the boring one: this seller versus the brand’s own store.

Marketplace and brand-impersonation red flags

Fakes are sold across the major marketplaces and discount platforms, often dressed to borrow trust. Watch for brand names used loosely: a famous logo in the photos but a seller name that is not the brand, packaging in the images that does not match the brand’s current retail packaging, and titles stuffed with several unrelated brand names at once. Watch also for listings with glowing generic reviews that never mention capacity testing, reviews that could have been written without opening the parcel, and a seller history full of unrelated products sold at implausible discounts.

Another classic pattern is the unbranded or oddly branded drive with a metal swivel casing sold purely on capacity. There is nothing wrong with unbranded small drives as disposable media — but an unbranded drive claiming flagship capacity at a bargain price is asking you to believe an unknown maker has beaten the entire industry. It has not.

Buy from the brand’s own store where you can

The simplest risk reduction is channel choice. Buy from the brand’s official store or an authorised retailer rather than a third-party listing that merely uses the brand’s name. For SanDisk, for example, you can go through the official store link /go/sandisk-store rather than gambling on an impersonating listing. Paying the genuine price through the genuine channel is cheaper, in the end, than a fake plus a dispute plus replacing it anyway.

For a fuller treatment of safe buying across platforms — what to check on Amazon and eBay specifically, how returns windows affect your testing deadline, and which seller signals matter most — read our companion guide on how to buy storage safely on Amazon and eBay. It extends this pre-purchase checklist into a complete buying routine.

Whatever you buy, test it on arrival

Even careful buyers get caught: the best fake listings imitate genuine ones closely, and counterfeits can infiltrate legitimate-looking stock. So the final rule admits no exceptions based on how trustworthy the listing looked. When the drive arrives, before you load it with anything, run FakeFlashTest — back up nothing (it is empty), run as administrator, Quick Size Test, screenshot the result. Five minutes, while the return window is wide open and the evidence is fresh.

If it fails, you are in the strongest possible position: a documented counterfeit, inside the returns period, with a test log to attach to the dispute. If it passes, you have bought with confidence rather than hope. Either way, the listing screenshots end at the download page and a quick test — the routine that makes fake drives a refundable annoyance instead of a data-loss disaster.

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.

FakeFlashTest is a freeware, Windows-only, portable tool by Steve Si, available from the official source via our download page. For the complete workflow for a new drive, see our main USB capacity testing guide. For the destructive alternative, see the Quick Size Test guide — understanding both modes helps you choose the right one.

How Test Empty Space works

Instead of writing marker blocks across the whole reported capacity, Test Empty Space writes test files into the drive’s free space, filling that space progressively, and reads the files back to verify them. Crucially, it does not wait until the space is completely full before checking: it reads back and verifies at intervals as it goes — the developer’s implementation checks at points such as 3, 5, 9, and 17 GB. On a fake drive, that means corruption can be detected early, as soon as cumulative writes pass the real capacity, rather than only at the very end.

The design goal is preservation. Test files occupy space Windows reports as free, so files already stored on the drive are not deliberately overwritten. When the test finishes, the test files are removed and the drive’s contents should be as they were. That word — designed — matters, and the next section explains why a backup is still required.

Why you must still back up first

Test Empty Space is designed to preserve existing files, but always back up first. The reason is specific, not generic caution: if a file you already have sits in a bad area of the drive — for example, beyond the real capacity of a fake, where data has already wrapped around — that file can already be damaged, or can be further corrupted as the controller handles writes around it. The test cannot protect data that the drive’s own hacked firmware is mishandling.

So copy everything important off the drive, confirm the copies open, and only then test with the files still in place if you need to. If the backup succeeds and is verified, you also gain a better option: testing an emptied drive with the Quick Size Test, which samples the entire reported capacity rather than only the free remainder. Many careful users do exactly that — back up, empty, quick-test — and use Test Empty Space only when emptying genuinely is not possible.

The central limit: it only tests free space

Everything Test Empty Space can learn is confined to the space that is free at the moment you run it. If a drive is nearly full, there is almost no free space to fill, and the test can tell you almost nothing. A pass on a drive with very little free space is weak evidence — the unchecked, occupied portion could still hide the wrap-around point.

The practical fix is to free space deliberately before testing: move files to your computer (which you are doing for the backup anyway), empty the drive as far as you reasonably can, and then run the test so it has a large area to exercise. The more free space it can fill and read back, the more meaningful the verdict. If freeing space is impossible and the free remainder is tiny, treat any result as provisional and plan a full test on an emptied drive later.

There is a second limit shared with the Quick test. The developer is clear that FakeFlashTest is a quick screen: it does not thoroughly test all memory and does not check for every fault. Test Empty Space verifies the free space it writes, at the time it writes it. It is an excellent fake-capacity screen for a drive in use; it is not a complete certification of every cell on the device.

How to run it

Download FakeFlashTest via the download page, extract the official ZIP using the password fake, and Run as Administrator — without administrator rights, the tool lists no USB drives. Connect the drive directly, confirm its letter, select it carefully, choose Test Empty Space, and let it run to completion without removing the drive or letting the PC sleep.

Read the result in full. A failure during the read-back at any interval means the free-space writes could not all be stored correctly — exactly the signature of a fake or a failing device. If you encounter errors during this mode, our troubleshooting guide on Test Empty Space errors explains what they mean for files already on the drive and how to get a cleaner verdict on an emptied drive.

When to choose Quick instead

Choose Test Empty Space when the drive is in use, files must stay in place for now, and there is a substantial amount of free space to test. Choose the Quick Size Test when the drive is new, empty, or fully backed up and can be emptied — it samples the entire reported capacity, including the far end where fakes lie most obviously, and it gives the cleaner verdict.

Either way, act on a failure the same way: stop trusting the drive, preserve the result log as evidence, and do not promote a failed device to backup or dash-cam duty. A non-destructive check that tells you the truth early is valuable precisely because it lets you act while you still have choices.

FakeFlashTest is a freeware, Windows-only, portable tool by Steve Si. Get it from the official source via our download page. The latest version, v1.1.5, is described by the developer as the latest Beta build. There is no install: you extract the password-protected ZIP (the extraction password is fake) and run the program.

What the Quick Size Test actually does

The test writes small marker blocks — 512 bytes each — at intervals spread across the drive, and then reads them back to check that each marker is still intact at the address where it was written. It starts from the end of the reported capacity and works through the drive, which is a deliberate choice: a fake drive lies most obviously at its far end, where the reported space does not exist at all.

On a genuine drive, every marker can be written and read back correctly, because every reported sector corresponds to real flash memory. On a fake drive, the controller reports far more capacity than the physical chip holds. Markers written beyond the real capacity either fail, overwrite earlier markers as the addresses wrap around, or read back corrupted. Any of those outcomes exposes the lie quickly, without filling the entire drive byte by byte.

That sampling is also the test’s limit, and the developer states it plainly: FakeFlashTest is a quick screen. It does not thoroughly test all of the memory and it does not check for faults everywhere. A drive can pass the Quick Size Test and still have a defective area between two sampled points. For a thorough verdict you need a full write-and-verify test such as H2testw, which can take hours. Think of the Quick test as a fast, usually decisive capacity check — not a complete health certificate.

Warning: this test is destructive

The Quick Size Test destroys the data on the selected drive. Writing marker blocks across the drive overwrites file system structures and file data, and afterwards the drive will normally need to be formatted before reuse. Never run it on a drive that holds the only copy of anything.

Back up first, verify the backup opens, and then double-check the drive letter inside FakeFlashTest against the letter in File Explorer. Selecting the wrong letter is the most damaging mistake a user can make with any destructive test, and it is entirely preventable with ten seconds of care. If you cannot empty the drive, do not use this mode — use the preserving alternative described in our Test Empty Space guide instead, and accept that it only tests free space.

How to run it, step by step

First, connect the drive directly to the computer, avoiding hubs where possible, and confirm Windows shows it with a drive letter. Second, right-click FakeFlashTest and Run as Administrator — without administrator rights the tool will not list USB drives at all. Third, select the correct drive in the tool, reading its letter and size twice. Fourth, choose Quick Size Test and start it, then leave the computer to work: do not remove the drive, let the PC sleep, or hammer the machine with other heavy disk activity while the test runs.

Finally, let the test reach its own conclusion and read the full log, not just the headline. Our guide on how to read FakeFlashTest results explains what passes, failures, and real-capacity figures mean, and why screenshotting the log matters if you need a refund.

How long should it take? Honest timing

The developer’s own example diagnosed a fake 16 GB drive in 27 seconds. That example is real, and it shows why the test is called Quick — but it is a single example on a small fake, never a guarantee for your drive. Timing depends on the reported capacity, the real speed of the device and reader, and how the controller behaves once writes pass its real limit.

A small genuine drive may finish quickly. A drive claiming a very large capacity, a slow card in a slow reader, or a fake whose controller struggles under sustained writes can take much longer — potentially far longer than a minute or two. Judge progress by whether the test is advancing, not by a stopwatch. If it appears completely frozen for a very long time, consult the troubleshooting advice for stuck tests rather than repeatedly unplugging the drive mid-write.

If the Quick test fails every drive you try

There is one result that should make you suspect your computer rather than your drives: the Quick Size Test failing every drive, including one you know is genuine. The developer addresses this directly — security software or a driver interfering with the tool’s low-level access is the usual cause, and the advised fix is to run FakeFlashTest in Windows Safe Mode, where that interfering software is not loaded.

That scenario has its own dedicated guide: Quick Size Test Fails Every Drive? The Safe Mode Fix. Follow it before concluding that several unrelated drives all happen to be fake. Testing a known-good drive alongside a suspect drive, on the same PC and setup, is the simplest sanity check in this whole subject.

Used as intended — empty or backed-up drive, administrator rights, correct letter, patience, and a careful reading of the log — the Quick Size Test is the fastest honest answer to the only question that matters on day one: is this drive’s capacity real? Download the tool from the download page, run it on arrival, and you will know before your files are at risk.

FakeFlashTest is Windows-only and portable, with no install. You run it on a Windows PC even if the card will spend its life in a phone or camera. Get it via our download page, which links to the official download from the developer. If you have never tested storage before, the general workflow in our USB flash drive testing guide is worth reading first — the principles are identical, and this guide focuses on what is specific to cards and readers.

Use a proper card reader — this step decides the test

FakeFlashTest tests what Windows can see, so the card must appear in Windows as a drive with a letter. The reliable way to do that is a good USB card reader plugged directly into the computer. A reader that constantly disconnects, runs extremely slowly, or only works intermittently will produce confusing results and painfully long tests.

If you need a reader, a USB 3.0 UGREEN reader via /go/ugreen-card-reader is genuinely useful kit for this job — not an accessory for its own sake, but the piece that makes the test trustworthy. Plug the reader directly into the PC, preferably a rear port on a desktop or a main port on a laptop. Avoid USB hubs for testing: hubs add another device that can drop the connection, share power, or slow the transfer, and they make troubleshooting harder. Avoid the built-in slow card slot on some laptops for the same reason if a proper reader is available.

Insert the microSD card (in its full-size adapter if your reader needs one), confirm Windows assigns it a drive letter, and note that letter carefully. If no letter appears, open Disk Management and assign one to the card’s volume — without a letter, no testing tool can address it.

Back up, then run as administrator

If the card already holds photos or recordings, copy them off and verify the copies open before you test. One FakeFlashTest mode is destructive, and even the preserving mode cannot protect a file that already sits in a bad area of a fake card.

Extract the official ZIP — the extraction password is fake, set by the developer to reduce false blocks by Windows Defender — then right-click the program and Run as Administrator. The developer is clear: without administrator rights, FakeFlashTest will not list USB drives, and a card in a reader counts for this purpose. An empty list almost always means you skipped this step. Our dedicated guide to that symptom is linked from the troubleshooting section if you need it.

Choose between Quick Size Test and Test Empty Space

For a new, empty card — the most common case — run the Quick Size Test first. It writes and reads back 512-byte marker blocks at intervals across the card, starting from the end, so it can expose an inflated capacity without filling every byte. It is destructive: anything on the card will be lost, which is fine for a new card and exactly why you backed up an older one. The method is explained fully in our Quick Size Test guide.

If the card already holds files you must keep in place, use Test Empty Space instead. That mode writes test files only into the free space and reads them back at intervals, and it is designed to preserve existing files. Understand its limit, detailed in our Test Empty Space guide: it can only test the space that is currently free. A card that is nearly full leaves it almost nothing to check, so for a trustworthy verdict on a used card, move the files off, back them up, and run the Quick test on the empty card instead.

Dash cams, phones, and why fakes fail there first

Dash cams are where fake cards cause the most painful losses. A dash cam records continuously and overwrites its oldest footage as the card fills. On a fake card, the wrap-around point arrives far earlier than the driver expects: the card reports plenty of space, the camera keeps recording, and older — or even recent — clips are silently corrupted. The failure is usually discovered after an incident, when the one clip that mattered will not play.

Phones hide the problem differently. A phone will let you save photos and apps to a fake card for weeks, because light use stays within the small real capacity. The corruption starts once total writes pass that real limit. Testing on arrival, before the card goes into any device, avoids both scenarios. A card that fails should never be promoted to dash-cam duty on the theory that it seemed to work in the shop.

Reading the result for a card

A pass on the Quick Size Test means the sampled points across the reported capacity responded correctly — a good sign, and for most buyers enough to proceed, ideally followed by formatting the card in the device that will use it. The developer is honest that FakeFlashTest is a quick screen, not a thorough test of all memory or a check for every fault, so a pass is not a guarantee against a card failing later for other reasons.

A fail tells you the reported capacity is false and usually indicates the approximate real capacity. Screenshot the result log straight away. That screenshot is your evidence for a refund claim, and it is far more persuasive than saying the card felt faulty. Stop using the card, do not entrust it with recordings, and replace it with a genuine card from a reputable seller. If you bought a card that failed, the same evidence routine described for USB drives applies — test, document, dispute, replace.

In short: reader first, direct connection, back up, run as administrator via the tool from the download page, test while the card is empty if you can, and act on the result immediately. A microSD card costs little to test and a great deal to trust blindly.

Start from the right place: get the tool only via our download page, which links to the official password-protected ZIP from rmprepusb.com. Do not download copies from random file-hosting sites. You will also want this guide open alongside the tool, because the most common mistakes happen before the test even starts — choosing the wrong drive letter, or testing a drive that still holds the only copy of important files.

Why fake capacity matters

A fake drive is not just a slow or faulty drive. Its controller firmware has been hacked — often described as clocked — so that a small flash chip, for example 8 GB or 16 GB of real storage, reports itself to Windows as 512 GB, 1 TB, 2 TB, or even more. Everything looks normal at first. You can copy files, see folders, and check properties, and Windows will happily show the inflated size.

The problem appears when you write past the real capacity. At that point the drive wraps around and silently overwrites data you saved earlier. The folder listing can still look normal while the files inside are corrupt. Overwritten data is usually not recoverable. That is why testing on arrival, while you can still return the drive, matters far more than testing months later after you have filled it.

Step 1: Back up anything on the drive first

Before any test, copy anything you care about off the drive to your computer or another storage device, and check that the copies open. This is not optional caution. One of FakeFlashTest’s two modes is destructive by design, and even the gentler mode can expose corruption in files that happen to sit in bad areas of a fake drive.

If the drive is brand new and empty, this step is quick. If you have already used it, treat the backup as your safety net. A test result is useful; a test that costs you your only copy of a file is not. Back up first, every time.

Step 2: Download and extract FakeFlashTest correctly

Go to the download page and follow the official link. The official download for the latest version, v1.1.5 — described by the developer as the latest Beta build — is a password-protected ZIP. The extraction password is fake. The password is not a trick: it was set to reduce false blocks by Windows Defender, which can be suspicious of low-level storage tools.

Extract the ZIP to a folder on your computer, not onto the drive you are about to test. Keep the extracted program somewhere easy to find, such as your Downloads folder or Desktop. Because FakeFlashTest is portable, there is nothing to install and nothing to uninstall afterwards. If Windows asks questions about an unfamiliar program, pause and check that you really did download it from the developer’s site via the link above — source matters more than dismissing warnings.

Step 3: Run as administrator and pick the right drive

Right-click the FakeFlashTest program and choose Run as Administrator. This step is required: the developer states clearly that the tool must run as administrator or no USB drives will be listed. If the drive list is empty, running without administrator rights is the first thing to check, before you assume anything is broken.

Now choose the drive letter with great care. Check the letter in File Explorer and in Disk Management if you are unsure, and match the size and label to the drive you inserted. The Quick Size Test destroys data on the selected drive, so selecting your system drive or a backup drive by mistake would be a serious error. Take ten seconds here. Remove other USB storage you do not need for the test if that helps you identify the target with confidence.

Step 4: Run the Quick Size Test first

For an empty or backed-up drive, start with the Quick Size Test. As explained in detail in our Quick Size Test guide, this mode writes and reads back 512-byte marker blocks at intervals across the drive, starting from the end. Because it samples across the whole reported capacity instead of filling every byte, it is designed to be fast.

The developer’s own example diagnosed a fake 16 GB drive in 27 seconds. That is a single example, not a promise. A large or slow drive can take much longer, and you should let the test finish rather than judging it in the first minute. Remember what this test is and is not: the developer is explicit that FakeFlashTest is a quick screen. It does not thoroughly test all memory and does not check for every fault. A pass is reassuring, not a lifetime guarantee.

Step 5: Consider Test Empty Space or a full test

If the drive holds files you cannot move, the alternative is Test Empty Space, covered in our Test Empty Space guide. It writes test files only into the free space and reads them back, checking at intervals, and it is designed to preserve existing files. It still only tests the free space, so a nearly full drive gives it very little to work with.

For the most thorough check, a full write-and-verify tool such as H2testw remains the reference. It fills the entire drive and verifies every byte, which is more complete than any sampling test but can take hours. Many people use FakeFlashTest first as a fast screen, then run a full test overnight if the drive passes and they plan to trust it with important data. That two-stage approach is sensible and honest about each tool’s limits.

Step 6: Read the result and decide what to do next

When the test finishes, read the log carefully rather than looking only for the word pass or fail. Our guide on how to read FakeFlashTest results walks through what a pass means, what a failure tells you about real capacity, and why you should screenshot the log. If the drive fails, the log becomes your evidence.

If it is confirmed fake, follow the steps in Fake Drive Confirmed: What to Do Next: stop writing to it, salvage what still opens, pursue a refund, and replace it with a genuine drive from a reputable seller. If it passes the quick screen, format it, use it normally, and still keep backups elsewhere. No single test — quick or full — replaces keeping copies of files you cannot afford to lose.

That is the whole routine: back up, download from the official source, run as administrator, choose the letter carefully, test, and act on the result while returns are still possible. Five careful minutes on arrival can save you from discovering a fake the hard way, months later, when the files it overwrote are the ones you needed most.