iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Windows is usually not saying that the volume has too little free space. The warning “You cannot shrink a volume beyond the point where any unmovable files are located” means that Windows found a file or NTFS structure near the end of the partition that it cannot move while Windows is running. Because Disk Management shrinks a volume from its trailing end, it stops before that item.

The safest fix is to identify the blocker first, then temporarily address only that specific issue. Start with a backup, inspect Event Viewer for shrink event 259, and then move or temporarily disable the paging file, hibernation, or shadow-copy storage only if the diagnostic points to it. Reboot, retry the shrink, and restore any changed Windows features afterward.

Fix “Cannot shrink a volume beyond the point” in Disk Management

This error is common when shrinking a C:, D:, or other Windows partition to create a new volume, prepare unallocated space for Linux, or transfer space between partitions. It affects the built-in resizing process in Windows 10 and Windows 11, including NTFS volumes that appear to have plenty of free space.

Why Windows cannot shrink the volume farther

Windows can reduce a partition only from its end. It can often relocate ordinary files, but some files and file-system structures cannot be moved automatically while the volume is mounted. If one of them is close to the end, it establishes the smallest size Windows will allow.

[used files] [free space] [unmovable file] [free space]
                                      ↑
                    Windows cannot shrink past this point

That is why these three terms are not interchangeable:

Term	Meaning
Free space	Space not currently occupied by ordinary files. File Explorer reports this figure.
Shrinkable space	The amount Windows can safely remove from the end of the volume while preserving the file system.
Unallocated space	Space outside the partition. It can be used to create another volume or, when positioned correctly, extend an existing one.

For example, a volume might show 200 GB of free space but offer only 20 GB to Disk Management if an unmovable file is located near the partition boundary. Microsoft documents this end-of-volume limitation and identifies paging files and shadow-copy storage as examples of data that may prevent further shrinking.

Common blockers include:

• pagefile.sys, the paging file used for virtual memory;
• hiberfil.sys, the file used by hibernation and related power features;
• System Protection restore points and Volume Shadow Copy storage under System Volume Information;
• NTFS metadata such as the USN change journal, the volume bitmap, or the master file table;
• file-system errors, bad clusters, encryption-related restrictions, or another partition-layout problem.

The paging file is frequently reported in practical troubleshooting, but it is not the universal cause. The diagnostic event should determine which fix to try.

Check the partition and prepare before resizing

Partition-boundary changes are normally safe when Windows completes them successfully, but an interruption, failing disk, or incorrect volume selection can cause data loss. Complete these checks first:

1. Back up important files. For a system volume, an image backup is preferable to relying only on a few copied documents. For a data volume, make sure the backup can actually be opened or restored.
2. Use AC power on a laptop and do not force a restart, close the lid, or disconnect the drive during a resize.
3. Open Disk Management by pressing Win+R, entering diskmgmt.msc, and pressing Enter. You can also right-click Start and select Disk Management.
4. Confirm the correct physical disk, drive letter, volume label, capacity, and file system. Selecting the wrong volume in DiskPart is a serious operational error.
5. Confirm whether the volume is a normal basic NTFS volume. Microsoft’s documented shrink procedure covers basic NTFS volumes and volumes with no file system. DiskPart also documents shrinking simple or spanned dynamic volumes, but the available operations depend on the disk type and layout.
6. Do not use the procedure on an EFI System, OEM, or recovery partition. These special partitions are excluded from the documented DiskPart shrink command.
7. Check whether BitLocker is enabled and make sure the recovery key is backed up. Use an elevated Command Prompt to inspect it:

manage-bde -status

A raw partition containing data should not be treated casually. Microsoft warns that shrinking a partition without a recognized file system can destroy data, so use a verified backup and a tool that explicitly supports the volume type.

Decide what the unallocated space must accomplish

Before shrinking, decide whether you need to:

• create a new Windows volume;
• leave the space unallocated for a Linux installer; or
• extend another existing partition.

This matters because shrinking one partition does not automatically give its space to another. If you shrink D:, Windows normally places the unallocated space after D:, not beside C:. The built-in Extend Volume command generally requires unallocated space to be immediately after the volume being extended on the same physical disk.

Find the file blocking the shrink

1. Make one diagnostic shrink attempt

