You have KB3125574 installed and ran Disk Cleanup after installation. It is a false detection as some intermediate updates in the supersedence chain for .NET Framework 3.5.1 have been expired by Microsoft and the chain is now incomplete at the metadata level. For cosmetic reasons, you may decide to install the old patches, but the only thing that will happen is to flag Windows Update that they are installed. There is nothing to be installed in fact.
Your pastebin that has the links to the July WU client seems to have expired abbodi. The link redirects to the homepage.
I am showing 3 Updates for Dec. KB3205402 Dec Net Framework Rollup KB3207752 Dec Monthly Rollup KB890830
Hi all. I've been checking December, 2016 Security Monthly Quality Rollup for Windows 7 KB3207752 x64 as per abbodi's tips, and it contains 3075249 (consent.exe telemetry points) and 3968708/3080149 (Unified Telemetry Client). Packages are: - For 3075249 (component "Microsoft-Windows-LUA") package_170_for_kb3207752~31bf3856ad364e35~amd64~~6.1.1.3 (deployed with other "safe" components) (component "Microsoft-Windows-Authentication-AuthUI", not sure about this component, but was present in original 3075249) package_354_for_kb3207752~31bf3856ad364e35~amd64~~6.1.1.3 (alone) package_362_for_kb3207752~31bf3856ad364e35~amd64~~6.1.1.3 (with other) - For 3968708/3080149 (component "Unified-Telemetry-Client") package_567_for_kb3207752~31bf3856ad364e35~amd64~~6.1.1.3 (alone) So UTC could be removed from image by removing package 567 after applying DecRU. However 3075249 would stay. Abbodi has already confirmed several times that 3075249 has no effect if UTC is not present/disabled. If accepting the trade-off, there's no reason to not install JulRU 3172605 which only includes 3075249. It has the added benefit of including WU fix (for those interested). To summarize, an updated Dec 2016 W7 image without effective telemetry is possible as follows: - As per 2016-12-13 WHD repository - Without Convenience RU 3125574 abbodi script (with disabled W10 updates) - Re-added 3140245 (partially superseded update by CRU) - DecRU + package 567 (UTC) removal step There are other ways to avoid 3075249 as well, but they require re-adding a continously growing list of (old) packages superseded/included in 3172605 and most following RUs and also go with the alternative "Security Only" RU way. IMHO the way above is fair enough.
Hello abbodi1406, can you post the KB article link for fixing Windows 7 slow checking for updates again? Much appreciated!
There are several components in Windows 7 SP1 still bearing the 7600.16384 version number. Pretty normal. There are even downlevel files from later OS (mostly from 10). Since the introduction of the SxS (Side by Side) Store, there really aren't that much reasons to check versions manually. DLL hell ended with NT 5.x (XP/2003).
darrianpalmeraeu: It's still relevent. And yes- it checks things at an update level (not individual files), but how else would you update the files?