Believe it or not, I was going to mention the Update Client patch, based on a discussion we had a few months ago about the same thing. We established that I had/have a later version of the Update Client than yourself, with reference to tie-ins with Windows 10 nagware. - Coldheart2236
Yes, I'm running version 7.6.7600.320 of the Windows Update client. And that is really all you need. Even today my WindowsUpdate.log reads:
2016-06-21 07:21:08:269 464 1210 Setup SelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320
2016-06-21 07:21:08:363 464 1210 Setup SelfUpdate check completed. SelfUpdate is NOT required.
So any later versions of the Windows Update client are primarily designed to install Windows 10.
That said, with KB3161647, it seems fairly innocuous - aside from the ambiguous "Some reliability improvements" which is what makes me reticent of installing the roll-up in the first place. - Coldheart2236
Don't forget that the infamous GWX update KB3035583 was originally released with the innocuous description of "additional capabilities for Windows Update notifications when new updates are available."
I'm going to wait it out to see if anything dodgy is packaged in there, but either way it's by no means a critical update and I can't see it causing me any issues if I ignore it. - Coldheart2236
According to Woody Leonhard's site, KB3161647 is "an official fix for slow Windows 7 update scan times": http://www.askwoody.com/2016/an-official-fix-for-slow-windows-7-update-scan-times/
However, I don't have that particular problem. It seems to be a bug introduced in one of the previous latter-day Windows Update Clients. So if I don't have the problem, I'm not going to install the fix. Especially since there could be some dodgy Windows 10 stuff in there too.
reply
share