[Solved] Cannot shrink a volume beyond the point where any unmovable files are located

"You cannot shrink a volume beyond the point where any unmovable files are located" means Disk Management can only cut free space off the end of the volume, up to the last file Windows cannot move. Usually that is the paging file, the hibernation file or System Restore's shadow copies. Find the blocking file in event 259 first, turn that feature off for the shrink, then turn it back on.

Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What "You cannot shrink a volume beyond the point where any unmovable files are located" means

The full text in the Shrink dialog reads: "You cannot shrink a volume beyond the point where any unmovable files are located. See the "defrag" event in the application log for detailed information about the operation when it has completed." The old version of this page said you see it only in Event Viewer. In fact it is the note in the dialog itself, and the details go to the log.

Microsoft explains the rule: when you shrink a partition, ordinary files are moved automatically to make new unallocated space at the end of the volume. Certain files, such as the paging file or the shadow copy storage area, cannot be moved, and you cannot shrink past the point where they sit. So a 2 TB drive with 1.5 TB free may still offer only a few gigabytes.

What prevents a volume from shrinking in Windows 11 and 10: causes in order

Most often the paging file pagefile.sys sits near the end of C:. Often the shadow copies of System Restore, stored in System Volume Information, or the hibernation file hiberfil.sys do. Less often NTFS's own files such as $MFT are the last ones. Rarely the disk has too many bad clusters, and then Microsoft says it cannot be shrunk at all.

How to fix "You cannot shrink a volume beyond the point where any unmovable files are located"

Fix 1 tells you which file stops the shrink, so you change only what you must. Fixes 2 to 4 turn off the three usual blockers for a short time. Fix 5 runs the shrink and turns everything back on. Fixes 6 and 7 are for when the limit stays low.

Fix 1. Find the unmovable file in event 259 of the Application log

5 minutesNo riskEveryone, before changing any setting.

Microsoft's own advice when a shrink stops early is to check the Application log for event ID 259, which gives information about the unmovable file. It tells you which of Fixes 2, 3 or 4 you need, so you do not switch off features for nothing.

1. Try the shrink once: right-click Start, open Disk Management, right-click the volume and select Shrink Volume. Close the dialog when it shows the size.
2. Right-click Start and open Event Viewer.
3. Go to Windows Logs > Application.
4. Select Filter Current Log in the right pane, type 259 in the event ID box and select OK.
5. Open the newest event with the source Defrag and read the file it names as the last unmovable file, and the cluster number.
6. Match the file to the chooser table above and go to that fix.

If the event gives a cluster number but you want to check which file uses it, Microsoft's fsutil tool answers that. Run it in Terminal (Admin) with your drive letter and the cluster number from the event.

Find the file that uses a cluster (Command Prompt or Terminal as administrator)

fsutil volume querycluster C: 0x2000

Fix 2. Turn off hibernation for the shrink

2 minutesLow riskEvent 259 names \hiberfil.sys, or you use a laptop with hibernation on.

The hibernation file hiberfil.sys is a large file on C: that Windows keeps open, so it does not move. Microsoft's powercfg /hibernate off command disables the hibernate feature, and the file goes away with it.

1. Select Start, type cmd, right-click Command Prompt and select Run as administrator. Select Yes in User Account Control.
2. Run the command below.
3. Restart the PC before you shrink.

Turn off hibernation (Command Prompt as administrator)

powercfg /hibernate off

Fix 3. Set no paging file on the volume and restart

5 minutes plus a restartLow riskEvent 259 names \pagefile.sys. This is the most common case on C:.

Microsoft names the paging file as one of the files a shrink cannot relocate. It also suggests moving it to another disk for the shrink and moving it back afterwards, which removes pagefile.sys from the volume.

1. Press Win + R, type SystemPropertiesAdvanced.exe and press Enter.
2. Under Performance, select Settings, open the Advanced tab, and under Virtual memory select Change.
3. Clear Automatically manage paging file size for all drives.
4. Select the drive you want to shrink, select No paging file and select Set. Confirm the warning with Yes.
5. If you have a second internal drive, select it, choose System managed size and select Set, so Windows still has a paging file.
6. Select OK in each window and restart the PC.

Fix 4. Turn off System Protection on the volume to remove shadow copies

5 minutesRead the warningEvent 259 names a file in \System Volume Information.

Restore points are kept as shadow copies, and Microsoft names the shadow copy storage area as unmovable. Microsoft's way out is to delete the stored shadow copies before the shrink, and turning off System Protection does that.

1. Press Win + R, type SystemPropertiesProtection.exe and press Enter. On Windows 11 you can also open Settings > System > About > System protection.
2. Under Protection Settings, select the drive you want to shrink and select Configure.
3. Select Disable system protection, then Apply, and confirm with Yes.
4. Select OK twice.

Fix 5. Restart, shrink the volume, then turn every feature back on

10 minutes plus a restartLow riskYou turned off the blocker in Fix 2, 3 or 4.

The paging and hibernation files are released only after a restart. Once they are gone, Windows can move the ordinary files and offer the space up to the next unmovable file.

1. Restart the PC.
2. Open Disk Management, right-click the volume and select Shrink Volume.
3. Enter the amount in MB in Enter the amount of space to shrink in MB and select Shrink.
4. Turn hibernation back on with powercfg /hibernate on if you turned it off.
5. Set the paging file back to Automatically manage paging file size for all drives if you changed it.
6. Turn System protection back on for the drive and create a restore point.
7. Restart once more.

You can also shrink from the command line. Microsoft's diskpart shrink takes a desired and a minimum size in MB and never loses data. It stops at the unmovable files on its own.

Shrink with diskpart (Command Prompt as administrator)

