MovieChat Forums > Computers and Software > Windows Update KB3161608

Windows Update KB3161608


June 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 - https://support.microsoft.com/en-us/kb/3161608

The second instalment of the (sort of) service pack, which I've yet to install myself. It does however seem benign, in the sense that it doesn't appear to have anything related to Windows 10 within its 5 component updates.

I'll probably keep an eye out for a couple of days, just to make sure there's nothing untoward going on with this June update.


Wipe your tapes with lightning.

reply

The second installment of the (sort of) service pack, which I've yet to install myself. It does however seem benign, in the sense that it doesn't appear to have anything related to Windows 10 within its 5 component updates. - Coldheart2236

Thanks for the heads-up, Coldheart. This update has not yet been offered to me.

You may have spoken too soon when you said there was nothing Windows 10 related. I note that one of the updates included in the roll-up is:

KB3161647 Windows Update Client for Windows 7 and Windows Server 2008 R2: June 2016
https://support.microsoft.com/en-us/kb/3161647

It's common knowledge that Microsoft has been using newer Windows Update Clients, in collusion with GWX, to install Windows 10 on unsuspecting Windows 7 computers. With the expiration of the free Windows 10 offer in just over a month, who knows what this new Windows Update Client will do?!?

I am definitely not installing this roll-up anytime soon, if ever.

reply

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. 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.

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.


Wipe your tapes with lightning.

reply

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

I'm gonna roll the dice and install it anyhow. Sooner or later, support will end and we will have to eventually switch to a different OS.

reply

As the saying goes, desperate times call for desperate measures. I just installed KB3161608.

After months of happily running version 7.6.7600.320 of the Windows Update client, I finally got hit with the dreaded slow-down bug. And it was as bad as everyone said.

So this is what I did:

1. Changed my Windows Update setting from "Check for updates, but let me choose whether to download or install them" to "Never check for updates".

2. Downloaded the standalone installer for KB3161608 from https://support.microsoft.com/en-us/kb/3161608 and installed it.

3. After the reboot I downloaded GWX Control Panel from http://ultimateoutsider.com/downloads/, installed it, and ran it.

4. I then manually checked for Windows Updates, and the new client really does speed up scans as advertised!

5. I installed the six new security updates and then rebooted again.

6. I ran GWX Control Panel again just to make sure nothing changed.

7. I then changed my Windows Update setting back to "Check for updates, but let me choose whether to download or install them".

So I would recommend KB3161608. It really does speed up the scan for updates. Furthermore, it didn't try to push any Windows 10 crap on me, although GWX Control Panel may have kept it in line. If you are experiencing the slow-down bug, I recommend the procedure above. If your Windows Update isn't too problematic at present, you could wait and install KB3161608 after the Windows 10 offer expires.

FYI. The new client is version 7.6.7601.23453

reply

I also experienced the long scan bug while running v7.6.7600.320 of WU. For some reason, I also had a problem updating Microsoft Security Essentials, so uninstalled it and reinstalled avast! while I was at it.

I've done the same as you, alpha, in installing the standalone .wmu file for KB3161608. GWX Control Panel still reads the same after installation and reboot, so hopefully no further issues while we weather the storm for the next fortnight.


Wipe your tapes with lightning.

reply

I also experienced the long scan bug while running v7.6.7600.320 of WU. I've done the same as you, alpha, in installing the standalone .wmu file for KB3161608. GWX Control Panel still reads the same after installation and reboot, so hopefully no further issues while we weather the storm for the next fortnight. - Coldheart2236

I was hoping I wouldn't need the new client, but yesterday I tried to install updates and the scan took forever. I tried to just let the scan run, but after 90 minutes a thunderstorm roared in and I lost power! 

After the stormed moved through, I broke down and installed KB3161608. So far so good. And I have to say I'm impressed with GWX Control Panel.

reply

This update fried the BIOS so I had to buy a new mobo.

reply

I, too, am experiencing no ill effects from the update.

I first had GWX Control Panel as a standalone exe just to test its analysis against the measures I'd taken - uninstalling and then hiding updates repeatedly, as well as making two changes in the registry to block the OS upgrading to Win10 and the GWX tray icon.

Now I have it installed in the wake of the recent WU problem and subsequent installation of KB3161608, and nothing has changed as of yet.

Still, there's two weeks to go...


Wipe your tapes with lightning.

reply