1. Open Disk Management with diskmgmt.msc.
2. Right-click the intended volume and select Shrink Volume.
3. Note the maximum amount Windows offers.
4. If that amount is insufficient, cancel the dialog rather than accepting an unexpectedly small result.

That analysis can create an entry in the Application log identifying the last unmovable file, its cluster location, and the shrink boundary.

2. Check Event Viewer for event 259

Open:

Event Viewer → Windows Logs → Application

Search or filter for the defragmentation service, commonly shown as defrag or Microsoft-Windows-Defrag, and especially Event ID 259. The exact event wording and available identifiers can vary between Windows builds, but look for references to the last unmovable file, its last cluster, and the minimum volume size.

Examples of items that may appear include:

• pagefile.sys::$DATA
• System Volume Information...::$DATA
• $Extend$UsnJrnl:$J:$DATA
• $Bitmap::$DATA

These examples are not a list of files that should be deleted. They tell you which branch of the troubleshooting procedure to use. Microsoft specifically recommends using event 259 to identify the unmovable file.

3. Map a reported cluster to a file

If the event provides a cluster number, open Command Prompt as administrator and run:

fsutil volume querycluster C: 0x749141f

Replace C: with the affected volume and replace 0x749141f with the cluster value from your event. The querycluster operation identifies which file uses the specified logical cluster. See Microsoft’s fsutil volume documentation for the command syntax.

4. Inspect shadow copies when the event points to System Volume Information

To list shadow copies associated with C:, run this in an elevated Command Prompt:

vssadmin list shadows /for=C:

A result involving System Protection or shadow-copy storage does not necessarily mean all shadow copies must be removed. Use the least destructive applicable option in the next section.

Fix the specific blocker

Paging file: move it or temporarily disable it

If event 259 identifies pagefile.sys on the partition being shrunk, move the paging file to another suitable volume if possible. Temporarily disabling it is a fallback, not a permanent performance recommendation.

1. Press Win+R, enter systempropertiesadvanced.exe, and press Enter.
2. On the Advanced tab, under Performance, select Settings.
3. Select the Advanced tab.
4. Under Virtual memory, select Change.
5. Clear Automatically manage paging file size for all drives.
6. Select the volume you need to shrink, usually C:, select No paging file, and select Set.
7. If another suitable volume is available, select it, choose System managed size, and select Set. Moving the page file is generally preferable to having no page file.
8. Confirm the dialogs and restart Windows.
9. Retry the shrink operation.
10. After resizing, return to the same Virtual Memory dialog, restore a system-managed paging file on the preferred volume, confirm the changes, and restart again.

The paging file supports virtual memory and may be important for memory-intensive workloads, system stability, and crash-dump configuration. A machine with limited RAM may behave poorly while it is disabled. Do not attempt to delete pagefile.sys from File Explorer.

Hibernation: use Powercfg, not manual deletion

If the blocker is hiberfil.sys, open Command Prompt as administrator and run:

powercfg.exe /hibernate off

This supported command disables hibernation and removes the hidden hibernation file from the operating-system drive. Restart Windows, retry the shrink, and restore the feature afterward with:

powercfg.exe /hibernate on

Disabling hibernation also disables hybrid sleep. Microsoft warns that this can create a data-loss risk if power is lost while hybrid sleep is enabled, so treat the change as temporary. Do not manually delete hiberfil.sys.

System Protection or shadow copies: preserve recovery data unless you accept its loss

If event 259 points to shadow-copy storage or System Volume Information, first decide whether existing restore points are worth keeping. Restore points can help recover from a problematic driver, update, or application installation. Deleting them removes that recovery history; it does not simply reclaim harmless temporary files.

To temporarily disable System Protection through the graphical interface:

1. Press Win+R, enter systempropertiesprotection.exe, and press Enter.
2. Select the affected system drive.
3. Select Configure.
4. Temporarily choose Disable system protection.
5. If Windows offers a Delete option and you use it, understand that existing restore points will be removed.
6. Restart Windows and retry the shrink.
7. After the resize, return to this dialog, re-enable System Protection, set an appropriate storage limit, and create a new restore point.

For deliberate, command-line removal of all client-accessible shadow copies for C:, Microsoft documents:

vssadmin delete shadows /for=C: /all

