Thanks for posting the feedback. Microsoft does read these groups, and your
feedback is valuable.
Some comments:
a) is not necessary. It is possible for a scan to run at night on a machine
with no user logged in, but that's not a requirement of the program--I scan
at times I expect my machine to be idle--it's a home machine, but I use it
very regularly via remote desktop at all times of the day and night--so my
scan is set for 10 AM when I figure if I am working that day, I'll be busy
earning $ rather than doing volunteer work here.
b) This one is of concern to the development team, I am certain. One
misunderstanding I suspect many have--I would recommend doing quickscans,
rather than fullscans, on a scheduled basis. I take the Microsoft
statements about what a quickscan covers seriously--I believe it is a good
indicator of whether there's a current infection. If something is found,
and it appears to be real, as opposed to a false positive, I would consider
doing a fullscan--or, perhaps, as an initial scan on a "new" machine.
c) bugs are not user friendly, for certain. I personally like the lack of
an icon and the behind the scenes way the program runs and updates.
