How long disk cleanup should take

Seems to be spending a lot of time especially on Windows Update Cleanup. Can't quite understand why deleting files should be such an intensive activity. Especially since it already spent quite a lot of time calculating what it could delete. Windows compresses the WinSxS folder by removing replaced updates ad compressing files which can't be uninstalled and which are not used into diffs.

Please note i rebooted onto Linux SystemRescueCd just to be able to list all files, also the ones looked by Window and also to do such listing as fast as possible no acl check, etc. Also please note that on cleanmgr i only count only time after search ends the search itself also tooks more than six hours. So deleting the files is not the botle neck the delete itself only need five minutes but cleanmgr takes more than eight hours. Yes, if i put the virtual disk totally on RAM, cleanmgr time does not drop but if i manaully delete the files, that time drops down just a little Linux write cache is great when you have 64GiB of RAM on it.

I am afraid that cleanmgr is doing something on the windows registry per each file it deletes accessing the registry is very low. So clearly cleanmgr is doing a lot of undetectable work, maybe sleep times? It can take as much as two or three seconds per operation, and if it does one operation per file, it can take near one hour per each thousand of files So definitly cleanmgr time is not caused by the deletion it self! What else is it doing? One way to mitigate this problem and speed up the "Windows Update Cleanup" phase of "Disk Cleanup" a bit is to temporarily set a higher priority for the TiWorker.

For 'Set Priority," choose "Above Normal. Aside from the miniscule speedup--and possibly good feeling of accomplishment--this provides, there's little that can be done since apparently "Windows Update Cleanup" is coded in a way that, for some unknown reason, proceeds file-by-file, making the overall work horribly disk-bound. And also, do know that the process is most probably not hung, and will indeed complete someday.

To verify this and to yet further distract yourself during this annoying wait time , you can check the 'Disk Activity' section of Resource Monitor run "resmon. Deleting 20 files of 5mb in size will take more time to delete than 10 files of 64mb in size. This is because when system deletes files, it doesn't really delete them as empty space on a drive can be made of "noise" bits but just overwrites the front part that says, "A file starts here" with gibberish and then it will happily overwrite that and the following parts later when you want to use the space.

Running Disk Cleanup at least once a month is an excellent maintenance task and frequency. Skip to content Android Windows Linux Apple. Home » Windows. See also How do I remove password protection from Windows 10? See also How do I reset my display color on Windows 10? See also How do I setup a wireless peer to peer network on Windows 10? Related posts: How long should Disk Cleanup take Windows 10?

You will especially notice a difference when searching for files. Disk Cleanup helps free up space on your hard disk, creating improved system performance. Disk Cleanup searches your disk and then shows you temporary files, Internet cache files, and unnecessary program files that you can safely delete. You can direct Disk Cleanup to delete some or all of those files. If Windows Update cleanup is stuck or takes forever to run, after a while click on Cancel.

The dialog box will close. Now run Disk Cleanup Tool again as administrator. But the special command line above bypasses both the day grace period and the 1-hour timeout. Unreferenced components are removed immediately, and the task will run to completion, even if it takes more than an hour. Comments are closed. Well dang, I was running the cleanup tool manually because I knew it uses quite some CPU and wanted it to get it over with on my schedule rather than random system schedule.

Guess I should stop doing that.