| By Susan Bradley |
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.
A Registry fix is needed by the latest XP patch
The latest in the continuing series of problems related to Windows XP Service Pack 3 involves Symantec’s Norton AntiVirus. The company recommends that users disable the program’s self-protection feature before installing XP SP3.
Subscribe to our Windows Secrets Newsletter - It's Free!
Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!
Subscribe and get our monthly bonuses - free!
Your hard drives store photos, books, music and film libraries, letters, financial documents and so on. This ebook is aimed at helping you understand your hard drives, expand their capacities and length of life, and recover what you can from them when they fail. We're offering you a FREE Excerpt! Get this excerpt and other 4 bonuses if you subscribe FREE now!
In a post to Norton’s support forum, Symantec senior SQA manager Reese Anschultz suggests that customers disable the SymProtect feature found in various Symantec security products:
• To do this in Norton Internet Security 2008 and Norton AntiVirus 2008, uncheck Turn on protection for Norton products on the Options pages of these programs prior to installing XP SP3. Once the service pack is in place, return to the Options page and re-enable this setting.
• In Norton SystemWorks 2008, open the Advanced Options under Settings, click Next, choose Norton SystemWorks Options, and select the General tab. Uncheck Turn on protection for my Symantec product.
For other Norton products, read Anschultz’s post, which comments that other third-party security products may also cause problems unless some functions are disabled before SP3 is installed.
Some Windows Secrets readers have had to remove Norton AntiVirus completely before deploying XP SP3. While taking this step may sound extreme, reader Bert Smith from Australia was told by a Symantec engineer that he should “follow these instructions” to use the Norton Removal Tool to uninstall Norton Internet Security 2008 before he deployed Vista SP1!
Given what we now know, it may actually be wise for you to uninstall Norton antivirus products prior to deploying SP3, which is XP’s latest — and last — service pack. Thanks to reader Jan Levine for identifying this issue in the Microsoft TechNet Forums.
If you find that installing XP SP3 has corrupted your Symantec security product, my fellow MVP Bill Castner has devised a downloadable Registry fix (scroll down the page until you see My “Fix”). Castner first identified this issue along with Jesper Johansson, who’s been tracking the XP SP3 problem in his blog.
Johansson also provides a patch for AMD computers that XP SP3 causes to reboot constantly. I described this problem in my May 22 column. For more information, see the following item.
A cure for XP SP3′s never-ending reboots
If you’re one of the folks whose AMD-based PCs constantly reboot after applying XP SP3, here’s how you can recover.
When the system is first booting, press F8 to enter Windows’ Safe Mode. Log into the Administrator acccount, click Start, Run, type cmd, and press Enter. When the command window opens, type the following command (don’t forget the space after the equals sign, which is required):
sc config intelppm start= disabled
The problem is caused by the presence of Intel drivers on AMD-based systems. Follow the above steps only if you know your PC uses an AMD processor; doing so on an Intel-based machine could render the system unusable.
To determine which processor your system uses, open the Control Panel’s System applet and click the General tab. (See Figure 1.)
Figure 1. Open the System applet in Control Panel to verify the type of processor your PC uses.
If the processor listed in the window is “Intel,” do not enter the command shown above. An Intel-based system that constantly reboots may be having an unrelated problem. It might be caused by conflicts with antivirus products, as described in my previous item, or something else entirely that no one has yet identified.
As I wrote in my May 22 column, there’s no rush to install XP SP3. Wait until we know more about these kinds of conflicts.
The Patch Watch column reveals problems with patches for Windows and major Windows applications. Susan Bradley recently received an MVP (Most Valuable Professional) award from Microsoft for her knowledge in the areas of Small Business Server and network security. She’s also a partner in a California CPA firm.