Diskmgmt shows the increased space .However the drive is not showing as extended

— ny_wk

When you extend a disk in Windows and Disk Management reports the new, larger size but File Explorer and the drive's Properties dialog still show the old capacity, the partition grew while the NTFS file system did not. The fix is a single command: select the volume in diskpart and run extend filesystem to stretch the file system to match the partition. This guide explains why it happens and how to repair it safely.

The problem: Disk Management shows the increased space but the drive is not extended

You expanded a virtual disk (in VMware, Hyper-V, a SAN LUN, or a cloud volume), grew the partition in Disk Management or diskpart, and the operation reported success. Yet something is clearly wrong:

• Disk Management shows the partition as the new size (for example 80 GB).
• The drive Properties dialog and File Explorer still show the original size (for example 10 GB).
• You may have seen a warning during the operation that the extend completed but the file system could not be resized.

The two numbers do not tie up because there are actually two separate sizes in play: the size of the partition (the slice of the disk reserved for the volume) and the size of the file system (the NTFS structure that lives inside that partition). Disk Management reports partition geometry, while Properties and File Explorer report the file system's reported capacity. When only the partition grows, the gap between them is exactly your missing space.

Why the file system stays the original size when you extend an NTFS volume

This is a long-documented Windows condition (Microsoft Knowledge Base article KB832316). The stated cause is that the NTFS driver exhausts its resources while trying to extend the volume in a single online operation. The partition table is updated to the larger size, but the in-place file-system resize does not complete, leaving the NTFS metadata describing the old, smaller capacity.

In practice it tends to surface when:

• You extend a volume that is online and in use, especially the system or a busy data volume.
• The growth is large or the volume has heavy fragmentation/activity at the moment of the resize.
• The underlying disk was grown by a hypervisor or storage array, then the partition was extended on top of it.

The important point: your data is intact. Nothing was lost. The file system simply needs a second, explicit instruction to claim the space the partition already owns.

The solution: run extend filesystem in diskpart

The reliable fix is to tell NTFS directly to grow into the unused part of the partition. The extend filesystem command in diskpart does exactly that. It is safe, non-destructive, and usually completes in seconds.

Before you start

• Identify the correct drive letter or volume number. Picking the wrong volume and forcing operations on it is the only real risk here.
• Take a backup or snapshot of any production volume first. Resizing is low-risk, but a recent restore point is cheap insurance.
• You need local administrator rights.

Step-by-step fix

