From my point of view and for my system, an old core 2 duo with an ssd and 4gb of ram. I mainly use linux and I switch to windows every time I want to use a windows-specific app or update the os. I manually run disk cleanup once every 3-4 months, mainly to get rid of the stuff that wu leaves behind. Most ofthe time I am like "I am gonna do this work and gtfo" and I switch back to linux. The update procedure is the most tedious thing I do on windows, not only because of the time it takes to download and install the updates, but for the waiting I have to do before the reboot and the next start of the os. You know, the "please do not power off your pc. installing update 2 of 10. 15 %. blablabla". On top of that, disk cleanup's most time consuming part is when it scans for the leftovers of wu and when it removes those leftovers. I know this both of these are not your fault but microsoft's. Making it start on the very next boot after the completion of the update pack, as a scheduled task I assume, imho, adds extra time to that tedious procedure. Also, judging from previous times, where it was taking me ~30 minutes to do the update and the mandatory reboot, it took me ~1 hour this time for 11 updates > reboot > 4 updates > reboot > disk cleanup > reboot (I think there was one more reboot somewhere else too). I understand that most of that time is wasted from windows update's procedure than from the cleanup itself, but cleanup took a fair share of 15-20 minutes from that total time! So yes, I would avoid it if I had the way to do it. Thank you for listening.
It's just 2 monthly updates now, a rollup and a ssu afterwards, the disk cleanup doesn't take that long anyway.
I am just mentioning what I saw, because I have no way to time it accurately. If the stuff that the logs report is timestamped, I think it would say the same.
I thought something didn’t work for you after cleaning the disk, but just waiting a bit to get valuable free space should not be a problem. In addition to cleaning the disk, telemetry removal and other service processes are launched, so a reboot is necessary in any case. But if you still don’t need cleaning, just click “Cancel” when it starts.
No, instead, I added other conditions - if the update is quiet or passive or any keys are specified, the update will not be checked.
Yes, for your and other utilities in order to avoid unexpected dialogs during integration or installation process.
I do not understand what your question is, according to the journal you have all the updates installed correctly. You do not need UpdateScan7.log, see only UpdatePack7.log.
@simplix : What a great work, Sir! Many Thanks. @jim_p & ALL : He is the author of this great work. Thank him & take your tips. Thanks. ...
Offtopic. Can someone show me how to quote multiple messages please? I click the "+quote" button on the ones I want, then I click reply but only the last comment is quoted.
UpdatePack7R2-20.4.20.exe CRC32: F15FF483 ED2K: 70D4FA417CAF9B464E921C34AB887FA7 MD5: B6B2C14E5DF540316EE63B4434FCA8FC SHA-1: 42CED646986115DF62651A8D389888C0876790B4 SHA-256: 1F030916E6DE67C52C7F2EE2DFFBAB808748C7FBA520D8DCA69EEBA6AB4C0198