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.
Fake security programs are taking advantage of user gullibility in order to hold people’s PCs for ransom.
Windows XP users who are running with administrator rights are especially vulnerable to these drive-by downloads.
Microsoft’s GDI+ graphics system could be exploited to allow hackers to use image files to launch attacks on your system.
In addition to patching Windows, this bug requires that you update your Office apps, Works 8, Digital Image Suite 2006, and nearly every Microsoft application development product.
As usual, patching the browser could lead to conflicts with third-party security programs.
Still, now that malware can be found on legitimate Web sites, you need to install the latest Internet Explorer patches right away.
The new version of Check Point’s ZoneAlarm firewall solves one problem, but Windows Small Business Server 2003 still needs a patch for the DNS patch.
A change in how Windows’ DNS client chooses ports caught ZoneAlarm’s developers — and users — by surprise.
Check Point’s security software conflicts with a new Microsoft DNS patch, necessitating a workaround to get your Internet connection operating again.
Resetting ZoneAlarm’s firewall database or reinstalling the application will get your PC back online.
If you’re using the release candidates for Vista SP1 and XP SP3, you face a June 30 deadline to convert to the final versions.
For most beta testers, the transition is seamless, but some Vista SP1 testers may not be able to uninstall the service pack.
The repeating reboots caused by XP SP3 on non-Intel systems have been quelled, but there’s still no rush to install the OS’s last service pack.
Symantec’s FAQ addresses concerns with both XP SP3 and Vista SP1, while Microsoft’s Knowledge Base article avoids singling out AMD processors.