To celebrate symantec-sucks.blogspot.com's existence I have decided to finally upload my avsucks folder.

(Note: This is an image-laden post that needs to be viewed separately. Clicky below to go to the article.)

I know that these images go off the edge of the screen but I don't mind. I don't have time to make it elegant by resizing crap, so just go away if you don't like it. I've also off-turned the bar of sides on this post for to make things fit better-ish like (and such).



Even Microsoft is not exempt from gamma retardation rays:
Windows Defender
There was an error while downloading the "mallware signeture".



McAfee uses the most exploitable, most easily broken engine within Windows to do all of its most important functions, such as updating, scanning, and uninstalling: Internet Explorer's ActiveX garbage!
McAfee's ActiveX troubles



McAfee doesn't stop there, though… they want you to remove their competitors because they can't be arsed to figure out what they did wrong. I say "they did wrong" because there's no way Spybot is causing whatever problem McAfee is trying to avoid here.
McAfee can't handle competition



So begins the barrage of Norton/Symantec images. The first one is a common one (already found on the Symantec-sucks blog but I had to post it anyway).
Symantec has no idea how to program
So you're able to tell me it's running in the background, but you're not able to just bring that window forward? What if that background process gets stuck or produces an invisible error message (can't rule anything out when it comes to Symantec)? It could potentially say "please wait" for the rest of your life!



This screenshot seems kind of normal until I tell you that I took this screenshot in August of 2007 with fully-updated definitions. I feel safe knowing there hasn't been any virus outbreaks since February 2006!
I feel safe now



Since I requested that LiveUpdate open up, why don't YOU wait until later and then open it FOR ME when you're ready? Will you ever be ready? Again, why can't you just bring the "background" session into the foreground?
You didn't really want to run LiveUpdate anyway



This set is a one-two punch that speaks for itself. In the second shot, I've launched LiveUpdate so I can see which programs are still registered with LiveUpdate (which is what the first shot is bitching about).
LiveUpdate registrations are still present
The only thing registered with LiveUpdate is LiveUpdate



Why are these things blocked by default in Norton Internet Security?
You didn't need NetBIOS or SSL anyway.



Because I've chosen an option other than what Symantec deems correct, it wants to "fix" the setting and put it right back to automatic. I didn't want automatic Windows Updates. I want to choose when to install them! Oh god, my computer is broken! Please "fix" it!
You'll take this setting and LIKE IT



What the fuck, Symantec. What the fuck:
Automatic LiveUpdate scheduler will devastate your Event logs if you don't comply



This virus was a ridiculously easy one. Unfortunately, Norton made it infinitely harder. You see, even if Norton can't do anything with a file (as usual), it locks it so you can't do anything either. After killing Norton's processes off, I was able to unregister this DLL and simply delete it. Yes, I was able to click it in Explorer and simply delete it. Norton won't even offer to delete it upon reboot, close any programs that are using it, or anything. It just says "nope, I can't help you – but I won't let you help yourself, either, so here's a ton of file locks to keep you from touching this file ever again".
Wimpy ass virus that Norton can't remove



Symantec's errors are certainly not limited to actual use of the product. You can't uninstall it either.
Since an error occurred during uninstallation, the recommended course of action is to uninstall it and reinstall it before uninstalling it:
Uninstall and reinstall to uninstall



The last entry is not Symantec's (yay!), but it's indicative of the same ineptitude in software engineering.

Trend Micro's security offerings are also kind of shitty. It wants to remove Spywareblaster for you because the developers couldn't be arsed to fix their whitelisting software. Yes, it's their fault, not Javacool's (maker of Spywareblaster). When Spywareblaster's immunize functions are activated (a bunch of ActiveX "kill bit" entries in the registry), Trend Micro's whitelist software goes nuts and takes up all of your processor's time to make an infinitely-growing .dat file. The method Spywareblaster uses to immunize is legitimate and is supported by Microsoft for the exact purposes Spywareblaster is using them for. I think Symantec outsources to Trend Micro or vice versa.
Trend Micro Internet Security is garbage.