AutoUpdate Worked, but;

[Rob]

On Mar 5 I posted "AutoUpdate - Didn't".
Understanding that there is a "wonky" factor to the whole update process I manually dl'd
5697 the other day.
However, today it did do an AutoUpdate but said that it installed ver 5695.
I checked the MS kb
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

And found that I did indeed have 5697.
(going back to "about" I found that it had refreshed itself to 5697).

Given this is the 1st time the autoupdate has worked on my w2kPro m/c, is it a fact of
life that the autoupdate replaces the signatures "carte-blanche", i.e. it doesn't check
(like AdAware-"No updated components available", for ex.)?

 

[Bill Sanderson]

The update processes both run the same code, I believe--i.e. both AutoUpdate
and File, Check for update.

That code has an appearance bug, which you've just demonstrated.

I've yet to see a case in which newer definitions already present were
replace by older definitions--even via a program update installation, and
possibly even by a remove and reinstall. That part of the code seems solid.

 

[Steve Dodson [MSFT]]

The best way to verify the current version of the signature is to follow:
http://support.microsoft.com/default.aspx?scid=kb;en-us;892519 . We are
working to make the UI better in this respect

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.