scan schedule - setting time

  • Thread starter Thread starter bert forest
  • Start date Start date
B

bert forest

I have tried to set the schedule time to a time other that
12:00:00 AM and after clicking "Update Schedule" and then
clicking OK to "scan schedule has been update" popup, the
scan time returns to 12:00:00 AM. Duh! My computer is
always turned off at midnight so the scheduled scan never
runs and any notice that it didn't run appears to slid
across the screen and out of view.
Has anyone figured out how to set a time other than
midnight and have it run at the new time?

Thanks
 
you click on the AM/PM and use the arrow buttons to set for 12:30AM or
12:30PM
Untitled (e-mail address removed)
 
I'm having the same problem as the OP. I can set whatever
time I want and 'update schedule'. When I'm returning
everything is reset to January, 1st 2004 12h a.m.
 
Ahh - OK I missed that no time whatsoever was working. I've seen this
posted as well before, and don't have a solid recommendation. It seems to
me that this is one of those symptoms of either an incomplete installation
or a permissions issue--the program isn't able (or isn't willing!) to write
information to the storage location. I would try repair installation via
add or remove programs, Microsoft Antispyware, change, update. If that
fails, uninstall and reinstall. Make certain you are logged in as an
administrator on the local machine, and consider making the install location
non-standard--say, c:\msas rather than under program files, if this
persists.
 
Bill said:
Ahh - OK I missed that no time whatsoever was working. I've seen this
posted as well before, and don't have a solid recommendation. It seems to
me that this is one of those symptoms of either an incomplete installation
or a permissions issue--the program isn't able (or isn't willing!) to write
information to the storage location. I would try repair installation via
add or remove programs, Microsoft Antispyware, change, update. If that
fails, uninstall and reinstall. Make certain you are logged in as an
administrator on the local machine, and consider making the install
location non-standard--say, c:\msas rather than under program files, if
this persists.
Click to expand...

I did everything you mentioned but nothing helped. In addition I made a
fresh install (as administrator) on another drive & folder -- same
result. This is a bit annoying ...

I'm using win2k /w service pack 4. Could it be that some other
threats -- like 'F-Secure Internet Security 2005' -- causes problems?
 
It is possible that the F-secure product might interfere in some way, but
this seems a very subtle effect.

Can you check your short and long date formats for your locale, in Control
Panel?

Make sure they are set to the default, which I believe is the very first
choice in the drop-down?

There's an issue with this beta where if these date formats are not at the
default they either prevent install (beta time bomb date considered already
past) Or, in at least one case, the time bomb came up early--sometime in
the last week, as I recall.

So-- there some significant problem with the date and time function
programming, and it won't hurt to check that detail.
 
I'm sorry, even these locale are set to the first entry. But of course
they are german by default. Short: TT.MM.JJJJ Long: TTTT, T. MMMM JJJJ
 
I don't know. The beta is marked as English only, but I've heard from users
in a variety of other locales who are using it without issue, but perhaps
for Germany this is an issue. Changing the locale and testing would be the
way to find out, I think.
 
Excuse me for being such stubborn... I've changed my locale to
English(US) with everything like date & time formats now being US like.

Then I opened MSAS and tried to change the schedule to something other
than January, 1st 2004. Ok, it still doesn't work. The funny thing is
that now it displays in the main window under 'Last Scan Run' December
30, 1899 [sic!!] at 12:00 AM.

I now assume the there's something serious wrong in this beta...
 
There are serious date/time related issues with the beta, but it also sounds
as though your particular install has a problem which I can't recall seeing
before.

Can you try downloading the new (as of February 16th) .509 build?

Please be certain you are running as administrator, and additionally that
you install with as few third-party services running as possible--antivirus,
other security applications, etc--just for the duration of the install and
first run.

I would go ahead and run in your proper locale, I think you've proved that
this particular issue doesn't relate to that.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

Ulrich Dirr said:
Excuse me for being such stubborn... I've changed my locale to
English(US) with everything like date & time formats now being US like.

Then I opened MSAS and tried to change the schedule to something other
than January, 1st 2004. Ok, it still doesn't work. The funny thing is
that now it displays in the main window under 'Last Scan Run' December
30, 1899 [sic!!] at 12:00 AM.

