Why won't DiskPart let me extend my volume?

Oliver

So my D drive is running out of space. I shrank my E drive to get 50GB of unallocated space. But DiskPart keeps telling me it can't extend the volume.

Do the unallocated space and the drive need to be right next to each other or something? I thought DiskPart could force it to work but it just fails. Any workarounds that don't involve losing my data?

john2451

Oliver This is the oldest Windows quirk in the book. As others hinted, Windows DiskPart cannot perform "sector jumping." If your layout looks like [D:] [E:] [Unallocated], D can't see past E.

The zero-dollar, natively built-in solution? Back up everything on E, delete E entirely so the unallocated space moves directly next to D, extend D, and then recreate E with what's left. It's tedious but 100% safe if you actually do the backup.

Daive7485

Yeah, you hit the classic Windows "wall." It's super annoying, but unallocated space must be sitting directly to the right of your D drive for DiskPart or Disk Management to even touch it.

The reason it's failing is that your E drive is currently "standing in the middle" of your D drive, and that 50GB of free space. Windows isn't smart enough to just "hop over" an existing partition to grab space elsewhere.

If you don't have too much stuff on your E drive, the cleanest way is to back up E's files to an external drive, delete the E partition entirely (so all that space becomes one big unallocated block next to D), extend D, and then recreate a smaller E partition.

Good luck!

LeoF_225

Yeah, DiskPart can only extend a partition into unallocated space that's directly next to it on the right side. So if your layout is basically:

[D:] [E:] [50GB Unallocated]

then D: still can't use that space, because E: is sitting in between.

Shrinking E: only creates free space after E:, not after D:. That's why the extend command fails even in DiskPart — it has the same limitation as Disk Management on basic disks.

You've basically got a realistic option if you want to keep the data:

Back up E:, delete the E: partition, extend D:, then recreate E:

Just make sure you back up anything important first. Moving partitions is usually safe, but if something interrupts the operation (power loss, crash, etc.), things can go bad pretty quickly.

Also check whether there's a Recovery/System partition between D: and E:. Sometimes that's the real thing blocking the extend operation, not the main partition itself.

katonof216

Yeah, gotta be right next to it.

BANDMANATL

john2451 "It's 100% safe if you actually do the backup."

Bold of you to assume Windows users know what a backup is. They’ll just delete E, lose 400GB of "homework" folders, and then come back here crying that DiskPart ruined their lives.

Seriously though, it’s 2026 and Microsoft still handles partition tables like it’s MS-DOS 6.22 running on a floppy disk.

furqanali8975

BANDMANATL To be technically precise, this isn't strictly an MS-DOS legacy issue, but rather a fundamental constraint of the Contiguous Allocation architecture utilized by Basic Disks under the MBR/GPT specification.

When you format a partition as a basic volume, the NTFS metadata (specifically the $Bitmap and $MFT) expects a contiguous range of Logical Block Addresses (LBAs). DiskPart can extend non-contiguously, but only if you convert the disk to a Dynamic Disk, which creates a spanned volume. However, doing so introduces a single point of failure and strips the ability to boot from those volumes. Hence, the OS natively restricts the extend command on basic disks to adjacent sectors on the right.

Mikoo3561

furqanali8975 Imagine writing a whole paragraph defending proprietary technical debt lmao.

"Contiguous allocation architecture" is just a fancy corporate euphemism for "our OS partition manager sucks." Linux LVM (Logical Volume Manager) solved this decades ago by abstracting physical extents. You can pool storage from anywhere, even across different physical drives, without breaking a sweat.

OP, skip this Windows garbage. Burn a GParted Live USB, boot into it, drag-and-drop your E partition to the right, and extend D. It literally takes 3 clicks and doesn't force you to delete your files.

rudolfaslamsargis826

Mikoo3561 Furiously taking notes Wait, what is GParted? Is it safe to use on a Windows machine? Won't moving the partition to the right corrupt the Windows registry if E drive has installed programs? Sorry if this is a dumb question, I'm just trying to learn.

john2451

rudolfaslamsargis826 Not a dumb question at all, kid. Ignore the Linux elitist above.

To answer your question: Yes, if E drive contains installed software or game libraries (like Steam), moving its starting sector can occasionally break shortcuts or registry paths if the drive letter changes during the process, though GParted usually preserves the UUID.

But honestly, telling a regular user to boot into a Linux live USB just to resize a partition is like recommending open-heart surgery for a papercut. Just download a free partition assistant tool that has a "Merge Partition" or "Move Partition" feature that automates the whole thing safely within Windows.

Mikoo3561

john2451 Calling GParted "open-heart surgery" while recommending closed-source, adware-laden Windows "utilities" is peak Windows admin coping mechanism.

GParted is open-source, lightweight, and actually respects your hardware. If Windows users spent 10 minutes learning how block devices actually work instead of clicking "Next" on shady freeware installers, threads like this wouldn't exist.

furqanali8975

Mikoo3561 While GParted is an excellent tool utilizing libparted to shift the sector offsets block-by-block, it is imperative to note that moving the starting sector of a partition forces a massive sequential read/write operation.

If OP has a spinning HDD or a DRAM-less QLC SSD, moving 500GB of data on E drive to the right to accommodate D drive's extension will cause severe write amplification. If a power outage occurs mid-operation because they didn't use an Uninterruptible Power Supply (UPS), the partition layout table will desynchronize from the actual data payload, leading to a catastrophic RAW filesystem error. @john2451 's backup-and-delete method, while archaic, minimizes sector-shifting risks.

k1413t

I split volume into two. They are next to each other. They show NTFS, Primary. I then attempted to use the merge function to go back to the full space. I went through the steps, the pc rebooted but I still have two volumes. Any help would be greatly appreciated.