Scheduling bug??

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The "scheduled scan" time won't update on the new AntiSpyware version. We
used to schedule overnight run around 0130-1415, but want to change that to
1400. When I try to re-set the time pop-up sez "Schedule changed", but as
soon as I OK this it goes back to 0200.
I've just noticed it will work OK up to 1200 - looks related to madcat's
earlier post maybe... Anyone else found this?
 
Updated MASW yesterday nad still got the problem. Installed on Italian
version of W2k pro
 
Come on Bill, you must know by now 24 hours in a day not 12 as your schedule
clock things, great program careless bug!
 
I see the scheduling bug continues in the update of Dec. 2005. It insists on
06:00 although I want it to run at 18:00.

What command line options are available to run it automatically using
another scheduler?
 
Hello Bill,

if your outside the USA,

Go to start/Control Panel/Country settings
Change Language to US English.
Click on Apply
Open MSA change all your time settings the way you wont.
Click on "Update Schedule"
Then go back to set your default Language.
MSA will scan and update on the right time!
Don't Click "Update Schedule", anymore, then it go's back to the AM
times again!

With Regards >*< TOM >*<
 
Have you noticed the workarounds for this bug which are posted a number of
times daily in these groups?

Here's the quickest. Go to control panel, regional settings, and change
your languate to English (United States)

Then make the afternoon schedule setting.

After scheduling the scan, change the language setting back to your
original choice.

The scan will happen at the desired afternoon time.


For command-line options, see:

http://blogs.technet.com/stevedod/archive/2005/04.aspx

--
 
Many Thanks, Tom. It worked fine.

I understand that we are divided by a common language but does that apply to
numbers too!?

Bill
 
Bugs are bugs across all languages and borders. If you set United States
settings to a 24 hour clock, the same bug is invoked.

I think that it is really unfortunate that this one wasn't fixed--but I
don't know how much work it would have cost, either.
--
 
Back
Top