Microsoft Security Essentials 2.1.1116.0

I have not seen that issue, but I have seen a few other bugs in past versions that caused me to move on to something else.. There always seems to be something slightly amiss....

 

Don't let it do a "full scan." Quick Scan is good enough unless you have an infected machine. Some people have reported excessive disk access after setting up MSE to do periodic full scans.

I also have no slowdown from MSE on my Netbook running Win7 starter edition.

 

I haven't had any system bogging down or slowdowns browsing while using MSE.
I'm using it on W7 64bit.
I have done a full scan on occasion and never had any trouble with it. I normally do the quick scan weekly.
It's been trouble free for me so far.

 

ditto- same here
robin

 

MSE found some viruses in my pen drive and it wanted to do upload some suspicious files. I use a Standard user account but I could not see the names and path of the files MSE wanted to upload. I had to enter my admin password to see those files and upload them. But I feel it is risky to do this as MSE self defense is poor.

 

It is fine.

 

I'm using MSE 2.0 (still no 2.1 update via WU ) on my laptop with W7 Pro x64 SP1 and so far so good!

Only gripe is that while scanning folders with Total Commander (my default file manager) MSE takes quite a long time to scan all the exe's in them (you can see the CPU getting heavy and the icons slowly showing).

I'd like to ask you mates if it's safe to check the option to only scan incoming files. Does MSE really 'remember' the previous files in the computer?

Thanks!

 

It is this and this alone that stops me from using MSE on my PC.

 

It whitelists exe files already scanned until the user logs off.
And better to not disable monitoring all files.

For the slow exe loads, i just put all my exe installers in a separate folder since its very rare to access them if the program is already installed.

 

Thanks a lot!

 

But why all these complications when other products don't have such problems and have just as advanced if not more scan engines? I like the minimalistic approach of MSE, but i totally hate their retarded 24 hour update check cycle, idiotic on-access archive scanning and god awful slow on-access scanner...

 

Sounds like a wonderful product

 

you're welcome

 

Hear, hear!

 

Please kindly find SignatureUpdateInterval key in the registry.
When you change value to 1, MSE will check availability of updated signatures
each one hour.
Also, you can use for example 6 and 12

Best regards
William

 

You shouldn't need to tweak registry entries manually to get updates more often or more regularly. I think that's one of his points.

 

I agree.

 

Just a thought IMHO:

MSE does what Microsoft says it does. It provides basic security, nothing more, nothing less. Is not aimed for the tech-savvy minority but for the vast majority of users who does not want to tweak their product and just want it to work in a leave-and-forget way. Furthermore, it is free. Somehow these facts seems to be forgotten by many.

Yes, I agree that MSE can be improved, everything can be improved. When the product is tested other free or paid products sometimes score better but given the fact that about 10% of the Windows users worldwide use the product, I am still waitng to hear about it failing them to the point that is not deemed a reliable security solution that fills its stated purpose. If the product is so inferior that some people in this thread seems to believe, that should have happened by now given the number of copies distributed.

Regards,
Joakim

 

Exactly.

 

Even if you're an above average user MSE is a perfect solution.
Why? Because in that case you will want a second or third layer of protection, and the most compatible AV I have tried is this one.
I have used it alongside:
Online Armor (HIPS on or off)
Threatfire
Comodo (defense+ on or off)
Outpost Suite free (with Outpost's AV enabled)
Immunet
Avast, all shields on (yes, yes)
Mamutu

It's not the best of AVs, does not intend to be; it is the most simple and compatible of all. No good surprises and no bad ones as well.

 

I've been running 2.1 since it was first released and noticed that it caused EventID 72 SideBySide errors every day since I installed it. This has been reported on their support site without any resolution.

Removing MSE solved the problem for me.

 

SideBySide errors can be resolved by installing runtime components of Visual C++ Libraries.

 

Did that fix the problem for you running MSE 2.1? As far as I know, everyone running this version of MSE is seeing these errors in the Event Viewer.

 

I've been having logs in Event Viewer since MSE's first beta (June 2009).
There's nothing to it.

 

Before installing Microsoft Security Essentials 2.1.1116.0, I had a previous version installed, so I downloaded the 2.1 package and uninstalled the old version and re-booted and then installed 2.1. Not had any SideBySide errors with any of the MSE versions, I’m running Windows 7 x64 with SP1.

... I’ve just checked the other computer running Windows 7 x86 with SP1, and there are no SideBySide errors, so apparently not ‘everyone’ with MSE 2.1 is experiencing these.