ComputerWorld

In what is becoming a common occurrence, Microsoft’s Patch Tuesday brought along so many bugs that they necessitated a remediation round. This month, unusually, it took only six days to get the exterminators out.

Since these fixes are aimed at four specific bugs introduced on Patch Tuesday, they don’t include the massive patches normally appearing on the second Patch Whateverday of the month. My guess is we’ll see at least one more big set of Windows patches before the month is out. Oh, boy.

Windows July patches, version 2

Yesterday, Monday, July 16, Microsoft released 27 new security patches for Windows, bringing the total number of patches so far this month up to 156. The new patches fall into six separate groups:

To read this article in full, please click here

You know it’s going to be an Alice in Wonderland month when some sites report that Microsoft plugged 54 vulnerabilities on Patch Tuesday, while others report 53. Fact is, patching has become so brutal — and so banal — that there’s no consensus on counting, much less on what’s good and bad.

Suffice to say that, once again this month, there was a huge number of security patches (129 individual patches, according to the Microsoft Update Catalog), with no pressing security fixes unless you’re using the Edge browser or Internet Explorer. Microsoft changed Win10 version 1803 to “Semi-Annual Channel,” but the term now means less than it ever has before. If that’s possible.

To read this article in full, please click here

Windows 7 customers should be on the lookout for a couple of, uh, challenges this month, as the Win10 1803 trail of tears continues and Win10 1709 finally looks pretty solid.

The Win7/Server 2008R2 network card bugs continue

First, the good news. If you installed last month’s Win7/Server 2008R2 patches and your network connections didn’t go kablooey, you’re almost undoubtedly OK to proceed with this month’s patches.

On the other hand, if you’ve been waiting to install patches on your Win7 or Server 2008R2 machine, you need to be aware of a bug that Microsoft has acknowledged. It was introduced by a patch back in March, according to the KB articles, and hasn’t been fixed yet:

To read this article in full, please click here