diskpart
list volume
select volume 2
shrink desired=200000 minimum=100000

Fix 6. Optimize the drive and try the shrink again

10 minutes to a few hoursNo riskA hard disk, and the offer grows a little each time you try.

Shrink moves ordinary files on its own, but on a crowded hard disk a full optimize first leaves fewer files near the end. On an SSD, Optimize runs a retrim instead, so it rarely changes the shrink size.

1. Select Start, type defrag and open Defragment and Optimize Drives.
2. Select the drive and select Optimize.
3. Wait until Current status shows OK, then try Shrink Volume again.

Fix 7. When NTFS files or bad clusters block the shrink

30 minutes or moreRead the warningEvent 259 names $MFT or another $ file, or the disk has bad sectors.

Files whose names start with $ belong to NTFS itself, and no Windows setting moves them. Microsoft also says that when dynamic bad cluster remapping has found too many bad clusters, the partition cannot be shrunk.

1. Accept a smaller shrink: use the size Disk Management offers now, and plan the new volume around it.
2. Check the disk for errors with chkdsk. Step by step: Check a disk for errors (chkdsk).
3. If chkdsk reports bad sectors, follow Microsoft's advice: copy your files to a new disk and replace the old one.
4. Copy files file by file, not with a sector by sector clone. Microsoft warns that a block level copy also copies the bad sector table to the new disk.
5. To split a drive that cannot shrink enough, back up, delete the volume, and create new volumes of the sizes you want.

If you still cannot shrink the volume

Collect these facts before you ask for help on Microsoft Q&A or from a technician. They show which file blocks the shrink and whether the disk is healthy.

• The text of the newest event 259 (source Defrag) from Windows Logs > Application, with the file name and cluster.
• The size Disk Management offers in Total size available for shrink space in MB, and the free space on the drive.
• Which features you turned off: hibernation, paging file, System Protection.
• Whether the drive is a hard disk or an SSD, from Defragment and Optimize Drives.
• The result of chkdsk C: /scan.
• Your Windows version: press Win + R and type winver.
• When it is hardware: chkdsk reports bad sectors or the shrink offers nothing at all. Microsoft's advice then is to move the data and replace the disk.

How to avoid the unmovable files limit next time

Frequently asked questions

What does "You cannot shrink a volume beyond the point where any unmovable files are located" mean?

It means Disk Management can only remove free space from the end of the volume, up to the last file it cannot move. Microsoft lists the paging file and the shadow copy storage area as such files. The space Windows offers is therefore the free space after that file, not all the free space on the drive. Event 259 in the Application log names the file, and Fixes 2 to 4 on this page turn the usual ones off for the shrink.

What is the "defrag" event in the application log?

It is event ID 259 from the source Defrag in Event Viewer, under Windows Logs > Application. Shrink uses the same engine as the drive optimizer, so the result of the shrink analysis is logged under that name. Microsoft says the event gives information about the unmovable file that is blocking the shrink. Open it after you try a shrink and read the file name and cluster it gives. Fix 1 shows how to filter the log.

Is this different on Windows 11?

No. Windows 11 and Windows 10 use the same Disk Management, the same diskpart and the same rule, and Microsoft's page on shrinking a basic volume applies to both. Only the way to System Protection differs a little: on Windows 11 it is under Settings > System > About > System protection. The SystemPropertiesProtection.exe and SystemPropertiesAdvanced.exe shortcuts in Fixes 3 and 4 open the same windows on both. Windows 10 left support on 14 October 2025.

Which files can prevent a volume from shrinking in Windows 11?

The usual ones are the paging file pagefile.sys, the hibernation file hiberfil.sys and the restore points stored as shadow copies in System Volume Information. Less often NTFS metadata such as $MFT sits near the end of the volume, and Windows cannot move it. Microsoft adds a rarer case: too many bad clusters found by bad cluster remapping stop the shrink altogether. Event 259 tells you which one it is on your PC.

Is it safe to turn off the paging file, hibernation and System Protection?

For the short time of a shrink, yes, with one cost. Turning off System Protection deletes all restore points of that drive. Turning off the paging file can make apps close when memory runs out, so keep large programs closed. Turning off hibernation also turns off fast startup. Turn all three back on as soon as the shrink is done (Fix 5) and create a new restore point.

Can shrinking a volume delete my files?

Microsoft says the shrink operation in diskpart causes no data loss on NTFS volumes, because ordinary files are moved and not deleted. The risk is in what can go wrong during the change, such as a power cut or a failing disk. Microsoft also warns that shrinking a raw partition with data in it, such as a database file, can destroy that data. Back up before any partition change.

Do I need to show hidden files or defragment first?

No. The old version of this page told you to show hidden and protected system files first, but none of the fixes needs that. Event 259 names the file without it. Defragmenting is only worth trying on a hard disk when the shrink size grows a little each time (Fix 6). On an SSD, Optimize runs a retrim and usually does not change the size Windows offers.

Can a third-party partition tool move unmovable files?

Some partition tools work outside of Windows, for example from a boot disk, where the paging and hibernation files are not in use. We did not test them for this guide, so we cannot say which one handles which file. If Windows cannot shrink enough even after Fixes 2 to 4, the safe way without extra tools is to back up, delete the volume and create new volumes of the sizes you want (Fix 7).

What if the search was about Word being unable to shrink something?

This page is about Windows Disk Management and the Shrink Volume dialog. A message such as "after several attempts Word was unable to shrink" most likely comes from Microsoft Word, when it tries to fit a document on fewer pages with Shrink One Page, and has nothing to do with disk partitions. Search for that exact Word message instead. The fixes on this page will not change how Word fits text on a page.