Disk Cleanup seems to be broken

djdelarosa25 · 14 Feb 2018

The newest update did not fix this issue, unfortunately

MeAndMyComputer · 14 Feb 2018

djdelarosa25 said:

I hope this gets fixed soon. My OCD is killing me

What is OCD?

stealth2920 · 14 Feb 2018

MeAndMyComputer said:

What is OCD?

Obsessive Compulsive Disorder. I have it too.

MeAndMyComputer · 14 Feb 2018

djdelarosa25 said:

No, it's not that it doesn't delete everything. It's because it doesn't seem to delete ANYTHING at all.

Please see the screenshot that I uploaded to know what I'm talking about. Everytime I run Disk Cleanup, it always shows 76.9 MB worth of files to be deleted, even if I repeatedly do so.

I usually wait until the end of the month to run disk cleanup as part of my monthly maintenance plan. Well I couldn't to see what happens: and lo & behold: My system is doing the same as yours.

Bree · 14 Feb 2018

Bree said:

There is a known bug with the latest cumulative update KB4058258 Windows 10 v1709 Build 16299.214 in that 46MB is left behind however you try to clean up. It's not a problem in Disk Clean up, the same thing happens if you use the command:
Dism.exe /online /Cleanup-Image /StartComponentCleanup
The problem appears to be in the windows update files themselves. This problem will likely go away after the next update comes out this Tuesday.

See post #72: Cumulative Update KB4058258 Windows 10 v1709 Build 16299.214 - Jan. 31

It didn't fix it. after installing KB4074588, build 16299.248 and running Disk Clean up the 46MB is still there.

It seems the only way to clear the '46MB Windows Update Clean-up' is is to completely remove all the 'problem' update files that came with KB4058258. There appears to be a mismatch in the files and their manifest that prevents Disk Clean up or DISM from removing some older superseded updates.

The only way I've found to remove all references to the KB4058258 update is to do an in-place repair install. This puts you back to build 16299.15.

Repair Install Windows 10 with an In-place Upgrade
Then check for updates and go directly to build 16299.248 with KB4074588. After this, both Disk Clean up and DISM's StartComponentCleanup option seem to work normally again.

It can take a long time, so only worth doing if your OCD can't stand seeing the 46MB in Windows Update Clean-up :)

MeAndMyComputer · 14 Feb 2018

Bree said:

It can take a long time, so only worth doing if your OCD can't stand seeing the 46MB in Windows Update Clean-up :)

I'm leaving mine as is. I just did what I did out of curiosity. It doesn't affect my computers performance.

Bree · 15 Feb 2018

MeAndMyComputer said:

I'm leaving mine as is. I just did what I did out of curiosity. It doesn't affect my computers performance.

Well, for the benefit of others I experimented to find a solution. It's a time consuming fix, but my OCD is satisfied now. It wasn't the 46MB that worried me, but the fact that DISM's StartComponentCleanup aborted at 20%.

MeAndMyComputer · 15 Feb 2018

Bree said:

Well, for the benefit of others I experimented to find a solution. It's a time consuming fix, but my OCD is satisfied now. It wasn't the 46MB that worried me, but the fact that DISM's StartComponentCleanup aborted at 20%.

Thanks for that information. I did that DISM StartComponentCleanup and a couple of other DISM tests as part of my experiment also. In my case it was out of curiosity as I would not have any idea of what to do if a problem would have been reported. If a problem would have been reported I would have asked for help on what to do. On the 45MB threshold, my computer was at 52MB and fortunately I don't have a problem with that.