MS Windows Defender beta 2 out

updated this morning thru windows update 1.131276.16

 

Up to this moment MSAS leads. downloaded and installed Kazaa this morning both MSAS and NOD32 were fighting "in real time" the huge numbers of malwares and they did really great job to keep the computer disinfected. However, when Windows Defender and NOD32 were used only NOD32 was fighting "in real time" while WD did a good job "on demand".

 

i installed Defender about two weeks ago--and now my machine crashes at least once a day. I haven't uninstalled it yet--am just shutting it off.
If no more crashes occur with it shut-off--then i must assume that Defender is the cause of the crashes.

Anyone else having this sort of prob??

 

Working fine with me so far, only problem I have had is on the update for it, downloaded if fine and installed it no problems.

Now on the 12th notification of a download for update, the same one.

 

I never understood those people that install betas and then complain about crashes, things not working or slow. The word "beta" was an ugly word 10 years ago. Few wanted to have a beta version on their PC, now it seems that a new generation thinks that it shouldn't mind installing beta software on a working system. What's next? We are all going to install alpha version?

 

LOL. I fully agree with you. Betas for everyone nowadays. Unbelievable.

 

Reference

EDIT - MAJOR EDIT, PLEASE EVERYONE MIND THIS! UPON FINDING FALSE POSITIVES, THIS CRAP STALLED ON TRYING TO IGNORE OR ALWAYS ALLOW. FOR 20 MIN. UPON UNINSTALLATION, THIS DESTROYED THE MASTER BOOT ON THE COMPUTER, AND I HAD TO RESTORE IT BEFORE I COULD BOOT BACK INTO WINDOWS. BEWARE PEOPLE.
TESTING THIS DIARRHEA ON TWO COMPUTERS WITH SIMILAR RESULTS!


My experience is slightly different. I had no problems selecting ALWAYS ALLOW once WD2 finished its initial full scan. Uninstalls caused no problems. I have noticed that if you attempt to take actions while major scan activity is still going on -- things might hang for a while. Perhaps there is something odd about the system customization or even an infected WD download. (MS has had "summer interns" load up infected software to the Internet before.)

What is really annoying is that the scan activity seems tuned for power saving. That is the scans appear to try to piggyback on to when the system is being used. As result the system full scans (very exhaustive) take forever to complete. I guess this would be good for laptops to conserve power except as many have noted WD doesn't do a real good job of judging what level can be hidden as noninterfering background activity.

There also seems to be a little of the old style AV scan problem. I think any "on access" scanning should be an optional feature done against files after memory loading -- if done at all, rather than reading the disk files twice, once to scan and once to load. Most spyware is not as time critical as what AV covers. This really defeats one of the purposes of anti-spyware -- lost system performance.