It is still not clear why the Convenience Update is not made more official by posting it on Windows Update to have a single baseline and not two baselines, as there are differences in the final outcome between the two ways of updating with and without the Convenience Update. A possible explanation may be that the Convenience Update was put together by a different group within Microsoft, which comes from the PFE side and not from the product group. The wording and names of the engineering teams might be slightly incorrect, but you get the idea.
I think he does. It's just that he said "telemetry crap", as in "even more than what's already in there".
WER has always been completely disabled and cut off on all my PCs, since the early XP times. So has CEIP. Dealing with that for a long time now. By "Telemetry crap", which indeed implies "more than already was there", I mean the new era of Telemetry, the one that you cannot simply refuse without digging into the bowels of Windows. We know how to do that, casual users won't. Why should I get the offender onto my PC, only to have to deal with it afterwards? It's already in the name of the beast: Convenience. It isn't a requirement and should never be. More convenience for you means, you need to rely on others. They might screw you over, and MS has a well-known track record of screwing people's PCs, don't they? Personally, I prefer to manage my machines by myself. YMMV.
Yes, valid for normal offline integration unless you want to use W7UI or NTLite which have workarounds to integrate 3177467 offline
https://forums.mydigitallife.net/threads/windows-7-hotfix-repository.19461/page-511#post-1413957 change KB2533552 to KB3177467 and 6.1.1.1 to 6.1.2.5
Do i still need KB3020369 if i apply your script and if everything goes well with that script ? Thank you Abbodi
Master abbodi1406, Thank you so much for continuously updating the update list for Windows 10, 8.1, 7, Office 2016 and so on, which is highly appreciated. Just to confirm, we do not need to install KB4019990, after installing KB4470641 and KB4471318, right? Thank you for your confirmation.
KB4019990 is related to .NET 4.7.2 (KB4470640) it's already included in Monthly Rollup (KB4471318) but WU will still request it so, it's needed anyway
Master abbodi1406, Alright, thank you very much for your confirmation and information. So, it is sort of minor slip up of Windows Update which does not recognizes that KB4019990 is included in KB4471318, and as such, KB4019990 is redundant. For sure, we all trust you, more than we trust Windows Update. Keep up the good work in updating your update lists.