Replies

Let me say first an excellent review of the Resource usage for current free AV tools out there. It is always good to know which present specific loads on a system.

I have been using MSEE on a few systems for a while now and generally I don’t find it “heavier” on a system with one exception.

I have had it running on a couple of Win 7 Laptops one running Pro 64 bit and one running Home premium 32 bit. On both of these machines which are intermittent usage machines I noticed the same behavior.

When these machines had sat for approximately 1 week or more and the definitions had reached an out of date point. The machine on Login would exhibit high CPU usage and become unresponsive. In both cases they would exhibit extreme sluggishness and the operator could not get to Wireless connections to establish either a learned or new Wireless connection.

I know it was MSEE because on both machines it was showing nearly max CPU usage. I could kill the MSEE processes and the machine would become responsive allow you to connect the wireless and then at some point MSEE would re-enable and it would update.

It happened on numerous occasions until I replaced MSEE on those laptops.

I think what was happening is MSEE was trying to force an update due to the out of date status and since it could not find a network connection would tend to just hang.

I have multiple desktops and even laptops that generally sit on a wired network that I have not had the occasion to experience what I described above and in those cases continue to use MSEE and it has not failed me.

Anyway in the case of an intermittent use device especially a laptop I do not typically recommend MSEE but rather one of the other free tools out there.

Hope this is informative.