What's your reaction on this?

I don't think so, see here, pretty sure that is it.

Blue

 

OK,OK

Only 2?

Regards
LBD

 

The omission was intentional. I usually don't believe in burning bridges, so I don't want to make it painfully easy for NSClean to know who I am (though they probably do already). I'm not very worried about it, but on the other hand, I don't want to bend over backwards in letting them know who I am.

I reproduced the problem in three environments, two of which were fresh installs.

As for NSClean's responsiveness, this isn't the first time my queries have been ignored once the problem seemed to become too entrenched (though previously, I had not nailed it down to a specific problem with BOClean).

 

The problem occurred on two systems running under VMware, but also on my "real" system, where VMware is installed. I did not try running without VMware installed, but I would be utterly surprised if its mere presence had anything to do with the problem.

 

When I mentioned AT software pissing me off, I had forgotten about TrojanHunter--which works very well on my system. But I've been running KIS 6.0 for a couple days now, and I'm in love. I just removed TrojanHunter (and NOD32!) as I see no use for it (nor its new $20-per-year $12-per-year, or $16-per-two-year subscription fee). Thanks for the advice, though.