@abbodi1406 I use KUC W7 UpdateChecker to check for my updates，but it confused me. I have installed the updates from WHDdownloader. KB2900986 is superseded by KB4018271 KB4054176 and KB4054998 need to be installed Why?
@DUT while KB4018271 can be installed without IE8 (to update ActiveXCompat component) but the component has not changed from KB2900986, both add the same registry keys so KB2900986 is good enough with IE11 --- KB4054176 components version 6.1.7601.23990 rollup same components version 6.1.7601.23989 but the actual files under components are the same KB4054998 contain lang resources components but the actual lang files are still the same SP1 files and since WU don't require or offer KB4054998/KB4054176, i consider them not needed
@ch100 I guess those are the rules of Windows Installer (MSI), a separate patch is easier than rebuilding the base product think of it as traditional Office, only a service pack will change the product base version and they don't want to upgrade .NET 4.8 itself
Anyone know what might be causing WU To offer the Update Readiness Tool (KB947821-v34) and KB4592471 (LCU-2020-12) after clean installing a captured wim that includes the latest ESU-Bypass and all updates for December? Prior to running the tool, I ran DISM /Online /Cleanup-Image /ScanHealth and the CheckSUR.log indicated no errors. SFC came up clean too. I did a check for updates several times, but the 2 KBs were still being offered. I went ahead and installed the tool and after the install finished, WU disappeared and no longer was offering anything. The install added a bunch of stuff to [HKEY_LOCAL_MACHINE\Components\ which became non-existent after the install was done. There was nothing else relevant that I could tell that got installed except for the CheckSur dir and an additional registry key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CheckSUR\ I was hoping to find out what may have triggered the offers to avoid going this route again next time. [Solved]
For my test i needed to delete the softwaredistribution folder to be able to get both offered, with ESU Bypass v11 installed in full.
Enthousiast: It occurred in only 1 of my 4 PC's which all have BypassESU-v11 deployed. The Windows Update app in my other 3 PC's detected and installed KB4603002 and KB4601347 fine. I don't know why it occurred in 1 of them. Having to manually install it was no big deal.