Disk Management and Windows Explorer Show Different Sizes

If you encounter a situation where the disk size shows extended with actual size under Disk management but it appears as incorrect size under File Explorer. This is inconsistent after extending a virtual disk in Windows Server, an undocumented DISKPART command can resolve the issue. Below is a concise guide:

DISKPART Fix: EXTEND FILESYSTEM

Open DISKPART:

Launch Command Prompt and type diskpart.

List Volumes:

list volume

Identify the volume experiencing the issue.

Select the Volume:

select volume <Volume_Number>

Replace <Volume_Number> with the number of the affected volume.

Extend the File System:

extend filesystem

This command synchronizes the file system with the newly allocated space.

Exit DISKPART:

exit

Example Usage

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

———- — ———– —– ———- ——- ——— ——–

  Volume 0     D                      Removable     27 PB

  Volume 1     E   DATA_VOL    NTFS   Partition   2000 MB  Healthy

  Volume 2     C   Windows     NTFS   Partition   4001 MB  Healthy    System

DISKPART> select volume 1

DISKPART> extend filesystem

DiskPart successfully extended the file system on the volume.

DISKPART> exit

This method ensures the file system reflects the actual disk size after extending it in Disk Management as well as File Explorer.

Conclusion

The EXTEND FILESYSTEM command is a straightforward yet undocumented solution for resolving discrepancies in disk space reporting on Windows Server and earlier VMs. This ensures that both File Explorer and Disk Management display the correct size after extending a drive. Following the steps outlined above will save you time and eliminate confusion when managing disk space in your virtual environment.

For administrators replicating older server setups or managing legacy systems, understanding these nuances is key to maintaining a smooth and efficient workflow.