Microsoft's XP SP3 Patch Fixes Anti-Virus Glitch
Posted by Steven Parker on 02 July 2008 - 10:03 · 12 comments & 7606 views
About the Author
Full name: Steven Parker
Forum name: Neobond
Contact: via forum PM
Submissions: Normal · Headline
Full name: Steven Parker
Forum name: Neobond
Contact: via forum PM
Submissions: Normal · Headline
Slashdot It!
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
Add to Google- Advertisement
-
-
(3 replies)
#2 Posted by tereshchenko on 02 Jul 2008 - 12:15
- That's not registry problem - that's Symantec's antivirus problem.
-
#2.1 Posted by Azmodan on 02 Jul 2008 - 13:49
- (tereshchenko said @ #2)That's not registry problem - that's Symantec's antivirus problem.This problem occurs when the Fixccs.exe process is called during the Windows XP SP3 installation. This process creates some intermediate registry subkeys, and it later deletes these subkeys. In some cases, some antivirus applications may not let the Fixccs.exe process delete these intermediate registry subkeys.
When this problem occurs, certain applications, such as Device Manager and Network Connections, may be unable to enumerate the device or the connection instances. These applications will report a blank status even though devices and connections still function as expected.
It's a problem straight from major anti-virus retailers. So, how comes this is not a Windows problem? Because like the driver manufacturers, it's their fault that they didn't update their software to be compatible with the latest operative system. -
#2.2 Posted by non.sequitur on 02 Jul 2008 - 17:59
- (Azmodan said @ #2.1)(tereshchenko said @ #2)That's not registry problem - that's Symantec's antivirus problem.This problem occurs when the Fixccs.exe process is called during the Windows XP SP3 installation. This process creates some intermediate registry subkeys, and it later deletes these subkeys. In some cases, some antivirus applications may not let the Fixccs.exe process delete these intermediate registry subkeys.
When this problem occurs, certain applications, such as Device Manager and Network Connections, may be unable to enumerate the device or the connection instances. These applications will report a blank status even though devices and connections still function as expected.
It's a problem straight from major anti-virus retailers. So, how comes this is not a Windows problem? Because like the driver manufacturers, it's their fault that they didn't update their software to be compatible with the latest operative system.
What's an "operative system"?
-
(3 replies)
#4 Posted by cork1958 on 02 Jul 2008 - 12:43
- Anybody that installs Symantec crap on their systems deserves what they get from that crapware company!!
-
#4.1 Posted by non.sequitur on 02 Jul 2008 - 18:00
- (cork1958 said @ #4)Anybody that installs Symantec crap on their systems deserves what they get from that crapware company!!
Amen to that. -
#4.2 Posted by buletov on 02 Jul 2008 - 18:25
- The poor thing is that most of them perceive Norton as The Antivirus and aren't aware of the alternatives. This is mainly due to Symantec software (call it crap if you want, but it's merely a bloat) being preinstalled with most of the PCs and laptops lately. After three months of free use they get all kind of warnings that they MUST renew their subscription (or die) and this is just how the noose of the poor PC experience tights around their necks.
-
#4.3 Posted by smctainsh on 03 Jul 2008 - 04:31
- (buletov said @ #4.2)The poor thing is that most of them perceive Norton as The Antivirus and aren't aware of the alternatives. This is mainly due to Symantec software (call it crap if you want, but it's merely a bloat) being preinstalled with most of the PCs and laptops lately. After three months of free use they get all kind of warnings that they MUST renew their subscription (or die) and this is just how the noose of the poor PC experience tights around their necks.
Firstly, Symantec doesn't force you to continue using Norton Antivirus. It is entirely your prerogative as to whether you keep using it or not. Also, Norton Antivirus 2008 is a huge improvement on previous versions. I was skeptical at first, but took the plunge and am glad I did.
In the case of Symantec, it looks like a case of 'mud sticks' - people will continue to assume that a product is bad even when they start to improve it. In my opinion, these kind of assumptions can't be made, and people should gather the facts before jumping to conclusions. It becomes rather tiring to see the same comments such as 'Norton sux', when you know that said comments are false.
Smctainsh
-
#5 Posted by _dandy_ on 02 Jul 2008 - 23:02
- Freakin' Symantec.
First, they bitch and whine when they're getting locked out of the kernel and system services, and now they find ways to corrupt vital system files.
If viruses won't compromise your system, Symantec will corrupt it.
I just do...not...trust...any software that wants to take over basic system functions.
Some users who installed XP SP3 reported seeing garbled system entries that cluttered the Windows registry. The corruption in the registry led to problems such as lost Internet and wireless connections, along with uninitiated restarts caused by sporadic registry subkeys.
Microsoft provided an explanation for the problem in a Knowledgebase posting on Friday. The issue "occurs when the Fixccs.exe process is called during the Windows XP SP3 installation," the KB article explains. "This process creates some intermediate registry subkeys, and it later deletes these subkeys. In some cases, some antivirus applications may not let the Fixccs.exe process delete these intermediate registry subkeys." When the problem occurs, "certain applications" within Windows, such as "Device Manager and Network Connections" may be unable to function, Redmond added.