I now assume the there's something serious wrong in this beta...

Bill said:
I don't know. The beta is marked as English only, but I've heard from
users in a variety of other locales who are using it without issue, but
perhaps for Germany this is an issue. Changing the locale and testing
would be the way to find out, I think.
Click to expand...
Click to expand...
 
My version number always displays 1.0.501; after updating this didn't
change. So I uninstalled the program and downloaded the .509 build and
installed it with prior unloading F-Secure etc. Now it really displays
..509 as build.

The scan schedule problem still didn't disappear. I'm assuming that
settings are stored in registry and not in a file. Can I check this?

BTW notorious behavior is Options->Settings. Under Real-time protection
the first checkbox isn't checked, the second is, the third is checked as
'automatically prevent all scripts from running'. After I changed these
settings to the recommended values and clicked 'save' the checkboxes
automatically return to there 'false' values... (but of course I don't
want to automatically prevent all scripts from running)

After hitting the 'Spyware Scan' button the window now states 'Spyware
definitions out-of-date! Last updated on April 5th 2004 12:10' (lower
right location; and of course everything is up-to-date!)

The 'Tools->Summary' window also displays wrong values like the wrong
date in 'Scan Schedule' and 'Spyware Definitions' shows '00/00/0000
(version 12)'

Under 'Scan Scheduler' 'Select Your Scheduled Scan Times' the next line
displays 'Current scheduled scan runs at: <cr> lblScheduleDisplay'.

Bill said:
There are serious date/time related issues with the beta, but it also
sounds as though your particular install has a problem which I can't
recall seeing before.

Can you try downloading the new (as of February 16th) .509 build?

Please be certain you are running as administrator, and additionally that
you install with as few third-party services running as
possible--antivirus, other security applications, etc--just for the
duration of the install and first run.

I would go ahead and run in your proper locale, I think you've proved that
this particular issue doesn't relate to that.

Ulrich Dirr said:
Excuse me for being such stubborn... I've changed my locale to
English(US) with everything like date & time formats now being US like.

Then I opened MSAS and tried to change the schedule to something other
than January, 1st 2004. Ok, it still doesn't work. The funny thing is
that now it displays in the main window under 'Last Scan Run' December
30, 1899 [sic!!] at 12:00 AM.

I now assume the there's something serious wrong in this beta...

Bill said:
I don't know. The beta is marked as English only, but I've heard from
users in a variety of other locales who are using it without issue, but
perhaps for Germany this is an issue. Changing the locale and testing
would be the way to find out, I think.

I'm sorry, even these locale are set to the first entry. But of course
they are german by default. Short: TT.MM.JJJJ Long: TTTT, T. MMMM JJJJ

Bill Sanderson wrote:
It is possible that the F-secure product might interfere in some way, but
this seems a very subtle effect.

Can you check your short and long date formats for your locale, in
Control Panel?

Make sure they are set to the default, which I believe is the very
first choice in the drop-down?

There's an issue with this beta where if these date formats are
Click to expand...
not
at
the default they either prevent install (beta time bomb date considered
already past) Or, in at least one case, the time bomb came up
early--sometime in the last week, as I recall.

So-- there some significant problem with the date and time function
programming, and it won't hurt to check that detail.


Bill Sanderson wrote:
Ahh - OK I missed that no time whatsoever was working. I've seen
this posted as well before, and don't have a solid recommendation.
It seems to me that this is one of those symptoms of either an
incomplete installation or a permissions issue--the program isn't
able (or isn't willing!) to write information to the storage
location. I would try
repair installation via add or remove programs, Microsoft
Antispyware, change, update. If
that
fails, uninstall and reinstall. Make certain you are logged in as an
administrator on the local machine, and consider making the install
location non-standard--say, c:\msas rather than under program files, if
this persists.

I did everything you mentioned but nothing helped. In addition I made
a fresh install (as administrator) on another drive & folder -- same
result. This is a bit annoying ...

I'm using win2k /w service pack 4. Could it be that some other
threats -- like 'F-Secure Internet Security 2005' -- causes problems?

I'm having the same problem as the OP. I can set whatever
time I want and 'update schedule'. When I'm returning
everything is reset to January, 1st 2004 12h a.m.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top