I just trialled KAV 5 Personal Pro 5.0.372 and would like to offer some of my comments from a user that likes protection, but absolutely hates having to bypass problems due to bad design, bad software engineering or insufficient testing. I installed KAV 5 Personal Pro as on-demand only (this is what I wanted to test), disabling iStreams and Real-time protection during install. Disabling iStreams does not add ADS tags to files (i.e. bypassing the initial fragmentation increase issue people have talked about here and elsewhere). After a restart I tried starting KAV. It started up nice, but closed itself after c. 10 seconds. I tried starting again, again it closed itself. I went to look for an answer in the volunteer based Kaspersky forum (forum.kaspersky.com). Could not find one via browsing & using the search. Running a very tight system I wanted to make sure it was not due to malware. I scanned my system (full scan with Ewido, TDS3, NOD32, Bitdefender, AntiVir, Panda, eScan/KAV, a2, Counterspy, Spybot S&D, CWShredder and also took a look at running drivers, startup utilities and NTFS alt streams, run the latest rootkit revealer). Nothing found. At this point I was fairly secure it's an incompatibility issue and not an infection (esp. when the only software for the past week installed my system has been KAV + firefox 1.05). I disable Process Guard driver, TaskInfo drivers and other kernel level non-plug and play drivers and restart. Same problem. KAV quits itself. Ok, I proceed into configuring KAV during the 10 second time frame it stays up. I disable all real-time protections (files, internet, mail, macros, scripts, network). This takes some fast clicking, but I'm able to make the settings stick. KAV still crashes itself. I proceed to deleted the databases and manually re-downloading them. Bingo! Now KAV stays up, and does not quit itself. So, it appears KAV databases were corrupt and due to this, it silently quit itself, without any error, any notification or without trying to update itself. Quite moronic design, imho. Ok, time to hit Kaspersky forums to see what configurations I should use. Upon doing so, I'm hit with a barrage of problem reports: - Kav crashes on install - Kav fails to uninstall (esp. if Symantec antivirus has been on the machine earlier) - Kav crashes system - Kav causes BSOD - Kav fails to upgrade program component to a new version - Kav denies network access when used with Sygate - Kav double the number of Program Files links and processes by itself - Kav quits itself without a warning - Kav disables itself without a warning, leaving the system unprotected - Kav loses it's own key file (disabling itself again) - Kav failes to update the defs - Extended databases fail to be downloaded - Kav causes DDOS warning with various p2p software with default settings - Kav phone support does not answer - Kav fails to detect multiple locations of the same file via it's exclusion setting - Kav smtp mail scanner fails to work (sometimes works, sometimes doesn't) - Kav fails to uninstall itself Regardless of the programs stellar itw recognition rate and def update speed, I think I speak for the majority of computer users when I say: stay away from this product, unless you are an advanced user, feel very lucky, have lots of time & energy to tinker with it's settings and bybass it's bugs and idiosyncracies. What's even more disconcerting is that many of the findings for bugs/bad design/incompatibilies came from apparently advanced users (more so than the average joe). However, in many cases the "fix" was what the user had found out the hard way: do a tedious manual routine that bypasses the issue (does not fix it), instead of the developer acknowledging the issue, giving it a ticket and promising to fix it. It's not only that some of the issues in the program are quite old (being that they've been unfixed for long), but that new serious issues seem to pop up with even minor upgrades 5.0.xxx series. This is to me a serious indicator of flawed regression testing, bad software engineering and non-existent compatibility testing for a software as crucial as this. AV software should not be disabling itself without a warning, failing to install defs or corrupting it's own databases / license key. It should stay functional, up-to-date and functioning AND warn of all oddities/problems. As an example, compare this with the issues you see about NOD32 (or take another "bigger" AV utility). The problems with NOD32 seem extremely minor compared to issues with KAV 5. NOD32 is just one example, I could take many other examples. To be honest, I haven't seen such a buggy piece of security software in ages (not since Outpost Pro 1.0 anyway). And while I'm sure to get some advanced users calling me "n00b idiot, learn to use it!", I offer this as a warning to those with less time/skill on their hands: tread carefully, KAV is not a walk in the park. If you want an av solution that "just works", look elsewhere. Perhaps some of the programs that use KAV defs, but with a more thoroughly tested main application and less issues in it. My two cents worth. Best regards, Halcyon PS I think it's good that KAV doesn't get a lot of coverage in mainstream computer publications. With software quality at this level, they'd get absolutely butchered in any major computer publication catering for the big public (and not to the 10% minority of advanced computer users). It may scan well, but getting it to even install, not to mention, scan, update and stay activated can be a hell of a hassle.