When Extend Volume is greyed out in Windows Disk Management, the problem is often not the amount of free space. It is where that space sits on the physical disk.
Windows normally needs unallocated space immediately to the right of the volume you want to extend. A recovery partition, D drive, or any other volume between C and the unallocated space can block the operation.
The quick answer
For Windows Disk Management to extend a volume, check these requirements first:
- The empty area is labeled Unallocated.
- It is on the same physical disk as the volume you want to extend.
- It appears immediately after that volume in Disk Management.
- The volume uses NTFS or ReFS.
- Disk Management is running with administrator permissions.
If one of these conditions is missing, Extend Volume may be unavailable.
1. Open Disk Management without changing anything
Right-click the Start button and select Disk Management. You can also press Windows + R, enter diskmgmt.msc, and select OK.
Focus on the lower half of the window. Each horizontal row represents a physical drive:
- Disk 0, Disk 1, and similar labels identify physical disks.
- C and D are volumes or partitions; they are not necessarily separate drives.
- Unallocated space appears with a black bar.
- Small EFI, recovery, and reserved partitions may not have drive letters.
Do not right-click an unfamiliar partition and experiment with the available options. First record the entire row from left to right.
2. Compare your layout with these common cases
Case A
May workThe empty space is immediately to the right of C on the same disk.
Case B
BlockedThe recovery partition breaks the required adjacency.
Case C
BlockedWindows cannot extend C across the D volume.
Case D
BlockedC:
Unallocated
Capacity on another physical disk cannot be added to C this way.
3. Understand what each blocked layout means
A recovery partition sits in the middle
In a layout such as C | Recovery | Unallocated, the empty space is on the correct disk but not next to C. Do not delete the recovery partition merely to activate a menu option. It may contain tools used when Windows cannot start normally.
D sits between C and the empty space
Windows cannot extend C across D. Shrinking D in Disk Management normally creates unallocated space after D, leaving a smaller D between C and the new empty area. Deleting D would remove the volume and its files.
The capacity is on another disk
Free space on Disk 1 cannot normally extend the Windows volume on Disk 0. Drive letters do not combine physical disks. Moving large files or migrating Windows to a larger SSD is usually more relevant.
4. Check the less obvious causes
The space is free, not unallocated
Free space inside D still belongs to D. Windows cannot give that capacity directly to C without changing the partition layout.
The file system is not supported
Microsoft documents volume extension for NTFS and ReFS. Check the File System column before assuming the layout is the only problem.
The tool is not elevated
If administrator permissions are missing, close Disk Management and reopen it through an administrator account.
An MBR disk has reached its size limit
If the disk is larger than 2 TB, the partition style can matter. Microsoft states that using capacity beyond 2 TB requires GPT. Do not convert the system disk merely because a menu option is unavailable; first confirm the firmware mode, backup, and recovery path.
5. Avoid the fixes most likely to cause damage
- Do not delete a recovery, EFI, or reserved partition because it looks small.
- Do not format a volume to make a menu option appear.
- Do not convert the disk to dynamic storage as an experiment.
- Do not assume C and D are separate physical drives.
- Do not rely on a backup stored on another partition of the same disk.
- Save the BitLocker recovery key if device encryption is enabled.
- Back up irreplaceable files to a genuinely separate destination.
6. Choose the next step from the layout
| What you see | What it means | Safer next step |
|---|---|---|
| C followed by Unallocated | The basic adjacency requirement is present. | Back up first, then review the Extend Volume wizard carefully. |
| Recovery between C and Unallocated | The recovery partition blocks the extension. | Identify the partition and recovery plan; do not delete it blindly. |
| D between C and Unallocated | Windows cannot extend C across D. | Leave the layout unchanged, use a separate volume, or assess a carefully backed-up move operation. |
| Unallocated space on another disk | The capacity belongs to a different physical drive. | Move files or plan a migration to a larger system SSD. |
| No unallocated space | The physical disk has no capacity ready to add. | Return to storage cleanup before considering layout changes. |
What this diagnosis proves—and what it does not
Reading Disk Management can explain why Extend Volume is unavailable and show whether Windows has adjacent unallocated space. It does not prove that a third-party tool can safely move an intervening partition, or that the PC will boot normally after a layout change.
Microsoft lists a non-Microsoft partitioning application that can move volumes as one possible route when another volume sits in the middle. That is not a recommendation for a particular product. RestorePath Lab has not completed a partition move on its current test hardware.
Bottom line
Do not treat a greyed-out menu option as something to bypass. First identify the complete physical-disk layout. If unallocated space is not immediately to the right of C, Windows is usually blocking the operation because the partitions are in the wrong order—not because it failed to notice the available capacity.
Protect the files and recovery partitions first. A full C drive is inconvenient; an unnecessary partition deletion can turn it into a startup or data-loss problem.
Official sources checked July 29, 2026: Microsoft's volume-extension requirements and Disk Management guidance for Windows.