You open FakeFlashTest, ready to test a suspect drive, and the list is empty. The empty list is almost never a broken drive — and it is almost never a broken tool. In the great majority of cases it is one specific, developer-documented requirement that was skipped, plus a handful of ordinary Windows visibility issues behind it. Work through these five fixes in order and you will almost certainly be testing within minutes.
Make sure you are using the genuine tool from the official source via our download page (extraction password fake for the official ZIP). If the drive eventually appears and tests fine, our guide on how to test a USB flash drive for fake capacity covers the full testing routine to follow next.
Fix 1: Run as Administrator — the developer’s own requirement
This is the fix, most of the time. FakeFlashTest’s developer states it plainly: the program must be Run as Administrator, or it will not list USB drives. The tool needs low-level access to removable storage that Windows does not grant to a standard launch, and without that access its drive list stays empty even though the drive is sitting right there in File Explorer.
Close the program completely, right-click its icon, and choose Run as Administrator, accepting the Windows prompt. Reopen the list and your drive should appear. If you plan to test regularly, this is the habit to build: administrator launch first, troubleshooting second. Do not reinstall, re-download, or suspect the drive until this step has been done — it is remarkable how many “the tool doesn’t work” reports end exactly here.
Fix 2: Make sure Windows gives the drive a letter
FakeFlashTest addresses drives by the drive letter Windows assigns, so a device that Windows itself has not mounted with a letter cannot appear. Open Disk Management (right-click the Start button and choose it) and find the drive or card there. If the volume is present but has no letter, right-click it, choose Change Drive Letter and Paths, and assign an unused letter.
Watch out for letter collisions: a card reader presenting several slots, or a network drive already holding the letter the USB device would naturally take, can leave the device letterless. Assigning a fresh letter manually resolves it. Once Windows Explorer shows the drive with its new letter, relaunch FakeFlashTest as administrator and check again.
Fix 3: Deal with unallocated or unformatted space
A brand-new, wiped, or damaged drive may appear in Disk Management as unallocated space with no volume at all — and therefore no letter for any tool to list. If the drive is empty or fully backed up, create a simple volume in Disk Management and format it (FAT32 is what fakes typically arrive as; the format you choose for a test on an empty drive is not important to the verdict). Then relaunch the tool as administrator.
If the drive holds data you need, do not create volumes or format over it to make it visible — that path sacrifices the data for the listing. In that case, work through the other fixes first, and check the device on another computer if you have one. Visibility problems caused by a damaged file system on a data-bearing drive deserve salvage thinking first, testing second.
Fix 4: Try another port — and respect the reader caveat
USB ports and connections are a mundane but real cause. Move the drive to a different port, preferably directly on the computer — a rear port on a desktop — and avoid testing through a USB hub, which can underpower devices or drop connections in ways that make tools see nothing. Relaunch as administrator after reconnecting, so the tool enumerates devices fresh.
For microSD and SD cards there is an extra link in the chain: the card reader. A faulty, loose, or extremely cheap reader can fail to present the card to Windows at all, and some multi-slot readers behave oddly with certain cards. If a card does not show up, try the card in a different known-good reader (or the same reader on another port) before concluding anything about the card. Our card-specific guidance in how to test a microSD card for fake capacity covers reader choice in more detail, because for cards the reader is part of the test rig.
Fix 5: Confirm Windows itself can see the device
Step back and check the basics in order: does the drive appear in File Explorer? In Disk Management, even without a letter? In Device Manager under disk drives? Each “yes” narrows the problem: visible in Windows but not in FakeFlashTest points back at the administrator launch; visible in Disk Management but not Explorer points at the letter; invisible everywhere points at hardware — port, reader, cable, or a genuinely dead device.
One more ordinary check is worth ten seconds before you move on: remove and reinsert the drive firmly, and if it is a card, reseat it in its adapter and reader as well. A shallow insertion or a tired adapter contact can leave a perfectly healthy card electrically half-connected — visible to nothing, not because the card failed, but because the connection never fully happened. Reseating costs nothing and resolves a surprising share of these cases.
A drive that no computer can see at all may be a fake that has already failed, which is its own scenario with its own next steps. And if the tool lists drives but tests misbehave on all of them, that is a different symptom again, pointing at software interference rather than visibility. Get the drive listed first, run the test from the download page version of the tool, and let one fix at a time prove itself — starting, almost always, with Run as Administrator.