One of the updates released by Microsoft this week causes some applications using Visual Basic controls to fail.
The short-term solution is to remove the update, but be sure to reinstall it once your VB apps have been corrected.
The lone patch for January addresses three vulnerabilities that some experts claim will be the next big worm event.
While the threat to Windows users may not be quite so dire, be sure to reboot after you install this patch, even though Windows Update may not prompt you to do so.
Please stop your holiday preparations long enough to apply this week’s important security update for Internet Explorer.
While most of the sites that currently host the so-called XML exploit are located in Asia, this attack on IE is likely to spread quickly to other sites, so make sure to update your PCs with this patch before using Microsoft’s browser for anything else.
There’s no fix yet for Tuesday’s remote-code-execution exploit, which has already been found circulating in the wild.
Windows users should switch to a browser other than Internet Explorer until Microsoft releases a patch for this IE security hole.
A vulnerability that allows remote-code execution via the Server Message Block protocol has long been known to affect all Windows PCs and servers.
This week, Microsoft finally found a way to fix the problem, first described in 2001.
A remote-code exploit that could spread rapidly like the 2003 MSBlaster worm is putting all versions of Windows at risk.
I recommend that you immediately install a patch that Microsoft has just issued to protect your system from a vulnerability in the Server service.
Once again, a Windows security patch is causing users of ZoneAlarm security software on XP systems to lose their Internet connection.
It’s important for users of many different ZoneAlarm products to update their programs before installing this week’s XP patches.
The move from 32-bit Vista to its 64-bit counterpart can be rocky, so be sure to check for device drivers beforehand.
I’ve got some other early-implementer advice on how to keep the migration to 64-bit computing a smooth ride.