This is destructive and should not be a routine first step. Review the output of vssadmin list shadows /for=C: first and use the command only if you accept the loss of those shadow copies.

Advanced users may instead relocate or limit shadow-copy storage. For example:

vssadmin resize shadowstorage /for=C: /on=D: /maxsize=900MB

Microsoft warns that resizing a shadow-storage association may cause existing shadow copies to disappear. The destination must be appropriate and have sufficient space, so do not apply this example blindly.

Ordinary fragmentation: optimize once, but do not expect a guarantee

Free-space consolidation can help when ordinary files or fragmented free space are limiting the shrink. In an elevated Command Prompt, you can run:

defrag C: /X

The /X option requests free-space consolidation. Microsoft notes that approximately 15% free space is needed for complete and adequate defragmentation. You can also use:

Search → Defragment and Optimize Drives → select the volume → Optimize

On a hard disk, Windows performs traditional defragmentation. On an SSD, Optimize Drives normally performs SSD-appropriate maintenance such as TRIM rather than treating it like a mechanical disk. Do not repeatedly force manual defragmentation on an SSD, and do not assume optimization can move protected system files or NTFS metadata. This warning is about logical cluster placement, so using an SSD does not automatically remove the limitation.

File-system errors: run CHKDSK when the symptoms justify it

Run a file-system check if Disk Management reports a generic failure, the volume is marked dirty, Event Viewer shows file-system errors, the shrink continues to fail after the obvious blockers are handled, or the disk shows signs of corruption.

Start with an online NTFS scan:

chkdsk C: /scan

If errors are found, repair them with:

chkdsk C: /f

Windows may schedule the repair for the next restart if it cannot lock the operating-system volume. Back up important data before repair. Do not add /r casually: it checks for bad sectors and attempts data recovery, can take substantially longer, and is more appropriate when physical-disk problems are suspected.

NTFS metadata and bad clusters require a different plan

If the diagnostic identifies $UsnJrnl, $Bitmap, $MFT, or another NTFS metadata structure, do not try to delete or edit it manually. Windows may be unable to relocate that structure during an online shrink. After confirming the backup and checking the file system, use a trusted offline partition tool or choose a backup-and-recreate approach.

Bad clusters are a more serious warning than an ordinary resize limitation. Microsoft states that an excessive number of dynamically remapped bad clusters can prevent shrinking and recommends moving the data and replacing the disk. Do not rely on block-level copying in this situation, because the bad-sector table may be copied as well.

Retry the shrink with Disk Management

Once the identified blocker has been addressed and Windows has restarted where required:

1. Open diskmgmt.msc.
2. Verify the disk, drive letter, label, and current capacity again.
3. Right-click the volume and choose Shrink Volume.
4. Enter an amount that is no greater than the maximum currently offered.
5. Confirm the operation and wait for it to finish without interruption.

Disk Management should then show an Unallocated region immediately after the reduced volume.

Retry with DiskPart when you need more control

DiskPart is useful for querying the current limit and requesting a precise amount, but it is not a guaranteed bypass for unmovable files. It uses the same Windows storage and file-system constraints, so it may report the same minimum size as Disk Management.

Open Command Prompt as administrator and use:

diskpart
list volume
select volume N
shrink querymax

Replace N with the correct volume number. Use the size, label, drive letter, and file-system columns from list volume to verify your selection before shrinking.

To request a specific amount:

shrink desired=51200

DiskPart’s desired value is the amount to remove, in MB; it is not the desired final partition size. Approximately 50 GiB corresponds to 51,200 MB in this example.

You can provide a smaller fallback amount:

shrink desired=51200 minimum=40960

This asks Windows to remove 51,200 MB if possible, but to accept at least 40,960 MB if the larger request cannot be met. If the current maximum is below the minimum, the command will still fail.

A complete example is:

diskpart
list volume
select volume 3
shrink querymax
shrink desired=51200 minimum=40960
exit

The maximum reported by querymax can change while applications access the volume. Close unnecessary applications and avoid making other storage changes while running the command.

Optional: try smaller increments

Some users report that several smaller DiskPart operations work when one large request does not:

shrink desired=10240
shrink desired=10240
shrink desired=10240

