That’s because Windows uses this folder for certain system-level features. And this will answers some of the other questions you might have: Change the settings for the drive you are having issues with and specify that it must use "No paging file"ĭoing this should solve the problem.The click on "Change" under "Virtual Memory".Select the drive you are having issues with and click configure.Right click on "This PC" and then "Properties".That file is swop file related and I had to do this for Windows 10: I would not have figured this out by myself. Mine had this to say: The last unmovable file appears to be: System Volume Information::$DATA Take the guess work out of it by just opening the " Event Viewer" and going to Windows Logs then Application and look for entries where Source = Defrag. To remove these, use the following command in an elevated command prompt: Vssadmin delete shadows /For=: /all These turned out to be shadow copies of drives on a 2008R2 server. Once your machine has rebooted and you know you have no page file (check at the root of C: with hidden and system files showing) - try a defrag and then try shrinking the volume again.ĭon't forget to reset your pagefile back to its original size afterwards! Failure to do so will potentially cause significant performance issues with any machine.ĮDIT: I have just had to do this on another system which had other unmovable files. Select No paging file, and click the Set button.Un-check Automatically manage paging file size for all drives.Select the Change box under Virtual memory.Select the Advanced tab and then the Performance radio button.Having come across this myself previously on both server and desktop operating systems - I can say the most likely culprit is the pagefile. The most common "unmoveable" files are files which are locked during normal computer operation such as virtual memory/pagefile/system restore files as well as a few other files which may be open, but not running "in memory" The main reason for not being able to shrink the disk are that there are unmovable files on the disk at the time of trying to shrink the volume (as your screenshot says).
0 kommentar(er)
