Extend Volume is greyed out, and the reason is beside it
Windows will only grow a partition into free space immediately to its right. What to check in Disk Management, and the ways around it.
You freed space, you opened Disk Management, and Extend Volume is grey. The reason is almost always positional rather than mysterious: Windows can only grow a partition into unallocated space that sits immediately to its right on the same physical disk.
The four rules, in the order they bite
- The free space must be unallocated, not another formatted partition. Free space inside D does nothing for C.
- It must be adjacent, and to the right, in the Disk Management layout view.
- It must be on the same disk. Space on disk 1 cannot extend a partition on disk 0.
- The volume must be NTFS or ReFS. FAT32 and exFAT partitions cannot be extended this way.
Reading the layout properly
# Elevated prompt. This is the picture Disk Management draws.
diskpart
list disk
select disk 0
list partition
exit
# Or without diskpart
Get-Partition | Select-Object DiskNumber, PartitionNumber, DriveLetter, Type,
@{n='SizeGB';e={[math]::Round($_.Size/1GB,1)}}, Offset | Sort-Object DiskNumber, OffsetSorting by Offset puts the partitions in physical order, which is the thing the graphical view shows and the list view hides. Whatever sits between your partition and the free space is the blocker.
What is usually in the way
| In the gap | What to do |
|---|---|
| A recovery partition | Usually the culprit after an upgrade. See the guide below |
| Another data partition | Move its contents, delete it, then extend |
| Unallocated space to the left | Windows cannot extend leftwards. The partition has to be moved |
| Nothing, and it is still grey | Check the file system is NTFS and the disk is basic, not dynamic |
A recovery partition sitting between C and the free space is the most common single cause, and it appears there because an upgrade created a new one. That is its own subject, including whether removing it is wise: the recovery partition.
The other half: Shrink Volume stopping early
The mirror image of this problem is asking to shrink C by 200 GB and being offered 40. Windows will not move unmovable files, and the ones that sit near the end of the volume set the limit.
| Unmovable file | Turn it off temporarily with |
|---|---|
pagefile.sys | System properties, Advanced, Performance, no paging file |
hiberfil.sys | powercfg /hibernate off |
| Shadow copies | Disable System Protection, or delete snapshots |
Turn those off, restart, shrink, then turn them back on. Each has its own page: the page file, hiberfil.sys and shadow copies.
When not to bother
If the machine has a second drive, moving a large folder there is faster, safer and reversible, which is the argument in C drive against D drive and moving programs to another drive. Repartitioning a boot drive to win 30 GB is a lot of risk for a number a single cache clearance often beats.
Common questions
Why is Extend Volume greyed out in Disk Management?
Because there is no unallocated space immediately to the right of that partition on the same disk. Free space inside another partition, space on a different disk, or space to the left will all leave the option disabled.
How do I extend C drive when the space is not next to it?
Whatever sits between has to go: move its contents and delete it, or move the partition itself. A recovery partition created by an upgrade is the most common blocker.
Why can I only shrink my drive by a small amount?
Unmovable files near the end of the volume set the limit, typically the page file, the hibernation file and shadow copies. Disabling those temporarily, restarting and then shrinking gives the full amount.
Can I extend a partition onto a second disk?
Not as a basic volume. It requires converting to a dynamic disk or a storage pool, both of which have real trade-offs. Moving folders to the second drive is usually the better answer.