Fix USB Drive Showing Wrong Capacity / Size (3 Easy Ways)

You plugged in a 64GB flash drive, and Windows tells you it's 4MB. Or maybe it's showing 32MB instead of the 128GB you paid for. You've tried a different USB port, a different laptop, maybe even prayed a little. Nothing changes.

I've lost count of how many times a user brought me a drive like this, convinced it was "broken" and ready to toss it in a drawer forever. Most of the time, the drive is fine. What's broken is the partition table, and that's a very different problem with a very fixable solution.

This guide walks through exactly why this happens and gives you three separate methods to get your full capacity back, starting with the easiest and working up to the nuclear option.

The Quick Answer

Nine times out of ten, this happens because a chunk of your drive got turned into a hidden or unallocated partition — usually by a tool like Rufus, BalenaEtcher, or Ventoy when you created a bootable USB for Windows, Linux, or a Raspberry Pi image. The rest of your storage didn't vanish. It's just sitting there, unformatted and invisible to Windows Explorer.

The fix, in almost every case, is to delete all the partitions on the drive and create one clean new one. I'll show you how below, with three different methods depending on your comfort level with computers.

Why This Actually Happens

1. Bootable Drive Tools Left Behind Leftover Partitions

This is, by far, the number one cause I see in the field. When you use Rufus, BalenaEtcher, or Ventoy to flash an ISO onto a USB drive — say, to install Ubuntu, boot a Raspberry Pi imager, or run a Windows installation media — these tools restructure the drive's partition table to make it bootable.

That process often creates a small FAT32 or ISO9660 boot partition and leaves the remaining space either unallocated or hidden. Windows only shows you the first partition it recognizes in Explorer. So your 64GB drive suddenly "shows" as 4MB or 32MB because that's literally all the space Windows can see in the visible partition — the rest is sitting there unallocated, invisible until you go looking for it in Disk Management.

Ventoy is especially notorious for this because it deliberately creates a large hidden partition to store your ISO files, plus a small visible one. If you've ever used Ventoy and then tried to go back to using the drive normally, this is almost certainly what happened.

2. Corrupted or Damaged File System

Sometimes the file system itself gets corrupted — from unsafely ejecting the drive mid-write, a bad sector, or a power failure while data was being copied. Windows sees a drive it can't properly read and defaults to reporting whatever fragment of allocated space it can identify, which is often a tiny sliver of the real capacity.

3. Leftover Recovery or OEM Partitions

Some drives, especially ones repurposed from OS recovery media or manufacturer tools, ship with a small hidden recovery partition baked in. If that partition never got cleaned up, it can eat into what Windows displays as "available" space.

4. Fake Capacity Drives (Counterfeits)

This one deserves its own callout because it's more common than people think, especially with drives bought from third-party marketplace sellers at suspiciously low prices.

Heads up: Counterfeit flash drives are programmed to report a capacity — say, 512GB — while the actual physical memory chip inside might only be 8GB or 16GB. The drive's firmware lies to your operating system. Once you write more data than the real chip can hold, it either overwrites your existing files or corrupts everything on the drive.

Here's how to check if that's what you're dealing with:

• Use H2testw (Windows) or F3 (Linux/Mac): These tools write test data across the entire reported capacity and then read it back to verify it's actually there. If a "128GB" drive fails at 8GB, you've got a fake.
• Check the write speed: A drive that reports a huge capacity but writes at USB 1.1 speeds (under 1MB/s) is almost always fake or damaged.
• Buy from reputable sellers only, going forward: If a 1TB flash drive costs $12, it isn't a 1TB flash drive.

If your drive fails an H2testw or F3 test, no partition fix in the world will help — the hardware itself is misrepresenting its size, and no amount of formatting recovers storage that was never physically there.

Assuming your drive passes that test (most do), let's get into the actual fixes.

Before You Start: A Word of Caution

Every method below involves deleting data. Not "maybe deleting" — deleting. If there are files on that drive you need, back them up first if you can access them at all. If you can't access them because the drive is showing as corrupted or RAW, that's a separate data recovery situation, and formatting will make recovery harder, not easier.

Also — and this really matters — double, triple check you've selected the correct disk before running any destructive command. Diskpart in particular does not ask "are you sure" twice. It does what you tell it, instantly, even if what you told it was your main hard drive.

Method 1: Windows Disk Management (GUI, Easiest)

This is where I start with 90% of cases because it's visual, low-risk, and doesn't require memorizing commands.

Step 1: Right-click the Start button and select Disk Management (or press Windows + R, type diskmgmt.msc, and hit Enter).

Step 2: Find your USB drive in the list at the bottom. It'll usually be labeled by its size and show as "Disk 1," "Disk 2," etc. Look for the drive letter and total size to confirm you've got the right one — this step is not optional.

Step 3: You'll likely see multiple partitions on the drive — maybe a small one labeled with a drive letter, and a large block marked Unallocated. This unallocated space is your missing capacity, hiding in plain sight.