This is not a guaranteed Microsoft-supported workaround and should not replace identifying the blocker. Use it only after a backup, when the requested reduction is modest, and verify the volume in Disk Management after every operation. If DiskPart says the requested size would make the volume smaller than its minimum size, reduce the request or return to blocker diagnosis.

Can PowerShell resize the partition?

Yes, PowerShell provides another interface, but it does not necessarily overcome an unmovable file. First inspect the supported range:

Get-PartitionSupportedSize -DriveLetter C

Then specify the desired final partition size:

Resize-Partition -DriveLetter C -Size 200GB

This difference is important: DiskPart’s shrink desired=51200 means “remove 51,200 MB,” while PowerShell’s -Size 200GB means “make the final partition 200 GB.” The Storage module’s supported-size calculation can still reflect the same file-system limits. Do not use PowerShell as a supposed force option.

Use a bootable partition tool only when Windows cannot safely do the job

An offline partition environment can sometimes move files or partitions that a live Windows volume cannot. GParted Live is an official bootable option for resizing, copying, and moving partitions, but its download page warns that partition editing can cause data loss and recommends backing up first. Check the official GParted news page for the current release instead of relying on an old version number.

Commercial partition managers are another category, not an automatic guarantee of safety. Before using any bootable or third-party tool:

• make a full image backup and verify that it can be restored;
• save and test access to the BitLocker recovery key;
• confirm that the tool supports the actual file system, partition style, encryption state, and Windows build;
• connect a laptop to AC power;
• create a Windows recovery USB or have installation media available;
• do not interrupt a partition move or resize;
• read the tool’s handling instructions for BitLocker and mounted volumes.

Suspending BitLocker is not the same as decrypting the drive. Suspension leaves the data encrypted and is normally preferable to full decryption for a short, planned operation, but an offline tool must still support the encrypted volume appropriately.

BitLocker precautions for an offline operation

Partition-table changes can trigger BitLocker recovery. Before using third-party or bootable software:

1. Confirm that the recovery key is backed up.
2. Check status with manage-bde -status.
3. In an elevated PowerShell window, suspend protection if appropriate:

Suspend-BitLocker -MountPoint 'C:' -RebootCount 1

After the operation, verify that protection has resumed. If necessary, resume it with:

Resume-BitLocker -MountPoint 'C:'

Follow the tool and Microsoft BitLocker guidance for the specific Windows edition and operation. Suspending protection reduces the chance of a planned change immediately triggering recovery; it does not replace the recovery key or a backup.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

When backup, recreate, or reimage is safer

Non-system data volume

For a data-only volume that refuses to shrink, the conservative alternative is often:

1. Copy or image the data to another disk.
2. Verify the copy or perform a test restore.
3. Delete the original volume.
4. Create the desired partition layout.
5. Restore the data.

This avoids moving locked metadata in place, but it requires enough temporary storage and a verified restore. Do not use this procedure for a system volume unless you have a complete, tested recovery plan.

Operating-system volume

If C: cannot be reduced after diagnostics and file-system repair, consider a full-disk image or migration to a correctly sized disk instead of repeatedly forcing an in-place resize. It takes more preparation, but it may be safer than manipulating a difficult system partition.

After the shrink: use the unallocated space and restore settings

When the resize succeeds, Disk Management displays unallocated space after the reduced volume.

• To create a Windows partition, right-click the unallocated region and choose New Simple Volume.
• If a Linux installer needs raw unallocated space, leave it unallocated rather than formatting it as a new Windows volume.
• To extend an existing basic volume, the unallocated space must be on the same physical disk and immediately after that volume. An intervening partition prevents the built-in Extend Volume operation.

For example, shrinking D: in a layout such as [C:] [D:] [Unallocated] does not normally make the unallocated space usable by C:. It would need to be directly after C:, as in [C:] [Unallocated]. Moving D: requires a suitable partition tool or a backup-delete-recreate plan.

Post-resize checklist

• Restore a system-managed paging file on the preferred volume and restart.
• Re-enable hibernation with powercfg.exe /hibernate on if it was previously enabled.
• Re-enable System Protection, configure its storage limit, and create a fresh restore point.
• Verify BitLocker status and resume protection if it remains suspended.
• Confirm the expected disk sizes, drive letters, labels, and unallocated space in Disk Management.
• Restart Windows normally and open files and applications from the resized volume.
• Check that the computer boots normally before deleting any backup.

