Same problem AGAIN with new defs 5739

  • Thread starter Thread starter Quaid
  • Start date Start date
Q

Quaid

I cant understand why MS cant get this issue fixed as
this seems to be happening more often, what up guys????
and for people who dont know much about computers can
someone explain step by step how to correct it. THANKS
 
Did you download the latest Microsoft antispyware software
version 1.0.615 If you did, it then should be fixed.
 
Quaid said:
I cant understand why MS cant get this issue fixed as
this seems to be happening more often, what up guys????
and for people who dont know much about computers can
someone explain step by step how to correct it.
Click to expand...

The problem can occur because the way in which MSAS makes web
requests (HTTP) means that it is vulnerable to being served stale versions
of any file from any web cache between MSAS and the actual update server.
Those web caches could be:
- on the user's own PC (e.g. Temporary Internet Files);
- within the user's ISP's infrastructure;
- maybe within Microsoft's or Akamai's infrastructure;
- the update server farm might itself be a load-balanced cluster of web
caches in front of the true update server.

The first of the list above can be fixed by the user emptying their
Temporary Internet Files in control panel Internet Options. Apart from
that, there is no work-around for the normal end-user.

Everyone is going to have to get used to definitions updates failing until
all those web caches have refreshed themselves.

So don't rush to be an early adopter of new definitions versions.

The recent pattern is fairly clear: updates seem to be issued sometime on
Thursday Redmond time: Europe sees them sometime overnight before breakfast
on Friday morning. It would be sensible to set MSAS scheduled updates for
sometime on Fridays, by which time most caches should have refreshed.
 
Robin.

I have the same issue but the right file are being downloaded (with build
615) cause after running the update on an empty cache i went to the folder
where the files are and extracted them and then when i replaced the old dats
in the antispyware folder with the newest ones. and then the update stopped
recuring so the right files are being downloaded just not updating.
 
DKI said:
I have the same issue but the right file are being downloaded (with
build 615) cause after running the update on an empty cache i went to
the folder where the files are and extracted them and then when i
replaced the old dats in the antispyware folder with the newest ones.
and then the update stopped recuring so the right files are being
downloaded just not updating.
Click to expand...

Look in the MSAS "errors.log" file: at the end you might find errors
realting to "WinTrust", indicating that the downloaded files were found to
have SHA1 hash checksum failures when compared with the expected values in
the Microsoft-signed catalog files. Again, this can be because the .cat
files were stale in a web cache.

Presumably you un-zipped the *.gcz files to *.gcd?

Look for the *.cat files in your Temporary Internet Files to check for
yourself.
 
-----Original Message-----
Quaid said:
I cant understand why MS cant get this issue fixed as
this seems to be happening more often, what up guys????
and for people who dont know much about computers can
someone explain step by step how to correct it.
Click to expand...

The problem can occur because the way in which MSAS makes web
requests (HTTP) means that it is vulnerable to being served stale versions
of any file from any web cache between MSAS and the actual update server.
Those web caches could be:
- on the user's own PC (e.g. Temporary Internet Files);
- within the user's ISP's infrastructure;
- maybe within Microsoft's or Akamai's infrastructure;
- the update server farm might itself be a load-balanced cluster of web
caches in front of the true update server.

The first of the list above can be fixed by the user emptying their
Temporary Internet Files in control panel Internet Options. Apart from
that, there is no work-around for the normal end-user.

Everyone is going to have to get used to definitions updates failing until
all those web caches have refreshed themselves.

So don't rush to be an early adopter of new definitions versions.

The recent pattern is fairly clear: updates seem to be issued sometime on
Thursday Redmond time: Europe sees them sometime overnight before breakfast
on Friday morning. It would be sensible to set MSAS scheduled updates for
sometime on Fridays, by which time most caches should have refreshed.

--
Robin Walker [MVP Networking]
(e-mail address removed)

Thanks for the info Robin, i will delete temp.internet files and hope that works.
Click to expand...
 
I understand what you're saying about the various caches, but why do I only
see this issue with MSAntispyware? Lavasoft, Spybot, Symantec, and even
MSupdate don't have this problem - do they use a FTP or some other method?

I'm just curious -- thanks for you help and dedication to this forum!
 
The beta product is based on unique code created by a third-party. There's
at least one other product out there based on this same code, so perhaps it
has a similar issue.

We may well see a significantly different mechanism in beta2.

--

Rusty said:
I understand what you're saying about the various caches, but why do I
only see this issue with MSAntispyware? Lavasoft, Spybot, Symantec, and
even MSupdate don't have this problem - do they use a FTP or some other
method?

I'm just curious -- thanks for you help and dedication to this forum!
Click to expand...
 
Back
Top