News, tips, advice, support for Windows, Office, PCs & more
Home icon Home icon Home icon Email icon RSS icon

We're community supported and proud of it!

  • Patch Tuesday for Win7 and 8.1 brings order – but it’s still too early to install

    Posted on December 15th, 2016 at 06:54 Comment on the AskWoody Lounge

    I still haven’t seen any reports of bad patches – but the Security Bulletin numbering system and especially the .NET patches are mighty confusing.

    InfoWorld Woody on Windows

    UPDATE from poster SteveK:

    lots of machines on our w10 1000 +/- computer network choking on what appears to be KB3206632. Partially installs then IP errors occur, and computer can no longer obtain valid IP address to be on network. Can shutdown, reboot etc. multiple times and it does not install. One did finish today after 5 restarts and we were able to see that it was the update that was holding IP up. No idea why it decided to install on that 5th or 6th restart. Our current strategy is to reimage but as the numbers increase we can’t keep doing this. Not yet able to determine why some will install KB3206632 when rebooted and others will never finish installing it.

    Anybody else seeing that?

    ANOTHER UPDATE from Abbodi. For those of you trying to figure out why there’s a Security-only patch for one version of .NET, but a Monthly Rollup for all versions, there’s an elephant in the room. “Both .NET 4.6.2 updates are identical it seems they created the security-only update just to comfort the non-security haters. Apparently they didn’t feel the same or have the time to do that with other .NET versions.”