Windows 10: disk cleanup bug??

Disk cleanup says it can free up to 4 TB of space on my 120GB C: drive, after a update. WTF!!!

Even adding the 2TB HDD and another 120 GB SSD (which is 60 GB partitioned) which are far from full, this doesn't make any sense.

Is this some weird bug in Disk Cleanup utility? Is there a explanation for this?
Thanks





:)

 

Disk cleanup

CleanMgr has some basic rules for some of your temp files - need to be older than x days before it would delete some. Plus files that are currently in use it wont delete.

That does seem like an extreme amount of temp files. I would go find where those are located and figure out why so many.

Those few bytes in Temp Internet files are probably just space used by empty dat files and windows default browser things.

You might want to do a web search of disabling prefetch. Prefetch takes about 6 fresh boots to populate, so you might as well disable it. Although I dont why you want to delete those.

You might be interested > Disk Cleanup Cleanmgr Command Line Arguments in Windows 10

 

disk cleanup

Using disk cleanup including previous versions is completely safe to use.

 

This is a known item, and appears after the Anniversary Update to Windows 10. It's related to Windows Update files that are heavily cross-linked on disk, which causes them to be reported as larger than actual size. If you run this Google Search you'll see this item has been widely discussed in the community. It turns out to be about 900 MB of on-disk info, if memory serves, so it's nowhere near as big a thing as it may seem! *Wink
HTH,
--Ed--

 

Are you seeing the same numbers if you go to Settings-System, click on Storage then select the drive you want to check?

 

This is a well-documented problem that goes back to KB3194798. I blogged about it back on October 12, drawing on member Bree's excellent explanation of the issues behind the huge reported size. It has to do with links embedded in the file itself to files all over the WinSxS folder hierarchy. Each instance of the link counts as if it were a file, and the sizes of all the files are summed to report the apparent size of the object. For 64-bit systems (I don't have any 32-bit data, sorry) the actual size is more like 900 MB, not 3.98 or 3.99 TB as is variously reported. It's just an artifact of the internal file structure: it's not the real size of the data blocks involved.
HTH,
--Ed--

 

And it's another example of sloppy software engineering from MS.

 

Many thanks!

I've searched about disk cleanup huge files and found nothing, sorry for posting a known issue *Sad

 

On a different note Derek, are you running some sort of Windows 95 colour scheme there? Looks good!

 

Many thanks! *Smile
Yeah, I always liked the classic Windows 95/98 style, and tried to "emulate" in Windows 10 as far as I could *Smile