updates

  • Thread starter Thread starter The Franchise
  • Start date Start date
T

The Franchise

am set for auto updates but when checked manually the
same update will be applied.from 5727 to 5731.Is there a
problem?
 
The Franchise schreef:
am set for auto updates but when checked manually the
same update will be applied.from 5727 to 5731.Is there a
problem?
Click to expand...
Shutdown MS AntiSpyware. Right click the following and "Save target as..."
http://download.spynet.com/ASDefinitions/gcDeterminationData.gcd

http://download.spynet.com/ASDefinitions/gcThreatAuditScanData.gcd

http://download.spynet.com/ASDefinitions/gcThreatAuditThreatData.gcd

Copy/paste these files to Program files/Microsoft Antispyware

Restart MSAS and "check for updates".
 
I don't understand the directions - WHAT doyou right
click???

I was getting 5727 repeatedly, and today tried manual
update and got it up to 5731.

Am set to have the program check for updates upon bootup,
and let me know if there are updates. It's been doing
this for a week and only downloading 5727.
 
(e-mail address removed) schreef:
I don't understand the directions - WHAT doyou right
click???

I was getting 5727 repeatedly, and today tried manual
update and got it up to 5731.

Am set to have the program check for updates upon bootup,
and let me know if there are updates. It's been doing
this for a week and only downloading 5727.



and "Save target as..."
Click to expand...
Hello,

if you rightclick on the 3 links you get a window says:"Save target
as..." a window where you can choose where you want to place the file,
do that in C:\Program Files\Microsoft AntiSpyware\
after that restart MSAS and "check for updates".

Hope this helps.

Regards >*< TOM >*<
 
nope, that doesn't fix the problem, those definitions you
reference are version 5729, and even after manually
downloading/installing them (overwriting the old gcd
files), the MSAS updater, when manually invoked, will
attempt download/install version 5731 definitions
database, repeatedly, no matter how many times the updater
is launched.

btw, manually downloading files to update your security
software's database kinda defeats the purpose of an auto-
updater, now doesn't it

btw, i didn't have this outdated definitions problem until
i updated the MSAS program to the latest version last
week, at the request of a little MSAS notification that
popped-up in the corner of my screen... so, i obligingly
let it do its thing. in retrospect, it's probably not
such a good idea to whimsically do updates, and i can see
a time when hackers will find ways to exploit
the 'autoupdate' features that are becoming common in most
software now. how is one to be sure an update is legit,
particularly when everything is set to automatically
update? seems to me we're spending more and more time,
effort, resources, et al maintaining, updating and
securing our systems (windows) than we do actually getting
useful/enjoyable things done with the damn thing... but i
digress.
 
This problem has happened before with the last build.
That time running the installer and selecting "Remove,"
rebooting, and reinstalling fixed the problem, only it
won't work with this build.

Make certain that you are downloading all the files.
Also, if you get a "Page not found" error for one or more
of the files, change the http:// prefix to https://, as
this sometimes works.

Hope this helps.

ALan
 
I get the same problem. Everytime the program starts-up it
only loads the original spyware definitions 5727. A manual
update loads and installs the most recent spyware
definitions, currently 5731, which remains active during
the current antispyware scan session, but disappears again
the next time I reboot. I too am set for autoupdates, but
have been checking for updates just in case. This is
definitely a problem that needs fixing, particularly for
anyone counting on the active protection component using
up-to-date definitions.
 
alan,

thanks for the help, msas updater still won't successfully
update definitions to v5731, it reports success, but it
seems to 'forget' what it did. for example, i've shutdown
msas and run the updater 3 times, each time it
says, 'upgrading definitions version 5729 to 5731' i had
no problems manually downloading/overwriting those .gcd
(database) files, which took me from v5725 to v5729
definitions, but the updater still tries to install v5731,
repeatedly.
 
If this thread is still alive, please see the message from Robin Walker in
the .announcements group: "Definition update recycling - Permanent Fix."
July 9, 2005, 6:33 PM (EDT)


--
 
Back
Top