Bugs in AntiSpyWare tools

Everyone on the web consistently recommends Lavasoft's Ad-Aware SE and Spybot Search & Destroy, for protecting your PC. I install these two programs for most of my customers. Ad-Aware Pro, the version that includes Ad-Watch, is better because Ad-Watch loads at startup for live protection.

But I have yet to read anyone's comment, including the developers of these programs, about serious BUGS that each program has:

Ad-Watch often refuses to unload itself from memory, so when you click on Shut Down, it never does. This is a major pain in the ass. (Savvy users discovered a tool to unload all memory-resident programs, like Ad-Watch, to cure this: Google for Windows User Profile Hive Cleanup. It didn't work for me; maybe it will for you.)

Spybot version 1.4, which has been around for quite some time and is still the latest version, has a display bug that effectively hides half its message windows, so you can't properly make selections.

Both these bugs have been around for months and months, so now I don't install Ad-Watch for anyone (including myself), and I use Spybot 1.3.

Should I be complaining? Both these programs are free, yes, so never look a gift horse in the mouth, right? BUT my confidence in the ability of either of these programs to perform effectively and protect me and my customers from malware is seriously diminished, when the developers can't even be bothered to issue a fixed build.

Which brings me to Microsoft: not on the subject of anti-spyware, but their damn MSN Live Messenger. Did you know that early in October Microsft updated their server side, which immediately placed a bug in most user's client versions of Live Messenger, which in turn refused to allow them to connect! The little people heads that signify MSN just kept spinning, and spinning... When questioned, a Microsoft employee said he hoped that MS would issue a statement and a fix... but two weeks have gone by with nary a word from them. You'd think that with the millions of MSN users, this would have become an issue. I just don't understand it.

(You can fix this bug if you have it, in Live Messenge: Google for remove_wlmpolicies.reg)