G
Guest
I do not see the Defender is any advanced MSA. Instead I view Defender as a
NEW anti-spyware program. New interface, new search alogrithm, new
scheduler, etc. Why is this a BETA2. It is a BETA or BETA1 for the Defender
program.
I think the program is a step backwards from MSA. It is full of bugs,
autoscan, what about this ignoring MPCMDRUN popup, where id the history of
scans performed, excedpt for checking the Defender home screen how do a
know a scan was run and that that I have real time protection.
----------
Task schedule is set to automatic and the other automatic tasks on my
machine are all running. Face it Defender has a bug -- instead of looking for
a quick solution maybe MS should look for the problem and fix it.
I noticed that several people are having this prolem. In fact, some people
are getting the ballonn that scan has not not run in XX day because the
auto-schduler is not running.
Why did the MSA autoscan work on my machines last week and
Defender does not work?
How is MS verifying that the BETA 2 is working? The history does not give a
history of when the scan were run.
I would like to see a months worth of scan to verify what days the scans
were run. How do I know that last Monday a scan was run without a history of
scans?
Is the BETA2 creating history files or debug file you can send to MS them?
Why to I have to keep getting a balloon for MPCMDRUN each time I reboot?
It looks like from Beta1 to Beta 2 was too big a step.
Why did the MSA autoscan work great but defender does not run? (same machine
and same software)
NEW anti-spyware program. New interface, new search alogrithm, new
scheduler, etc. Why is this a BETA2. It is a BETA or BETA1 for the Defender
program.
I think the program is a step backwards from MSA. It is full of bugs,
autoscan, what about this ignoring MPCMDRUN popup, where id the history of
scans performed, excedpt for checking the Defender home screen how do a
know a scan was run and that that I have real time protection.
----------
Task schedule is set to automatic and the other automatic tasks on my
machine are all running. Face it Defender has a bug -- instead of looking for
a quick solution maybe MS should look for the problem and fix it.
I noticed that several people are having this prolem. In fact, some people
are getting the ballonn that scan has not not run in XX day because the
auto-schduler is not running.
Why did the MSA autoscan work on my machines last week and
Defender does not work?
How is MS verifying that the BETA 2 is working? The history does not give a
history of when the scan were run.
I would like to see a months worth of scan to verify what days the scans
were run. How do I know that last Monday a scan was run without a history of
scans?
Is the BETA2 creating history files or debug file you can send to MS them?
Why to I have to keep getting a balloon for MPCMDRUN each time I reboot?
It looks like from Beta1 to Beta 2 was too big a step.
Why did the MSA autoscan work great but defender does not run? (same machine
and same software)