When a capacity test gives a strange result — very slow, disconnecting halfway, different every time you run it — the card is not always to blame. The reader between the card and the computer is part of the test, and a poor reader can make a good card look faulty or a test take so long you give up before it finishes. This guide explains what a reader does to test validity and speed, why we advise against built-in slots and hubs for big tests, and what a reliable testing setup actually looks like. It is simpler, and cheaper in time, than most people expect.
Some links on this page are affiliate links — if you buy through them we may earn a commission at no extra cost to you. See our affiliate disclosure.
Why the Reader Is Part of the Test
FakeFlashTest and similar tools write test data to the card and read it back to check it survived. That conversation passes entirely through your card reader. If the reader drops the connection mid-test, runs at a fraction of the card’s speed, or handles large capacities unreliably, the results reflect the reader as much as the card. Developer communities around fake-flash testing give the same advice for the same reason: test big cards through a dedicated reader connected directly to the computer, so the only thing being measured is the card itself.
This matters in both directions. A flaky setup can make you return a genuine card — annoying but recoverable. Worse, a test abandoned because it crawled for hours through a slow slot means a fake card never gets caught, and goes into a camera or phone to lose real data later. A good reader is what makes testing a routine instead of an ordeal.
The Problem With Built-In Slots and Cheap Hubs
Many laptops have a built-in SD slot, and it feels like the obvious place to test a card. In practice those slots vary enormously: some are connected internally at slow speeds, some struggle with larger cards, and microSD adapters add another loose contact into the chain. You may still get a valid result — eventually — but a full test of a large card can stretch out far beyond what the card itself requires.
Hubs add a second problem. A cheap unpowered hub shares power and bandwidth between everything plugged into it, and a card under sustained writing is exactly the load that exposes that. Disconnections during a test, especially the same test passing when run directly, are a classic hub symptom. For testing, remove variables: one reader, one cable if it needs one, straight into a USB port on the computer itself.
What to Buy: A Dedicated USB 3.0 Reader
The reliable setup is a dedicated USB 3.0 SD and microSD reader from a recognised accessories brand, with its own slot for microSD so you are not relying on a loose adapter. USB 3.0 matters because the reader needs to be comfortably faster than the card’s writing, so the card — not the reader — is the limit the test measures. A reader that handles both full-size SD and microSD covers dash-cam cards, camera cards and the adapters in between.
UGREEN makes popular USB 3.0 card readers in exactly this class, and it is the brand we link for this job: UGREEN card reader at the brand store. We are recommending the type and the direct brand route, not a benchmark winner — there are no test figures in this article because reader choice is about stability and a clean connection, not headline numbers. Buy it from the brand store or a platform-sold listing, following the same seller logic as for the cards themselves in buying storage safely on Amazon and eBay.
Setting Up a Test You Can Trust
- Plug the reader directly into the computer — no hub, no dock, no front-panel extension if you can avoid it.
- Insert the microSD card in the reader’s own microSD slot rather than via a full-size adapter where the reader offers one.
- Back up anything on the card first. Testing writes across free space or, for the quick test, across the drive in a destructive check — follow the guide for the mode you use.
- Close other heavy transfers and let the test finish. Interrupting a test tells you nothing.
- If a result looks odd, change one thing — reseat the card, use a different USB port — and re-run before concluding the card is at fault.
The full testing steps themselves live in how to test a microSD card for fake capacity and, for USB drives, how to test a USB flash drive for fake capacity. Get the tool itself from our download page and run it as administrator so the device is listed correctly.
Reader, Card or Computer? Reading the Symptoms
| Symptom | More likely cause | What to try |
|---|---|---|
| Test disconnects partway, card vanishes | Reader, hub or cable | Direct port, reseat card, different reader |
| Test is extremely slow for the card size | Slow slot or USB 2.0 path | USB 3.0 reader in a USB 3.x port |
| Real capacity far below claimed, consistently | The card itself | Re-run to confirm, then treat as fake and see the refund guide |
| Different result every run, no pattern | Connection stability | Remove adapters and hubs, then re-test |
Consistency is the tell. A fake card fails in the same place, at the same real capacity, run after run and reader after reader. A reader problem moves around. If you have confirmed a fake, our refund guide shows how to use the log, and our microSD buying guide covers choosing a genuine replacement — endurance lines for cameras, mainstream lines for general use. If you are also replacing USB drives, start with best genuine USB flash drives.
One Reader, Kept With Your Testing Routine
You do not need a drawer of adapters. You need one decent USB 3.0 reader that lives with the computer you test on, so that testing a new card takes minutes to set up and the result means something. Pair it with the habit from the rest of this site — every new card and drive tested on arrival, packaging kept until it passes — and the reader pays for itself the first time it catches a fake that a slow laptop slot would have let you give up on. Reliable tests need reliable plumbing. This is the plumbing.