Cannot Extend VM Partition in Windows Server 2022 When Option Is Greyed Out

In a Windows Server 2022 VM, Extend Volume may stay greyed out even after you expand the virtual disk. Usually the guest OS has not rescanned the disk, the free space is not next to the volume, or another partition blocks it.

Before You Start

• Take a VM snapshot or backup before resizing.
• Expand the virtual disk from the hypervisor first.
• Rescan disks inside Windows Server.
• Check whether the unallocated space is directly behind the target volume.

Windows Server Method When the Space Is Adjacent

1. Pause databases, file shares, or other heavy workloads if the VM is in production.
2. Take a VM snapshot or create a server backup.
3. Expand the virtual disk in Hyper-V, VMware, or your cloud console. This step only increases the virtual disk size; it does not extend the Windows partition yet.
4. Start Windows Server 2022, open Disk Management, and choose Action > Rescan Disks.
5. Check whether the new unallocated space is directly to the right of the target volume.
6. If it is adjacent, right-click the target volume and choose Extend Volume.
7. Follow the Extend Volume Wizard, keep the correct disk space selected, and finish the wizard.
8. Open File Explorer or Disk Management again to confirm the volume shows the new size.

Use Qiling Disk Master When Extend Volume Is Still Greyed Out

Use Qiling Disk Master after the virtual disk has already been expanded and Windows Server can see the added unallocated space. The next step depends on the partition order on the VM disk.

• Free Download

Check the Expanded Virtual Disk First

Open Qiling Disk Master inside the VM. Select the virtual disk by disk number, total capacity, and partition layout. Confirm the added space appears as unallocated space on the same virtual disk. Then use the case that matches your disk layout.

Case A. Unallocated Space Is Adjacent to the Target Volume

Step 1. Select the target volume, such as C: or a data volume. Confirm it is on the expanded virtual disk and the unallocated space is directly to its right.

Step 2. Choose Resize/Move for the target volume.

Step 3. Drag the right border into the adjacent unallocated space, or enter the new volume size manually.

Step 4. Preview the layout. It should show only the target volume becoming larger, with no delete, format, or move operation.

Step 5. Click Proceed. Restart the VM if Qiling asks for it, then confirm the new volume size in Disk Management.

Case B. Another Partition Blocks the Unallocated Space

Step 1. Select the partition between the target volume and the unallocated space. If it is a data partition, confirm its files are backed up. If it is a recovery partition, keep it and move it instead of deleting it.

Step 2. Choose Resize/Move for the blocking partition.

Step 3. Drag the whole blocking partition to the right side of the unallocated space. This makes the unallocated space sit directly behind the target volume.

Step 4. Preview the move operation and click Proceed. Wait until the move finishes, and restart the VM if required.

Step 5. Select the target volume again, choose Resize/Move, extend it into the now-adjacent unallocated space, preview the final layout, and click Proceed.

Step 6. After Windows Server starts, open Disk Management and confirm the target volume shows the expanded size.

Case C. Windows Server Does Not Show the Added Space

Step 1. Return to the hypervisor or cloud console and confirm the virtual disk size was actually increased.

Step 2. Inside Windows Server 2022, open Disk Management and choose Action > Rescan Disks.

Step 3. If the size still does not change, restart the VM during a maintenance window and open Disk Management again.

Step 4. If the added space appears after restart, go back to Case A or Case B based on whether the unallocated space is adjacent to the target volume.

Step 5. If the added space still does not appear, check the VM storage controller, snapshot chain, cloud disk attachment, or hypervisor task status before trying partition operations.

After Extending the VM Partition

• Open Disk Management and confirm the volume shows the new size.
• Check the application or shared folder that uses the extended volume.
• Remove the VM snapshot only after the server runs normally.

Conclusion

For VM disks, always expand the virtual disk first, make Windows Server recognize the added space, and then extend the partition. If the space is blocked, move the blocking partition before extending the target volume.

Related Articles

• Windows Partition Management Tutorials
• Windows Data Recovery Tutorials

Is this information helpful?   Yes   No

This information is not relevant.

This information is not easy to understand.

This information is not deep enough.

What can we do to improve this information? (Optional)

Refresh Please enter the verification code!