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.
Antivirus software from Symantec Corp. may cause the installation of Service Pack 3 for XP to corrupt the Windows Registry by adding unnecessary keys.
Symantec advises users to disable the SymProtect security feature of its products before applying XP SP3.
Both HP and Microsoft are working to fix problems causing AMD-based PCs to reboot repeatedly after XP Service Pack 3 is loaded.
In the meantime, security expert Dr. Jesper Johansson has beaten the companies to the punch by devising a tool that ensures AMD machines can be patched.
Microsoft’s latest — and last — service pack for Windows XP causes some systems that use AMD chipsets to reboot over and
The solution involves booting into Safe Mode or using the Recovery Console to disable a problematic driver.
Windows XP Service Pack 3 will soon be available, but that doesn’t mean every IT pro should rush out and install it on all XP systems.
My philosophy is that while service packs should always be installed, they don’t necessarily need to be added right away. XP SP3 is no different.
On the heels of Vista Service Pack 1 comes the update that far more Windows users have been anticipating.
Unfortunately, XP Service Pack 3 is an unremarkable update for everyone except network admins, who will appreciate the additional control over wired and wireless connections offered by SP3’s Network Access Protection.
An unannounced auto-deployment of Microsoft’s .NET Service Pack 1 rocked the accounting industry by affecting key applications right before the U.S. tax deadline.
This week, I’ll help you control the damage by providing you with a primer on .NET patching.
Patches for IE should be our first priority this month, with several vulnerabilities that are ripe for malicious attacks facing us.
There’s still no sign of Windows XP SP3 in the near future, but Windows Server 2008 is receiving its first patches, and Vista SP1 is subject to a much-needed patch for an earlier patch that’s proved troublesome.