External Drive Shows the Wrong Capacity in Windows
Short answer
Open Disk Management by pressing Win+X and picking it from the menu. If the drive shows unallocated space alongside a small partition, the capacity is there and only part of it is formatted. If Disk Management also reports the small size, the drive is either genuinely that size, has a stuck host protected area, or is a counterfeit reporting a false capacity to the operating system.
On this page
Before anything else, check whether the shortfall is actually a problem. A 1TB drive showing 931GB and a 2TB drive showing 1.81TB are both correct, and no amount of troubleshooting will change either number.
Manufacturers count a gigabyte as a billion bytes. Windows counts it as 1,073,741,824. The gap is about 7%, it grows with capacity, and both figures describe the same physical storage.
The real problems look different, and they start at a factor of two or more.
Work out which situation you have
| What you see | Cause |
|---|---|
| 1TB showing 931GB, 2TB showing 1.81TB | Unit conversion. Normal. |
| Drive reports roughly half or a third | Partitions, or a mismatched interface |
| 2TB reports 32GB or 8GB | Lost partition table, HPA, or a fake |
| Drive is full far earlier than it should be | Counterfeit capacity |
The tool that answers all of these is Disk Management, and it shows things File Explorer deliberately hides.
Look at Disk Management
Press Win+X and choose Disk Management, or press Win+R and run
diskmgmt.msc.
Find your external drive in the lower pane. The row shows its total capacity on the left and its partition layout as blocks to the right. Three possibilities:
Unallocated space alongside a partition. The capacity is physically there and only part of it is formatted. This is common on a drive that previously held an operating system or was partitioned on another device.
To use it: right-click the unallocated block → New Simple Volume, and accept the defaults. That adds a second drive letter. To merge it into the existing partition instead, right-click the existing partition → Extend Volume, which only works when the unallocated space sits immediately to its right.
Several partitions including small ones. A drive pulled from a laptop carries EFI, recovery and reserved partitions. They are hidden from Explorer and still counted. Removing them means deleting every partition and creating one new volume, which erases everything on the drive.
Disk Management reports the small size too. The hardware itself is telling Windows it is that size. That is the serious case, covered below.
When the hardware reports a false size
If Disk Management agrees with Explorer that your 2TB drive is 32GB, the reported capacity is coming from the drive’s controller. Three causes.
A damaged partition table
The GPT or MBR structure holding the layout can be corrupted by an unsafe removal during a write, or by a tool that wrote a partition table incorrectly.
The destructive fix is the diskpart clean operation, which removes all
partition information and lets Windows rebuild it. This erases the entire
drive. Recover any files you still need first — connecting the drive to
another machine, or running recovery software such as TestDisk or PhotoRec, are
the usual routes.
In Terminal (Admin):
diskpart
list disk
Identify the correct disk number by its size, carefully. Selecting the wrong one and cleaning it will destroy your system drive, and there is no undo. If two disks show the same size, disconnect everything else first.
select disk N
clean
create partition primary
format fs=ntfs quick
assign
exit
Replace N with the number you verified. The drive should then report its real
capacity.
A host protected area
Some drives carry a firmware-level hidden region, originally used by manufacturers for recovery images. A drive with one set reports a reduced capacity to the operating system, and Windows has no way to see past it because the hardware never mentions it.
diskpart cannot remove it. The manufacturer’s own utility sometimes can, and
on desktop machines a BIOS setting occasionally exposes the option. This is
uncommon on a modern external drive and more likely on a reused internal drive
in an enclosure.
A counterfeit drive
This is the most common cause of a wildly wrong capacity on a cheaply bought USB stick or memory card, and it is worth taking seriously because the failure mode is designed to be invisible.
The controller is reprogrammed to report a large capacity the flash cannot hold. Writing appears to succeed until the real capacity is passed, after which data is silently discarded or wraps around and overwrites earlier files. The file listing looks fine. The files are gone.
Test with H2testw or F3, both free. They fill the drive with verifiable patterns and read them back. A counterfeit fails verification at the point where the real capacity ends, usually well before the reported figure.
If it fails, the usable capacity is the real one, and the drive cannot be repaired into the capacity it claimed. Return it. Do not keep using it for anything you care about, because the next large copy will silently destroy what is already on it.
The in-between cases
A drive that fills up faster than expected without reporting the wrong total
is a different issue. On an external drive, check for a hidden System Volume Information folder holding restore point data, and for a Recycle Bin on that
drive that has never been emptied. Both are counted.
A drive formatted FAT32 cannot hold a file larger than 4GB and is limited to 32GB per volume when formatted by Windows’ own tools, which produces an apparently small drive on a larger device. Reformat to NTFS for Windows-only use, or exFAT for sharing with macOS. Both support large files and large volumes.
A USB 2.0 port or cable does not change reported capacity, but it does make a modern drive feel broken. If the drive is slow rather than small, that is the first thing to check.
Before you erase anything
Every destructive step above assumes the data is expendable. If it is not:
- Try the drive on another computer first. A controller or driver problem on one machine presents exactly like a drive fault.
- Try a different cable and port. Marginal power delivery on an unpowered hub causes drives to enumerate incorrectly, which can include reporting the wrong size.
- Check Device Manager for the drive under Disk drives. A drive appearing with a warning triangle has a driver or enumeration problem rather than a capacity one.
- Run recovery software before
diskpart clean, not after. Once the partition table is rewritten, recovery becomes considerably harder.
If the drive is making clicking or grinding noises, stop. Every further attempt to read a mechanically failing drive reduces what a professional recovery service can retrieve, and software will not help.
What does not help
- Formatting the visible partition to recover unallocated space. Formatting changes the file system inside a partition; it does not change the partition’s size.
- “Capacity restore” utilities found on download sites. Most either run
diskpart cleanbehind a friendlier interface or reprogram the controller in ways that make a counterfeit worse. - Buying a bigger enclosure. The enclosure is not the limit.
- Expecting a counterfeit to be fixable. The flash is the size it is. Tools that “fix” one simply set the reported capacity to the real figure, which is a reasonable outcome and not a recovery.
Realistic expectations
Most of these questions end at the unit conversion, and the answer is that nothing is wrong. 931GB on a 1TB drive is what a 1TB drive looks like.
Where Disk Management shows unallocated space, recovering it takes about a minute and the full capacity returns immediately.
Where the hardware itself reports a small size, the outcome depends entirely on which cause it is. A corrupt partition table is repairable at the cost of the data. A counterfeit is not repairable at all, and the only sensible response is a refund and a drive bought somewhere with a returns process. If the broader problem is running out of space rather than a faulty drive, freeing up disk space on Windows covers where it usually goes.