Step 4: Right-click on each existing partition on that drive and select Delete Volume (or Delete Partition). Do this for every partition on the drive, including any small hidden ones.

Step 5: Once the entire drive shows as one solid block of Unallocated space, right-click it and choose New Simple Volume.

Step 6: Follow the wizard — assign a drive letter, choose NTFS or exFAT as the file system (exFAT if you'll use it across Windows, Mac, and Linux), and select Perform a quick format.

Step 7: Click Finish. Your drive should now show its full, correct capacity in File Explorer.

Warning: If Disk Management shows your drive as "RAW" instead of a recognizable file system, don't panic — that's still fixable, but skip straight to Method 2 below since the GUI format option sometimes fails on RAW disks.

Method 2: Diskpart (Command Line, More Reliable)

When Disk Management refuses to cooperate — which happens more often than I'd like, especially with drives that Ventoy or Rufus have really mangled — Diskpart is the tool that gets it done. It's more powerful, which also means it's less forgiving.

Safety Warning: Diskpart operates on whole physical disks, not folders or files. Selecting the wrong disk number will silently wipe your Windows installation, your backup drive, or anything else connected. Read every step twice before hitting Enter.

Step 1: Press Windows + R, type cmd, and press Ctrl + Shift + Enter to open Command Prompt as Administrator.

Step 2: Type the following and press Enter to launch Diskpart:

diskpart

Step 3: List all disks connected to your system:

list disk

Step 4: Identify your USB drive by its size in the list. This is the critical step — match the size shown (even if it's the wrong/reduced size) to the drive you're trying to fix. Note the disk number, for example Disk 2.

Step 5: Select that disk (Replace 2 with your actual disk number):

select disk 2

Step 6: Confirm one more time you've selected the right disk:

detail disk

This shows drive details so you can verify it's the USB drive and not your system drive.

Step 7: Wipe the drive clean, removing all partition and volume data:

clean

Step 8: Create a new primary partition on the now-empty disk:

create partition primary

Step 9: Select the new partition and format it (Swap exfat for ntfs if you need NTFS instead):

select partition 1
format fs=exfat quick

Step 10: Assign a drive letter so Windows recognizes it in File Explorer:

assign

Step 11: Exit Diskpart:

exit

Your drive should now show up in File Explorer at its full, correct capacity. This method fixes the vast majority of Ventoy, Rufus, and BalenaEtcher leftover-partition cases that Disk Management can't touch.

Method 3: Third-Party Tools (When Windows Won't Cooperate)

Occasionally you'll hit a drive where Diskpart throws an error like "The parameter is incorrect" or refuses to clean the disk. This tends to happen with SD cards used in Raspberry Pi projects, or drives with unusual partition structures Windows doesn't fully understand.

SD Card Formatter (from the SD Association) is my go-to here, and it works for USB flash drives too, despite the name. It's built specifically to handle drives with hidden partitions and non-standard formatting left behind by imaging tools.

• Download it from the official SD Association website.
• Select your drive from the dropdown (again — verify the size matches before proceeding).
• Choose Overwrite Format rather than Quick Format if the drive was previously used with Raspberry Pi OS, Ventoy, or a Linux distro. This does a full pass and clears out partition remnants Quick Format can miss.
• Click Format.

If SD Card Formatter still can't restore full capacity, the drive may genuinely be a counterfeit or have failing memory cells — go back to the H2testw/F3 test mentioned earlier to confirm.

FAQ

Will formatting delete my files?
Yes. Any method here — Disk Management, Diskpart, or third-party formatters — erases everything on the drive. If you need the existing data, recover it first using a data recovery tool before formatting, or copy off anything you can still access.

What if Diskpart gives me an error like "Virtual Disk Service error" or "Access is denied"?
This usually means write protection is enabled on the drive, or another process has it locked. Try attributes disk clear readonly right after selecting the disk in Diskpart, then run clean again. If that fails, physical write-protect switches exist on some SD cards and adapters — check for one.

Why does this keep happening every time I use Rufus or Ventoy?
Because that's literally what these tools do by design — they restructure your drive's partitions to make it bootable. If you regularly switch a drive between "bootable installer" and "normal storage," expect to run one of the fixes above every time you switch it back.

Can I avoid this happening in the future?
Not entirely, if you're using imaging tools regularly — it's just part of the tradeoff. What you can do is keep a dedicated drive for bootable images and a separate one for regular storage, so you're not constantly reformatting the same drive back and forth.

My drive shows as "RAW" — is that different from unallocated?
Yes. RAW means Windows sees a partition but can't identify its file system, usually due to corruption. It still responds well to Diskpart's clean and reformat process, so Method 2 above applies directly.

Is there a risk of this happening again on the same drive?
Not from normal use. Once you've cleaned and reformatted the drive with a single healthy partition, it'll behave like any standard USB drive unless you run it through a bootable-image tool again.