For some weird reason the pack first tried to integrate the march 2020-03 rollup (KB4540688) before it did integrate the ESU check suppressor (KB4528069), but because that update got installed successfully, the 2020-03 rollup installed fine on the next run. What is weird is that the re-run installed the same updates which were already installed during the first run. The second run should only have installed the missing/failed ones from the first run.
The UpdatePack7R2 works with unpacked updates, sometimes the antivirus starts checking them and interferes with proper operation. I advise you to disable the antivirus while installing updates.
Code: Name: UpdatePack7R2-20.4.15.exe Size: 899906528 bytes (858 MiB) CRC32: 8DF8FA0D SHA1: C23D752F7CA4125875FAC1E03167BF3FEFBA907C SHA256: 9F77E198DFB2EDFD429AA76F6EA5DEF4295B4E85D03AAF53142533B0EF6BAF44 BLAKE2sp: D408ABED3B409DC141F749C42191E298F95FAC73861503259E5CF1EDB6E03AAE
Updatepack 20.4.15 log: https://forums.mydigitallife.net/th...l-wim-esd-creation.79421/page-25#post-1590359
@jim_p, When I update Windows 7 with UpdatePack7 OFFLINE, I always use a clean ISO MSDN ... And all the updates listed in your LOG are integrated into my Win7_Ultimate ... See attached log
Don't you have a Google account like Gmail, etc.? Google all in one account allows 15 GB free data storage limit in google drive & there are other cloud options like Mega, OneDrive, Dropbox, etc. Thanks. ...
Ok... But I am not talking about integration here, I am talking about a regular update from the update pack.
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.