This is related to an old thread I posted: (hxxp://www.wilderssecurity.com/showthread.php?t=87690) I've had problems with IMON, since updating to the first 2.5 version. It's never been resolved, and when I contacted Eset, they couldn't duplicate it... so the problem persists. Rather than going into the problem again, I have one question: I have things set in IMON, according to the *extra settings* thread... am I seriously weakening my protection, by using the default scanner extensions, rather than the *scan all files* which is recommended (misc tab - scanner setup)? When I do this, many of my problems with IMON cease, but I don't want to trade my security. What I do now, is when I experience problems on a particular (trusted) website, I disable IMON for a few minutes. It can be an annoyance, switching IMON on & off every few minutes. I still think there's some IMON bug with javascript & IE, since 2.5 was first rolled out, since it never happened with earlier versions Any help is appreciated...