Update problem Def.5693

  • Thread starter Thread starter Gus
  • Start date Start date
G

Gus

I updated from definitions 5691 to definitions 5693 it
downloaded and installed OK.(2/25/05)
But now if I try to update manually it shows that is
downloading and installing def 5693 from def
5691.Microsoft AntiSpyware Version:1.0.509
Diagnostics OK.O/S WinXP SP2.Anyone has the same
problem?
 
The same thing is happening to me. Now every time I click
to check updates it wants to reinstall 5693.

delta
 
Can you note down the sequence of messages that you see--and roughly how
long they take? Does this go by quickly, or does it really look like it is
downloading the definition files?
 
There's a bug which shows the version in place wrongly--both in the messages
at completion of Automatic Update, and in what is shown in Help About.

The version in place is actually correct, but the version number is off in
both those locations.

If you then do a manual check--file, check for updates, you can see that no
update takes place--you don't see the update checking and installation
lines--but you get two stars for being current. You then go back to Help,
About, and this time the correct version number is shown.

This is how it has always worked for me, but I do see a couple of threads
today which seem a bit different, so I may need to back off on my statement.
 
Yes it does go through the update sequence.It says
updating from 5691 to 5693 and then goes through the
install process just like it always does. When I check
the version it will list 5693 with the last time I
updated. I tried again a few minutes ago and it again
updated to 5693 with the current time.

delta
 
I haven't seen this reported before--congratulations!

I'm looking at this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

and going to update for the 5693 files on my system--maybe we can compare:

HMMMMMM......
OK--looks like there's a new bug here.

The files "on the ground" are:


02/17/2005 02:59 PM 2,143,028 gcThreatAuditScanData.gcd
02/17/2005 02:59 PM 1,253,851 gcThreatAuditThreatData.gcd

Which are 5691, according to the KB article. But Help About, and all the
updates, say that I am on 5693, and have since 1 am last night.

Thanks for the reports, and for kicking me to actually check my own machine!
 
OK--now I'm totally confused.

I thought I'd try to figure out how to fix this issue. I looked at a couple
of other machines, and they had the right files laid down for 5693--or at
least plausible dates and sizes, etc.

So--I went to my installation directory, shut down Microsoft Antispyware,
and deleted those two files. I was interested to see what would happen.
What I expected, was that those files would be regenerated in the 5687
version which I understand is packaged with the download.

When I restarted Microsoft Antispyware, and looked at that directory, here's
what I found:

02/24/2005 12:56 AM 2,152,324 gcThreatAuditScanData.gcd
02/24/2005 12:56 AM 1,255,694 gcThreatAuditThreatData.gcd

I haven't double checked, but these look like 5693 to me.

So I don't know what's going on here, but that experiment may be a useful
one for those who are not getting proper updates to try.
 
This is what I did to stop it from reinstalling 5693. I
turned off AntiSpyware and then deleted the two files in
my temp folder. I restarted the computer and went to
update and it said I am current. I also checked and I
have 5693 installed.

delta
 
Hmm - so you found definition files sitting in TEMP? I don't think I
checked to see what was there. If I find this issue on another machine,
I'll remember to check that out--thanks.
 
You need to turn off the program to delete them or you
get "can't delete, files being used by a program". Once
you turn it back on it just recreates two new files.

delta
 
ooh--and those two are probably the two files that everyone complains about
that are left orphaned after a given run!

Interesting. And surely a dynamic Microsoft has got a handle on and will
get fixed with a major rev of the beta.
 
Back
Top