Quick decision guide

What you find	Best next action	Important trade-off
The offered shrink is close to the target	Use Disk Management directly.	Normal partition-change risk remains; keep the backup.
Event 259 names pagefile.sys	Move or temporarily disable the paging file, restart, and retry.	Virtual-memory and crash-dump behavior changes temporarily.
Event 259 names shadow-copy storage	Disable System Protection or relocate shadow storage only after deciding what recovery data can be lost.	Existing restore points or shadow copies may disappear.
Event 259 names hiberfil.sys	Run powercfg.exe /hibernate off, restart, and retry.	Hibernate and hybrid sleep become unavailable temporarily.
Ordinary fragmentation is the limitation	Use Optimize Drives or defrag C: /X once.	Protected files and metadata may remain unmoved; SSDs are optimized differently.
CHKDSK reports errors	Back up and repair the file system before resizing.	Repair may require a restart and does not fix a failing physical disk.
NTFS metadata remains at the boundary	Use a verified image/restore plan or a trusted offline tool.	More complexity and higher operational risk.
Bad clusters are present	Back up, investigate disk health, move data, and plan disk replacement.	This is a storage-failure problem, not an ordinary resize problem.
Unallocated space is not beside the volume to extend	Move the intervening partition or recreate the layout from a backup.	Moving partitions is riskier than simple shrinking.

Frequently Asked Questions

Why can I shrink only a few gigabytes when the partition has hundreds of gigabytes free?

Disk Management shrinks from the end of the volume. Free space elsewhere does not help if an unmovable file or NTFS structure is near the trailing boundary. Check the Application log for the defrag shrink event, especially Event ID 259, to identify the limiting item.

Does DiskPart bypass Disk Management’s unmovable-file limitation?

No. DiskPart is an alternate interface with useful controls such as querymax, desired, and minimum, but it uses the same Windows file-system constraints. It may report the same minimum size.

Will temporarily disabling the paging file damage Windows?

It is not recommended as a permanent configuration, particularly on systems with limited RAM or memory-intensive applications. If it is the diagnosed blocker, move it to another suitable volume when possible, disable it only for the resize, restart, and restore a system-managed paging file afterward.

Does disabling hibernation delete my personal files?

No. powercfg.exe /hibernate off removes the hibernation file and disables hibernation and hybrid sleep; it does not delete ordinary personal files. Restore the feature with powercfg.exe /hibernate on after resizing.

Will deleting restore points delete my documents?

It does not normally delete personal documents, but it removes the restore points and shadow copies that could help recover from a bad update, driver, or application installation. Use System Protection or documented VSS commands rather than deleting System Volume Information manually.

Can an SSD be shrunk, or is this only an HDD problem?

SSDs can be shrunk, but the limitation still applies. Windows is dealing with logical cluster and volume placement, not only the physical geometry of a mechanical disk. SSD optimization does not guarantee that protected files or NTFS metadata can be relocated.

Why is Extend Volume greyed out after I shrink another partition?

Windows generally requires unallocated space to be immediately after the volume you want to extend and on the same physical disk. Shrinking D: usually produces space after D:, so it is not directly usable for C: when D: remains between C: and the unallocated region.

What if Event 259 names $UsnJrnl, $Bitmap, or $MFT?

These are NTFS metadata structures, not ordinary files to delete. Do not edit them manually. After a backup and file-system check, consider a trusted offline partition tool or a backup-delete-recreate/restore plan.

Should I use a third-party partition manager?

Use one only after a verified backup and after checking its support for your file system, partition layout, encryption, and Windows build. An offline tool may move data that live Windows cannot, but it can still cause data loss or boot and BitLocker-recovery problems if interrupted or used incorrectly.

The Bottom Line

Bottom line: The warning means Windows has reached an unmovable file or file-system boundary at the end of the volume—not necessarily that the volume lacks free space. Make a backup, use Event Viewer event 259 and fsutil volume querycluster to find the blocker, apply only the targeted temporary fix, and retry after restarting. If NTFS metadata, corruption, bad clusters, or partition adjacency remains the problem, stop forcing the live resize and use a verified recovery plan or a carefully prepared offline tool.