Update does not work, old definitions remain in place

[Guest]

I have seen the posts about clearing the cache to allow updates to be
downloaded. I have done this and it still does not work. The only way I can
see of updating the definitions is to re-install. Have I missed something.

 

[Tom Emmelot]

Hello MikeP,

the version number of MSAS is that 6.15??
See Help/ About in MSAS.

Regards >*<TOM >*<

 

[Guest]

Reinstalling won't necessarily fix this--the definition version is the same
as the week the install file was posted, I think--back in July.

If you go to Help, about, do you see version .615?

If not, please go to www.microsoft.com/spyware/software and download and
upgrade.

If you do see that version number, then you are on the current version, but
there's something amiss--and this is what I'd try to see if it takes care of
it:

1) uninstall Microsoft Antispyware
2) delete \program files\microsoft antispyware and subfolders. You'll lose
access to any quarantined items, and customized settings and history
information.
3) reinstall Microsoft Antispyware, being certain to be logged in as the
administrator level user who will customarily use the program.

 

[Guest]

Bill,

I am on 1.0.615. I only downloaded it this Tuesday 25th. When I installed
the same file on another PC yesterday (26th) it updated to the next level of
updates dated 26th. I had exactly the same problem when I installed the
software earlier this year.
This seems to show that the updates can get through the network and firewall
OK. I do not have problems updating other antispyware or AV products.

The PCs are Windows XP Pro SP2 + latest security fixes. I have not yet
tested it on XP Home.

I will do what you suggest, but based on the other PC, I think it will maybe
update once then stop. Whatever, I will post the results when I get time to
try it.

 

[Dave M]

Mike, just curious, are you on a dialup access? I have trouble with signature
definition updates myself, and believe it's related to my slow connection
bottleneck. I just keep re-trying (sometimes like 12 times, sometimes once),
and eventually it takes. TIA for your response.

 

[Guest]

Dave,

In both cases it is via a LAN and a fast ADSL line.

Mike

 

[Bill Sanderson]

If it updates once, it should continue to do so in the future. There are a
variety of issues involved in the failed updates--some of them outside your
control, but there is nothing permanently broken about the current build
which has been out since July 18th.

Beta2 is coming soon--and I suspect it will handle this function much more
smoothly.

--

 

[Guest]

One other thing to remember: On average, updates have been approximately
weekly, usually sometime late afternoon, early evening Thursday, sometimes on
a Friday or Saturday.

There's an update process that is part of the startup at install time--so
that it appears that the app is up to date as downloaded, but that really
involves a new definition download--just an invisible one.

 

[Guest]

Bill,

Thanks for your help. I still have an issue with one PC on definitions dated
26th and another on 25th (same software install, different definition
builds), and the one dated 25th consistently fails to update to the 26th.

Hope Beta2 resolves this. It is a shame that this is happening, because it
looks very good otherwise.

King regards.

Mike

 

[Guest]

In resistant cases, in addition to clearing out Temporary Internet Files,
some have found that manually updating the files helps. I'm not sure I've
ever done this myself--but at least it gets you the right files in place:

Here's Engel's description of the process:
---
There is a manual update procedure. Follow these steps:

Right click on MSAS icon within systray and choose
shutdown.

Right click and "Save target as..."

http://download.spynet.com/ASDefinitions/gcDeterminationDa
ta.gcd

http://download.spynet.com/ASDefinitions/gcThreatAuditScan
Data.gcd

http://download.spynet.com/ASDefinitions/gcThreatAuditThre
atData.gcd

Copy/paste these files to Program files/Microsoft
Antispyware

Restart MSAS and "check for updates"

If the http:// does not work, try https:// instead..