back to article Symantec update killed biz PCs in three-way software prang

Symantec has apologised after an update to its security software sparked repeated crashes on enterprise Windows XP machines. The antivirus giant withdrew the misfiring definition update, issued on 11 July, hours after problems first appeared, releasing a revised update the next day. No new issues have been reported since this …

COMMENTS

This topic is closed for new posts.
  1. ukgnome
    Mushroom

    BOOM!

    Eat this XP

    (don't worry Ballmer, Windows 8 launch will be successful with our XP crushing payload)

  2. dotdavid
    Go

    In my experience...

    ...Symantec AV usually kills biz PCs with just one piece of software - itself, so requiring three to do the same is something of an improvement perhaps.

    1. Darryl

      Re: In my experience...

      Nah, that just shows laziness on Symantec's part... Their software now requires other software working in concert to perform the one task that Symantec's software used to be relied on to be able to do by itself.

    2. Joe S

      Re: In my experience...

      Agreed. SEP just kills laptops to its knees

  3. Anonymous Coward
    Anonymous Coward

    Big difference between false positive and BSOD

    While many antivirus updates can result in false positives, which is annoying, the idea that a pattern-recognition update can result in Blue Screen of Death is unacceptable. Symantec's enterprise product has become increasingly bloated. We finally abandoned server-based management because it never worked properly with our relatively small (less than 20 computers) network, did not transfer properly to a new server and does not treat Macs with the same flexibility as PCs. We went back to unmanaged clients. Even though the unmanaged Mac product has even less control over options, this is a minor annoyance compared to the seemingly unnecessary complexities of the server-based product. It is extremely telling that the product can rarely be reinstalled successfully without removing all Symantec/Norton products. That said, it's a dangerous world out there and buggy antivirus is better than no antivirus in this never-ending "arms race".

  4. Keep Refrigerated
    Trollface

    with anti-virus like Symantec...

    Who needs malware?

  5. DS 1

    Sillymantec

    A company that generally seems to move all its development off to third would countries, while having management still done by older shool middle and upper management. The result? Diabolically poor software releases. Get into the higher problem solvers, and you'll find the American guy has to talk to the Indian guy tommorow, as he is already finished for the day. The UK op is riddled with high paid sales idiots.

    The engineering at symantec long ago perished in the ever deepeing race to the bottom. All the useless middle and upper management still rack in the dosh, which is where the money goes.

    The last time I spent with them was when their backup products started eating our servers.

    True comment from Backup Exec defect ********

    This is Symantec’s confirmation and verification the issue you’re experiencing is a flaw within the CPS code. Specifically,

    If CleanUpPushDeploy is called with an empty string, it will attempt to delete

    everything on the root drive. The value in PushSource string value is what is

    passed to CleanUpPushDeploy.

    PushSource string value should be c:\<guid>

    HKLM\SOFTWARE\Classes\SOFTWARE\Symantec\Install Status\PushSource

    So, in the event the above registry guid is non-existent, we’re defaulting to the root of the volume to do our clean-up; this is “unwise”.

    End of defect info

    The poorly written installer was not worth much, and the uninstaller was seriously bad for our health.

    Yes, Deleting my whole C drive in your uninstall of a poorly working product was not well recieved at my end either. Unwise. Yes. I suspect that reserved, cautious use of english has a comic tone of indulgence unworthy in a senario where your un-installer just did a *.* delete on a client server.

    I will say the team dealing with the issue were very good about it, but the rest of symantec were_absolutely not. We were promised a public advisory because we worked hard with them on the bug on the premise that we might at least warn others. In the end senior Symantec people made sure that never went out.

    Ended up with some smoothies in suits talking down to use with their brycreemed hair and pin stripes, trying to diminish the scope of the issue and pretend it was not worthy of complaint. To be honest, bugs I can work with. Problems exist in this world. What I can't and won't is vendors who are patently bad, evil, indifferent. And the none publishing of a very embarrasing, but lethal problem for customers showed us they were not to be trusted. Ever. Other people deserved to know about it and get a chance not to suffer what hit us.

    To be blunt, the issue I worked on should have had Symantec offering compensation to us, if nothing else for our diligent and friendly and full complete co-operation despite extremely stressful circumstances.

    And at that point we ceased using Symantec products anywhere. Ever. And no, I'm never going back.

  6. kain preacher

    Win XP

    Wow It's not like XP was release 3 months ago. I've seen Norton destroy web browsers.

  7. Anonymous Coward
    Anonymous Coward

    Windows

    Is proprietary malware. I'm surprised the AV vendors don't detect the Windows trojan more often.

    Of course, this problem doesn't happen on Apple Mac or nix platforms.

    1. Captain Scarlet
      Unhappy

      Re: Windows

      Well no Apple users think they don't need an anti virus, I'm not going to say anything about nix users

      /me installs ClamAV on nix server

This topic is closed for new posts.

Other stories you might like