AOMEI
Extend Volume Greyed Out? Check the Partition Layout Before Changing C:
Free space on D: is not the same as unallocated space beside C:. Read the disk layout before deleting a partition or applying a resize operation.
Windows Disk Management normally needs suitable unallocated space immediately to the right of the volume on the same disk to extend it. Free space inside D:, space on another physical disk, or unallocated space separated by a recovery partition does not meet that basic layout requirement.
C: is almost full. D: has room, or a new larger SSD has unused capacity, yet Extend Volume is greyed out. Buying more storage software or repeatedly shrinking D: will not help until the position of that space is understood.
Take a screenshot of the lower graphical view in Disk Management and identify the physical disk containing Windows. Read the partitions from left to right, including the small system and recovery partitions.
Read the Disk Layout Before Changing Anything
Check the disk number, partition order, file system and whether the disk is basic or dynamic. The guidance here concerns a normal Windows basic-disk layout. Storage Spaces, dynamic volumes and managed corporate systems need their own assessment.
Microsoft lists NTFS or ReFS and immediately following unallocated space on the same disk among the requirements for extending a basic volume. A typical Windows C: drive is NTFS. The black unallocated region in Disk Management is different from the free capacity shown inside a formatted volume.
Record the exact layout before deciding what to move. Avoid identifying a partition by size alone. A small partition may contain the Windows boot files or recovery environment.
Where the Space Sits Changes the Answer
Both examples show one basic disk. Block widths are not capacities.
01 Space is separated from C:
Normal extension is blockedDisk Management does not extend C: across the intervening recovery partition.
02 Space is beside C:
Other prerequisites still applyConfirm the file system, disk state and a protected resize plan before applying a change.
Why Shrinking D: Often Does Not Help C:
Suppose the order is C:, then D:. Shrinking D: with Disk Management normally creates unallocated space after D:. D: remains between C: and the newly available space, so C: still cannot use it through the normal Extend Volume workflow.
A recovery partition can create the same obstruction after cloning to a larger SSD. The extra capacity is real, but Windows cannot reach across an intervening partition to extend C: in Disk Management.
| What you see | Why Extend Volume may be unavailable | Useful next check |
|---|---|---|
| D: has plenty of free space | That space still belongs to D: | Compare partition order and the amount each volume needs. |
| Unallocated space is after Recovery | The space is not adjacent to C: | Plan the recovery partition position before any move. |
| Another disk has spare capacity | It is not the same physical basic disk | Consider moving data or a properly planned system migration. |
| Unallocated space is immediately after C: | Another prerequisite may be unmet | Check the file system, disk status, administrative access and any error message. |
Do not delete D: just to make the menu available. That removes its partition and puts its contents at risk. A layout change should follow a verified backup and a complete plan for the retained data.
Choose Between Cleaning Up, Moving Data and Resizing
If C: only needs temporary relief, review Windows storage usage, downloaded installers and files that can safely move elsewhere. Move supported data locations through the relevant application's settings. Dragging application folders or system directories to another drive can break them.
When space exists on the same disk but the layout blocks expansion, AOMEI Partition Assistant Professional offers partition management tools beyond Disk Management. The exact operation depends on the layout: moving a partition, resizing it and extending another volume are related but separate actions.
The manufacturer's Resize/Move workflow is shown below. It is a vendor interface example, rather than a picture of your disk. Confirm the selected disk and partition in your own system before queuing an operation.
Prepare the Backup, Recovery Key and Power
Make a current backup to a separate destination and check that important files can be recovered. A pending resize preview is not a backup. Keep suitable Windows recovery media and a way to access the backup if the computer does not start normally.
For an encrypted drive, check BitLocker status and retain the recovery key privately before storage changes. Suspending BitLocker protection is not the same as decrypting the drive. Follow the current instructions for the precise operation: AOMEI's resize guidance specifies decryption for a BitLocker-encrypted partition before resizing it.
Allow enough uninterrupted time and stable power. A partition move can take longer than changing a boundary into already adjacent free space because data may need to be relocated. Do not interrupt a storage operation simply because its progress appears slow.
Check the Proposed Order Before You Select Apply
Review the pending operations and resulting disk map. Check the target volume, final capacity, partition order and retained system and recovery partitions. If the preview does not match the intended result, cancel the queued plan and reassess before it is applied.
After a successful change, confirm that Windows starts, C: has the expected capacity, the other volumes and files remain accessible and the recovery arrangement is still available. Recheck encryption and protection status according to the operation's instructions.
If errors, an unhealthy disk or an unfamiliar partition arrangement appear, stop the resize plan and investigate. A partition tool cannot turn a failing physical drive into reliable storage. Repeatedly trying different destructive operations makes recovery harder.
Choose the Edition for the Computer You Manage
Partition Assistant Professional is a Windows PC edition. Confirm the licence entitlement for the computers and use case involved. A Windows Server installation needs an appropriate Server edition; a product name containing Professional does not make it a server licence.
Choose the Windows PC edition and a resize method that matches the actual disk layout and encryption requirements.
The useful answer is a layout plan: identify where the available space sits, protect the data, then choose the least disruptive supported method. If the physical SSD is too small, a correctly planned migration may be more sensible than repeatedly rearranging nearly full volumes.
For that route, use the cloned SSD boot checklist to plan an independent boot test before erasing the original drive.
Frequently Asked Questions
Why is Extend Volume greyed out when D: has free space?
The free space remains inside D:. Disk Management needs suitable unallocated space immediately after the target volume on the same basic disk. The partition order matters.
Will shrinking D: let me extend C:?
Often it will not, because shrinking D: creates unallocated space after D:, leaving D: between C: and that space. Check the actual resulting disk map before making changes.
Can I delete the recovery partition to make room?
Do not delete it casually. It may contain the Windows recovery environment. Preserve a working recovery route and have the complete layout assessed before changing system or recovery partitions.
Can C: use free space from a second SSD?
Not through a normal basic-volume extension of the Windows system partition. Moving data or migrating the system to a suitable larger drive may be the more appropriate plan.
Is suspending BitLocker enough before resizing?
It is not equivalent to decryption. Follow the current tool instructions for the exact operation; AOMEI resize guidance requires decryption for a BitLocker-encrypted partition. Keep the recovery key available privately.
Does Partition Assistant Professional cover Windows Server?
Professional is a Windows PC edition. Choose the appropriate Server edition for a supported Windows Server system and verify the licence scope before use.
