Well, it cleared 15 gigs... that's not quite the 21.1 gigs plus the misc smaller chunks that the Disk Cleanup said it would open (nor the 30 gigs that I've seen purged by itself a few times in the last year)... but it's still pretty good.
I can see that my Temp folder at User>AppData>Local>Temp
is virtually empty now.
Do you know where this second Temporary folder is?... or was the Disk Cleanup panel just referring to the one that I have at User>AppData>Local>Temp.
Maybe Disk Cleanup said it had 21.1 gigs when the system only showed that it had 9.8 gigs via the normal directory info, but then somehow it opened about 15 gigs when the actual Disk Cleanup process was run... but the other smaller chunks removed in other areas didn't nearly equal 5 gigs... only about 800 megs.
I dunno... anyway, thanks.
I've never manually deleted temp files before, so this is my first experience getting in to Disk Cleanup, though I have everything else set to run automatically, like defragment, malware sweeps, antivirus, etc. Since I've never deleted temp files before, and that's what my post is basically asking about, asking me why they would be needed is a bit pointless, right? You tell me, why are they needed?... is one supposed to manually delete temp files after every restart in Windows 7?
Someone else has referred me to a page about setting up automatic Disk Cleanups via the Command Line... here's that link... How to configure automatic Disk Cleanup in Windows 7
I know there are allot of funky things that happen in Windows when left at default settings. I had a prior experience where I finally investigated what seemed to be a constant drain on my processor, always running at about 75 percent according to two different desktop CPU usage gadgets. I discovered that some Windows Media Player network sharing service was constantly running my processor at 75 percent, never stopping until I figured it out and turned it off... then it came back after the next restart and I had to disable it completely.
That WMP network sharing service was completely useless and performing no service for me (completely indescribable by Microsoft forums people), yet it was set to put a constant 75 percent drain on the processor, 24 hours a day.