Update 5735 causes loop

  • Thread starter Thread starter KM1
  • Start date Start date
K

KM1

I have two computerw with the newest version of MSAS,
1.0.614, which was downloaded clean on a freshly
formatted machines. I have experienced the download loop
before with the older version before the reformats but it
usually took care of itself the next day. Today I
checked for an update, found one 5733 to 5735, updated
both machines, restarted, checked again and instead of
getting the MSAS is uptodate it updated again from 5733
to 5735. Did this on both machines. Checked in about
MSAS and it says it is using the new definitions with
todays date but everytime I check for updates it redose
the update. Will this fix itslelf on its own as in the
past? Am I truly up-to-date? The fix mentioned in this
newsgroup does not seem to apply to me because I have
downloaded the newest version on a fresh machine. What
should I do???

KM1
 
-----Original Message-----
I have two computerw with the newest version of MSAS,
1.0.614, which was downloaded clean on a freshly
formatted machines. I have experienced the download loop
before with the older version before the reformats but it
usually took care of itself the next day. Today I
checked for an update, found one 5733 to 5735, updated
both machines, restarted, checked again and instead of
getting the MSAS is uptodate it updated again from 5733
to 5735. Did this on both machines. Checked in about
MSAS and it says it is using the new definitions with
todays date but everytime I check for updates it redose
the update. Will this fix itslelf on its own as in the
past? Am I truly up-to-date? The fix mentioned in this
newsgroup does not seem to apply to me because I have
downloaded the newest version on a fresh machine. What
should I do???

KM1
.
More info:
Click to expand...

I tried the fix offered on one computer and it did work
however, when I went to check the updated version for
gcDeterminationData.gcd it was still at 07/08 and not
07/14. The other two, gcThreatAuditThreatData.gcd and
gcThreatAuditScanData.gdc, were at 7/14. So I went to my
other machine and checked the dates on these three files
and the gcDeterminationData.gcd and
gcThreatAuditScanData.gcd, were up to date while the
gcThreatAuditThreatData.gcd was at 07/08. what gives
with this. So the fix did stop the loop on the one
coputer for the time being but only two of the files
mentioned where updated. On the coputer that was left
alone, two of the files mentioned were up to date while a
different one was set at 07/08. What should I do at this
point? Will this be taken care of on its own as in the
past and will these files update eventually???

KM1
 
KM1 said:
I tried the fix offered on one computer and it did work
however, when I went to check the updated version for
gcDeterminationData.gcd it was still at 07/08 and not
07/14. The other two, gcThreatAuditThreatData.gcd and
gcThreatAuditScanData.gdc, were at 7/14.
Click to expand...

Check the errors.log file in the folder C:\Program Files\Microsoft
AntiSpyware\

At the end, you might find error messages explaining what went wrong with
this update.
 
Well, I know that Andre........... ;)

It always works! But is a stupid way to
get definitions, MS knows about this so
open an official manual download link until
next release is ready.
 
Back
Top