1. Open an administrative Command Prompt: right-click Command Prompt (or Windows Terminal) and choose Run as administrator.
2. Launch the partition tool: diskpart
3. List the volumes so you can find the one with the wrong size: list volume
4. Select the affected volume by its number (replace # with the number from the previous step): select volume #
5. Grow the file system to fill the partition: extend filesystem
6. When it reports success, exit: exit

After extend filesystem finishes, the file-system size will match the extended partition size, and the new capacity appears immediately in File Explorer and the drive Properties dialog. No reboot is required.

Two commands that look similar but do different things

This is the single most common point of confusion, so it is worth being precise:

For the symptom in this guide the partition is already large, so you want extend filesystem, not plain extend.

Full worked example with diskpart

Here is a complete session. The volume in question is the data volume D:, which Disk Management shows as 80 GB but Properties shows as 10 GB.

1. Start diskpart from an elevated prompt: diskpart
2. List volumes: list volume. Suppose the output shows Volume 2 D Data NTFS Partition 80 GB Healthy. Even though it says 80 GB at the partition level, NTFS inside it is still only 10 GB.
3. Select it: select volume 2
4. Extend the file system: extend filesystem. diskpart responds with DiskPart successfully extended the file system on the volume.
5. Confirm and quit: exit

Open D: Properties again and the capacity now reads the full 80 GB.

Doing the same thing with PowerShell

On Windows 8/Windows Server 2012 and later you can avoid diskpart entirely and use the Storage module. PowerShell is the modern, scriptable equivalent and is preferable for automation.

First find the maximum supported size for the partition, then resize to it:

1. List partitions to find the one you want: Get-Partition -DriveLetter D
2. Query how large NTFS can grow within the current partition: $max = (Get-PartitionSupportedSize -DriveLetter D).SizeMax
3. Resize the partition/file system up to that maximum: Resize-Partition -DriveLetter D -Size $max

If the disk itself still has trailing unallocated space, this one command grows both the partition and the file system together, which is why it is the cleanest approach on modern systems. The SizeMax value already accounts for the real space available.

Common pitfalls

• Running plain extend when you meant extend filesystem. If the partition is already full size, plain extend fails with "There is not enough usable space" because there is no adjacent free space left to grab.
• Selecting the wrong volume. Always confirm the drive letter and label in list volume before select volume. Note that some volumes (recovery, EFI) have no drive letter.
• Unallocated space is not adjacent. NTFS can only extend into free space that sits immediately after the partition. If there is another partition between yours and the free space, you must first move or delete that partition (or use a tool that supports moving partitions).
• FAT/FAT32 volumes. The extend filesystem path is for NTFS (and ReFS). FAT32 has different rules and a 32 GB practical creation limit in Windows tools; convert to NTFS if you need large-volume growth.
• Hypervisor disk not actually grown. If you expanded the VMDK/VHDX but Windows still does not see new unallocated space, rescan the disk first: in diskpart run rescan, then re-check list disk.
• Stopping at "Disk Management looks right." The whole point of this issue is that Disk Management can look right while the usable space is still wrong. Always verify from the file-system side.

Verification: confirm the file system size now matches the partition

Do not trust a single view. Confirm from at least two of these:

• File Explorer / Properties: right-click the drive, choose Properties, and check that Capacity now equals the extended size.
• diskpart: run list volume again and confirm the Size column matches what you expect for that volume.
• Command line: run fsutil volume diskfree D: to print total bytes, free bytes, and available bytes for D:. The total should reflect the new capacity.
• PowerShell: run Get-Volume -DriveLetter D and read the Size property.

If all of these agree on the larger number, the file system has successfully claimed the extended partition and the job is done.

A note on legacy systems

The original KB832316 scenario dates back to Windows Server 2003/2008 era servers, where the NTFS-resource-exhaustion bug was most visible. On Windows 10/11 and Windows Server 2016 and later, the in-place online extend is far more reliable, and the recommended path is the PowerShell Resize-Partition workflow shown above. The diskpart extend filesystem command still exists and still works on current Windows, so it remains the right tool when you hit the partition-bigger-than-file-system mismatch on any version.

Key Takeaways

• If Disk Management shows the new size but the drive Properties show the old size, the partition grew but the NTFS file system did not.
• The fix is diskpart → select volume # → extend filesystem; it is non-destructive and needs no reboot.
• Know the difference: extend grows the partition into free disk space; extend filesystem grows NTFS into space the partition already owns.
• On modern Windows, Resize-Partition -DriveLetter D -Size (Get-PartitionSupportedSize -DriveLetter D).SizeMax handles both in one step.
• Always verify from the file-system side (Properties, fsutil volume diskfree, or Get-Volume) — not just Disk Management.

Frequently Asked Questions

Why does Disk Management show more space than the drive properties?

Because they measure different things. Disk Management reports the size of the partition (the reserved slice of disk), while Properties and File Explorer report the size of the NTFS file system inside it. When an extend grows the partition but the file-system resize does not complete, the partition value is larger than the usable file-system value.

Is running extend filesystem safe? Will I lose data?

It is safe and non-destructive when you target the correct volume. extend filesystem only stretches the existing NTFS structure into space the partition already controls; it does not move, reformat, or delete files. The only real risk is selecting the wrong volume, so confirm the drive letter in list volume first and keep a recent backup of production data.

What if extend filesystem says there is no space to extend?

That message means NTFS is already using the full partition. In that case the partition itself is still small, so you need plain extend (which requires adjacent unallocated space) or you need to grow the underlying disk in your hypervisor/SAN and run rescan in diskpart before extending.

Can I do this without diskpart on Windows 10 or 11?

Yes. Use PowerShell: Resize-Partition -DriveLetter D -Size (Get-PartitionSupportedSize -DriveLetter D).SizeMax. This grows the partition and file system together up to the maximum space available, which is the preferred method on modern Windows.

For more Windows server and sysadmin walkthroughs, subscribe on YouTube @explorenystream.