Every day I'm at my desk working away when my CPU fan takes off like an airplane. When I check my running processes it's almost always the Disk Space Cleanup Manager and today it was using 19% of my CPU. It only lasts a couple minutes but I'd still rather completely disable it.

I disabled the "SilentCleanup" task in Task Scheduler, which is set to run cleanmgr.exe /autoclean /d %systemdrive% but that didn't seem to help.

Other ideas?

4/20/2016 enter image description here

  • Have you tried to delete the task? – Ramhound Mar 2 '16 at 18:12
  • Wouldn't that effectively be the same? (Except with no possibility to revert) – Scott Beeson Mar 2 '16 at 18:12
  • How much effort is it to create the task again? – Ramhound Mar 2 '16 at 18:34
  • Irrelevant if there's no effective difference between deleting the task and disabling it, which I believe is the case. If you present otherwise then I'd be willing to note all the details of the task and delete it (or rename it)... – Scott Beeson Mar 2 '16 at 18:36
  • 1
    How much free disk space do you have? – harrymc Apr 20 '16 at 17:52

Disk Space Cleanup Manager has two auto-starting tasks.

1 : SilentCleanup (which you already disabled from task scheduler)

2 : StartComponentCleanup

In order to disable StartComponentCleanup, go to Task Scheduler and then navigate to \Microsoft\Windows\Servicing. Now you can disable for delete this task as you wish.

P.S : I would suggest you to delete these auto-starting tasks. They can be manually started when required by using the Disk Cleanup utility or by executing this command as administrator.

DISM.exe /online /Cleanup-Image /StartComponentCleanup

  • I checked the StartComponentCleanup schedule and the last run result (last night) was "The component store has been corrupted. (0x80073712)". I have disabled it. I'll find out at 12:06 if this fixes my issue. But this is more evidence I need to repair or reinstall Windows. – Scott Beeson Apr 27 '16 at 12:50
  • Turns out this didn't fix the issue. It happened again at 12:06 today. I just finished taking ownership of and deleting 5 instances of cleanmgr.exe on my PC. – Scott Beeson Apr 28 '16 at 17:16
  • @Devil'sAdvocate: You have a Windows computer where sfc doesn't function and the component store has been corrupted, and your solution is to delete cleanmgr - a useful component of Windows? You are just extending the destruction of your Windows setup. – harrymc May 1 '16 at 18:10

You say you have "couple bad sectors on my SSD". This is what the Crucial article My SSD has bad sectors has to say :


My SSD has a lot of bad sectors. Do I need to replace it?


With a traditional hard drive, that is often the case, but with an SSD things are a bit different. Due to the nature of flash technology it's normal to have a small number of bad sectors on an SSD, and as long as the number of bad sectors remains constant there is no reason for concern.

The easiest way to keep track of the number of bad sectors on an SSD is to run ChkDsk.

If the number of bad sectors remains the same, all is well.

I would keep an eye on this SSD, before a catastrophic error occurs, and ensure having good backups at all times.

Since sfc /scannow was unable to complete, it seems that your Windows installation has suffered some damage. I would therefore counsel :

  1. In registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCac‌​hes, see if you have an item named StateFlags00n. These flags control the execution of cleanmgr. If you do, export a copy of the key and delete this item(s). Reboot to be sure it is effective.
    If this does not help or the flag is absent, continue on in this list.
  2. Run chkdsk to flag all bad sectors
  3. Do a Repair Install of Windows. This in-place upgrade install will fix your currently installed Windows 8 without losing anything. Use a recent enough version of Windows 8 installation media.
  4. If Repair Install fails, you would need to reset or refresh Windows, which would unfortunately mean losing data and installed applications.

Before taking the last two steps, just in case you end up by destroying your setup, take an image backup and do not place it on the system drive. Use for example AOMEI Backupper System Backup (and have it verify the backup). Create first a Windows PE & Linux Bootable Disc. Try the boot disc/usb before starting, to verify that it can detect both the system disk and the backup file.

  • 1. Did that. 2 & 3. I've known about the bad sectors for a couple months. Everything else on my machine is running great. So great, that I don't want to risk screwing it up by doing a repair or reinstall. Either way, do you think the disk cleanup issue could be related somehow? – Scott Beeson Apr 21 '16 at 13:24
  • If sfc fails, then everything only seems to be running great. When there is a corruption, everything can be related. I have added above information on how to ensure that you can always fall back to your current setup. – harrymc Apr 21 '16 at 13:37
  • I tried using Clonezilla when this all first started. It failed. I feel like I'm driving across the desert in a Lamborghini with a dead battery and no alternator. I'm doing great but if it does stop I'm screwed. – Scott Beeson Apr 21 '16 at 13:41
  • Sell your Lamborghini and buy a thousand new disks. AOMEI is much friendlier and sure than Clonezilla and is what I use. It has saved me more than once. If you need more help, just ask. – harrymc Apr 21 '16 at 13:45
  • 1
    While you are studying this tool and trying it out, you can wait a few days to see if someone else comes up with a less-dangerous answer. General remark: I always image the disk before doing Windows Update, after I once couldn't reboot since it rendered my Windows unbootable. – harrymc Apr 21 '16 at 13:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.