The tool Microsoft provides to patch entire networks, WSUS (Windows Server Update Services) ended up causing more issues than it fixed this week.
Despite the fact that many administrators had configured WSUS not to install new applications, the service silently installed Windows Desktop Search, which horribly slowed down many workstations.
Internet Explorer 7 is back, having been missing in action after the IE team announced that WGA testing was being removed from the IE 7 download.
In other post-Patch Tuesday news, Sun Java starts advertising Open Office, and I revisit my misgivings about the recent Outlook Express patch.
A pretty bumpy patch has just been released for SharePoint, but the rest of this week’s patch lineup is pretty tame.
We do have a few tricky issues to deal with, regarding updates for IE 7, Office 2003, and Vista, in addition to the other monthly security patches.
Office 2003 Service Pack 3 is out, bringing the security of Office 2007 to the 2003 platform.
But, at the same time, there are a few “gotchas” with Office 2003 SP3 that you need to look out for.
Windows Genuine Advantage: now more genuinely annoying for genuine
users of Vista.
A software failure at Microsoft over the weekend falsely branded
thousands of legitimate users’ PCs as “nongenuine” and restricted
Microsoft ranks 6 of the 9 patches released on Aug. 14 as “Critical,”
and only 3 as “Important” — but I’m rating all 9 of them as critical
if you use the platforms that are affected.
We must patch once again for three XML, GDI, and VML threats, along with the
usual Malicious Software Removal Tool updates and a new fix for 64-bit
As we start our back-to-school time of the year, many
of you are purchasing Vista machines.
Vista handles patching just a little bit differently than the older versions of
Windows, and I’ll tell you how.
Let’s review one more time the issues we’ve seen with Microsoft’s
July 10 .NET patches
Hopefully, this will give you a bit more guidance to help you
get your systems patched.
Installation of the .NET patches distributed Microsoft on July 10
has caused many of you hours of frustration.
I’m focusing today on the problems surrounding the .NET updates
that all of us have faced so far this month.