Transfer/Move Free Space on Windows Server 2019/2022

by John, Updated on: June 11, 2026

When the system C drive experiences critical storage shortages, administrators frequently look for solutions to reallocate storage boundaries. A common question is whether it is possible to move free space from data volumes directly into the primary partition. While this modification is entirely feasible, native Windows tools lack the architectural capability to execute it, making specialized utilities necessary. To safely adjust sector allocations without risking data loss, utilizing a reliable partitioning application is essential. This article explains how to move free space in Windows Server 2019/2022 without data loss.

Windows Server 2019/2022 cannot move disk space

Starting with Windows Server 2008, Microsoft introduced the "Shrink Volume" and "Extend Volume" capabilities within the native Disk Management snap-in. These functions allow administrators to resize partition without losing data under very specific layout conditions. Specifically, the built-in controller can only shrink an NTFS volume to generate unallocated block space on its right side, or extend an NTFS drive by absorbing contiguous unallocated space directly adjacent to its right boundary. Consequently, native utilities are completely incapable of moving storage blocks across alternate partitions, making professional third-party software mandatory for advanced reallocations.

As illustrated in the administration panel, the Extend Volume function becomes unavailable for both the C and E drives immediately after shrinking drive D inside the Disk Management utility.

Extend Volume disabled

This operational blocker occurs due to the following structural limitations:

  • The shrink utility can only generate unallocated sectors on the strict right side of the targeted partition.
  • The extend function can only reallocate capacity into a partition situated directly adjacent on the left contiguous boundary of the unallocated space.

Once drive D is shrunk, the system C drive remains non-contiguous to the newly generated unallocated block. Meanwhile, drive E sits entirely to the right of that block, causing the volume extension mechanism to fail.

The command-line diskpart tool shares identical architectural limitations.

Move free space from D/E to C drive on Windows Server 2019/2022

To transfer free space across alternate storage drives in Windows Server 2019/2022 environments, deploying a reliable server partition application is necessary. While several utilities exist, implementing an extensively certified partition management package is critical to mitigate the risks of filesystem corruption or boot structure errors during raw partition resizing. Outperforming conventional disk tools, NIUBI Partition Editor incorporates advanced data protection and file routing features:

Steps to move disk space from D to C drive in Windows Server 2019:

  1. Launch NIUBI Partition Editor, right-click the contiguous data partition D, and select the "Resize/Move Volume" option.
  2. In the interactive interface, drag the left border toward the right side (or input your desired capacity in the "Unallocated space before" block) to shrink the drive and create an unallocated partition block on its left edge.
  3. Right-click the C drive, launch "Resize/Move Volume" again, and drag its right border toward the right side to safely absorb the newly generated unallocated capacity.
  4. Click the "Apply" icon positioned in the upper-left corner of the master panel to execute the staged tasks.

Video Server 2019

When attempting to transfer space from a non-adjacent partition (such as drive E) to the C drive, shrink the source partition to generate an unallocated block on its left boundary first. Before you can safely add unallocated space to C drive configurations, you must include an intermediate step to move unallocated space from the right side of drive D over to its left boundary.

Cannot move free space or unallocated space from another disk

In some enterprise storage configurations, the primary disk lacks auxiliary volumes or contains insufficient free space. Administrators often investigate whether it is possible to harvest unallocated sectors from a completely separate physical hard drive. Structurally, no software solution can move or merge capacity across independent separate disks because the boundary limits of an individual physical hard drive are constant. However, alternative scaling procedures can resolve this limitation.

Method 1: Scaling configurations via physical disk migration

Because the physical sector layout of an individual hard drive cannot be dynamically expanded, a 500 GB drive cannot be modified to hold 600 GB of data. If a physical storage drive is entirely full, you can easily copy the existing configuration to a larger drive container. This workflow allows the extra unallocated storage block to be safely mapped and allocated to your targeted volumes. Follow the operational video tutorial to complete the migration:

Video Server 2019

Method 2: Scaling configurations within hypervisor environments

When running Windows Server 2019/2022 as a guest virtual machine inside VMware or Hyper-V infrastructures, you can expand the underlying virtual disk file directly without performing a physical drive copy. Follow the corresponding hypervisor deployment guides:

Following the virtual disk expansion, the newly provisioned block capacity appears as unallocated space at the end of the virtual drive. You can then apply the standard steps to move and merge unallocated space into your system partition.

In Summary

When attempting to reallocate free capacity in Windows Server 2019/2022 environments, native options like Disk Management and diskpart are restricted by contiguous block limitations, making the deployment of secure partitioning utilities essential. Equipped with robust data protection architectures, NIUBI Partition Editor streamlines volume restructuring tasks safely and efficiently. Simply choose the appropriate reallocating workflow that maps to your existing disk layout. These methods apply identically if your storage runs on enterprise hardware RAID configurations (such as RAID 1, 5, 6, or 10) without requiring array teardowns. Beyond resizing boundaries and shifting sector allocations, the application provides a versatile toolkit for complete disk management.

Download