Another Definition Problem

[ColTom2]

After manually downloading the new 5731 definitions on my
Sony desktop I go and run definitions update on my
Toshiba laptop and it indicates that definitions 5725 are
current. I reran the definitions update once again and it
showed updating to 5731. However, I go back and check the
definitions again and it indicates 5725 definitons are
installed and current.

I finally manually installed the 5731 updates.

MS had all kinds of defintion updating problems it seems,
including indicating that older definitions are current
when they are not. The MSAS program at this point is
totally unreliable.

 

[Guest]

This is a known bug for over a week and a
cumbersome "work around" has been posted in other
sections of this board.

I would guess that there might be an update to the
program to fix this at some point, but it may not be an
automatic download. There was another bug in this new
build for a day and it was replaced, but required a new
MANUAL download.

I'll just wait for a week or two for this bug to be
fixed, rather than mess with the "work around".

 

[Cliff]

I hope you are correct about another update soon (# 615?). Build 509 may
have had some problems, but it seems to be working ok for me and I just
updated to the latest definitions. " ... Spyware Version: 1.0.509 ...
Definition Version: 5731 (07/01/2005 11:43:30)" with no problems at all. I'm
certainly not going to download 614, given all the problems reported on
these sites. I also hope that on their download page they have clearer
instructions as to what's needed for an upgrade. I don't mind a manual
download, in fact I'd prefer it to trusting a balloon in the notification
tray on my desktop. I'd rather not have to uninstall the existing program,
however. But even that's ok if the instructions are clearly spelled out.
Most folks seem to be saying we need to uninstall the current program. If so
why isn't it clearly stated on the download page? (Don't bother to reply and
say only that "It's a beta") Given all the problems reported on these sites,
that's a cop out.)

Realizing that it doesn't catch as much as some of the other Antispyware
programs, I went with it because it was very easy to use. However these
latest upgrade problems are making me think that if there's not a better fix
before 07/31/2005, I'll just scrap MSAS.
/s/ Cliff

 

[Bill Sanderson]

I can guess at at least three different bugs in your narrative:

None of them is unique to this build.

1) the "sticky" update issue--the files really do not update
2) the update version appearance issue
The version number as shown in Help, About, may be erroneous--either
greater or lesser than the actual version.
3) A server-side issue in which a client with known to be out-of-date defs
querys the server, the server is too busy to reply (my guess) and the client
says --OK--nothing new to install.
If you repeat the same query immediately, you may well get the definitions.

I quite agree that this isn't confidence inspiring, but I also think that
there's no systematic problem with the build--I've yet to see the issue
first-hand. I haven't done a full migration to the new build 'cause I'm
trying to see how the auto-update works (and it is slow!)--however, all of
the dozen or so that I have done are behaving normally.

 

[Bill Sanderson]

Cliff - I wouldn't wait, myself. The only reason I haven't migrated every
machine I touch to the new build is to get a chance to watch the update
process work.

--

 

[Cliff]

Bill,
I guess I have an enforced wait, in that I'm going on vacation for awhile.

My question would be why would I want to upgrade when my build 509 seems to
be working fine and it continues to install the latest definition files. It
just seems like there are masses of people that are having problems and I am
not having any that I know of with build 509. I guess if there's an answer
to that question I might take a chance.

I suppose when I get back from another vacation in early August, I will
probably install whatever is the new build so I can be covered past the July
31 time-bomb date.

Thanks - It's good that you guys keep up with all this. I sometimes wonder
if the various "Forum Experts" ever get time to have any other life.

/s/ Cliff

 

[Tom Emmelot]

Bill Sanderson schreef:

Cliff - I wouldn't wait, myself. The only reason I haven't migrated every
machine I touch to the new build is to get a chance to watch the update
process work.

Hello Bill,

I did that and find out that if I Update all the files are here:

C:\Documents and Settings\Tom\Local Settings\Temporary Internet
Files\Content.IE5
So the are downloaded, but the install to the MSAS folder did not work!
So by hand I unzip them to MSAS and ready!
In C:\Documents and Settings\Tom\Local Settings\Temporary Internet
Files\, the are all in differend folders also with the .cat files and 1
other file that i dont now what it does.
So if you empty your IE5 folder and do the Update, you can find all I
talke about there.
I also use for update the old GIANTAntiSpywareUpdater.exe, but that wont
work eather.


With regards >*< TOM >*<

 

[Bill Sanderson]

The compelling change in 614 is if you use a vertical taskbar.

However, the improved handling of spyware removal which involves LSP's is
probably more important in the long run,

--

 

[Bill Sanderson]

I've now observed these files, and I believe that you are correct and that
these are the newer files which should be updating, but aren't.

I now have a test machine (my wife's!) which exhibits this symptom.

I want to get a chance to look at it and read the threads from Robin Walker
which may well have definitive information--i.e. I'd like to have the chance
to test whether his fix matches what I see, and fixes the issue.

--

 

[Tom Emmelot]

Hello Bill,

the problem is fixt by Robin, did some testing on that.
Had the old version so could do that from start, and it is correct!
I was near the solution but I forgot to look in the system32 directory
what happend there.
So Robin did a good job!

Regards >*< TOM >*<

Bill Sanderson schreef:

 

[Bill Sanderson]

I agree--every machine that I've seen the problem on has matched Robin
Walker's description, and the fix works. However, I've yet to get back to
my wifes machine!

--