unnecessary warning "You haven't scanned your computer in 3 days"

[Willem]

Under Tools, General settings I can change the schedule voor a scan from
daily to weekly. If I do that, WD may assume that I make this choice in full
consience and sanity. Still, after 3 days I get an icon with an exclamation
mark in the system tray, and a warning "You haven't scanned your computer in
3 days". I do not like unnecessary warnings, balloontips etc.

Willem

 

[andre]

I did they same and got the same nag. Please stop em.

 

[plun]

Hi

Same opinion.

I have my weekly Spyware scan after new defs arrives, the time
between I thrust RTP functionality.

With my antivirus program I scan perhaps 2 or 3 times a week and
thrust my RTP also about virus.

"Scanning your PC to death"

regards
plun

 

[Bill Sanderson]

I'm not disagreeing with anyone. What I will say is that the quickscan is a
better scan than I had initially expected--i.e. it works backward from
startup items and integration points--so if you have an active problem the
quickscan should find it. I'm leaning towards doing fullscans only once I
have found and cleaned a problem. And quickscans take a LOT less time.

See message from either Joe Faulhaber or Mike Treit explaining the
difference between the scans--not sure what group--maybe sigs?

--

 

[plun]

Hi Bill

I DON`T want any stupid baloon

Perhaps just a checkbox... "I don´t want baloons", save me from them !

And can someone from MS explain that it is no meaning to "scan and
scan" with a RTP shield.........

Spoiling great PC time with scans.....

regards
plun

 

[Bill Sanderson]

I think scans are for the same reason they are with antivirus--to catch
stuff already in place before new signatures identify it.

I agree that they are overemphasized--otoh--how soon is soon enough to catch
a keylogger?

--

 

[Guest]

Bill, my point is that it makes no sense to offer the possibilty to set the
schedule to *weekly* and then to start nagging me with warnings after 3 days.
The guy that wrote the warning routine just forgot to do a check on the
schedule setting.

Willem

 

[plun]

Hi Bill

50 Million PCs switched on 24/7 beacuse of all scans.

Lets say 12 hour uneeded switched on time, maybe 300 days per year.
300W/PC

1 PC 1080 kWh/year

Nearly 50 Million MWh electricity for a nightly scan

MS is the worlds greatest environment destroyer becuse of WD



regards
plun

 

[Bill Sanderson]

The scheduler should be capable of waking the system from a deep sleep state
to do the scan. In fact--there's one testimonial to the success of that in
these groups--however, the poster complained that it failed to allow the
monitor, at least, to go back to sleep.

My loose advice to folks is to schedule stuff for every night and just pick
one a week to leave the machine on. That probably isn't going to fly with
Windows defender since it catches missed scans and starts them 10 minutes
after the next login, according to an MS post, and the experience of some
posters here.

--

 

[Guest]

Bill, again: I did not start this thread to discuss what the right frequency
for scans is. Neither is this about energy conservation. Please start a new
thread to discuss that.
The fact is that the option *is there* under Tools, General settings to set
it at weekly. If the WD team thinks that weekly is not a good idea in any
case, the option shouldn't be there. But it is there. And since it is there,
I should only get reminders to scan my computer starting the 8th day, not on
from the 3rd day on after I set it to weekly. Period.

Willem

 

[Guest]

Hi all,

I agree with Willem. This is a bug. We should have found it. Now it's in
our bug DB.

Thanks for the report - and for trying Windows Defender.

Joe

 

[Guest]

Joe,

Thank you for responding. I discovered some more to this:
When logged in as a limited rights user, I also get this notification. If I
open WD, the
Start Scan button is greyed out (yes I have set the option to allow users
without Admin. rights at the bottom of the General Settings screen). If I
launch WD from the Start Menu with "Run As" and give Admin. credentials, a
new instance MSASCui.exe is launched and the Start Scan button comes
available in both instances. But if I click it the infamasous 0x80004003
error occurs. After that error, the button is gray again for the MSASCui.exe
that runs with limited rights.
Just for fun, I tried to launch more MSASCui.exe's with Run As. You can
really fill up the taskbar with WD-exclamation mark icon's in the SNA
I will start a seperate thread for that one.

In contrary of all the complaining by old beta users here, I think Beta2 is
a big improvement from a non-tech user perspective.

cheers, Willem

 

[Bill Sanderson]

It certainly seems arbitrary and a bit short to me.

--