Trouble updating??

[Guest]

When I check for updates I "always" get the same
notification that the program is updating from 5741 to
5743. It says the update is completed and installed, yet
when I then do another update, it gives me the same thing.
In other words, 5743 downloads and installs, yet it is
never identified as doing so. Any suggestions what I can
do to keep current? It doesn't seem to apply update 5743
for some reason. Thank you for any help or suggestions.

 

[Bill Sanderson]

I'd recommend ignoring this for awhile--if it is still happening on Monday,
we can look more closely.

 

[Guest]

Ok, funny thing I should also mention, I checked my version
and it's the latest. It also shows that it's running on
spyware deffiniton no. 5743. That's the same one that it
continually tries to update to. In other words, it seems
like it has but it's not recongized as having done so.
I'll sit tight, it always updated fine before. Must be a
glitch in this particular update. Thanks!!

 

[Bill Sanderson]

You can check this article:

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

once it gets updated. Steve Dodson says he hopes to get to it soon......

It gives the info you need to spot whether the files actually in place are a
given version of the defs.....but not 'til it gets updated!

--

 

[Guest]

-----Original Message-----
When I check for updates I "always" get the same
notification that the program is updating from 5741 to
5743. It says the update is completed and installed, yet
when I then do another update, it gives me the same thing.
In other words, 5743 downloads and installs, yet it is
never identified as doing so. Any suggestions what I can
do to keep current? It doesn't seem to apply update 5743
for some reason. Thank you for any help or suggestions.
.

 

[joe]

I notice the same problem updating, updates to 5743 then
when I try another update it downloads it again. Had the
same problem with the old version but issue was fixed
when I downloaded the upgrade. This is the first time it
did the same thing again with the new version. Appears
to me to be an ever ongoing problem with the updater. Do
you think they will eventually realize what the problem
is and eventually fix it with the next update. Any other
solutions?

 

[Bill Sanderson]

I think that the difficulty with this symptom is that it can have multiple
causes. The original problem with build .614 (and perhaps .613 for all I
know) was that a file wasn't properly replace in the upgrade process because
of a version numbering issue.

That was the change made to .615--a version number change.

Various other causes have been posited--issues with temporary file
locations, local or ISP caches, and perhaps Microsoft's load balancing
processes--or worldwide distribution of download sites.

As I've said before, this issue has been seen at times throughout this beta.
Clearly there's a systemic problem, but I don't think it is necessarly on
the local machine at this point.


--