Update/upgrade problem

[Guest]

I had a message from MSAS yesterday on both my PCs saying a newwer version
and asking me to install it. On one PC the worked correctly and gave me
version 1.0.701. On the other PC the installation hung at verifying the
install; when I hit Cancel repeatedly it allowed me to Quit or Resume. Resume
didn't help so I used Quit. MSAS said it had done the update and I was
protected but that PC still has v 1.0.615 and MSAS didn't actually continue
running; I had to restart it by hand.

1 This isn't helpful behaviour; a naive user would expect they were
protected. I suspect the problem is in the Windows Installer (a program from
Macromedia failed to install on the same PC on the same day) but the
successful update message shouldn't appear unless I'm actually sucessfully
updated!

2 I clicked the spyware definition date to check for updates and it says the
Most recent softwre is installed even though the version number hasn't
changed. How do I get v 1.0.701?

 

[Guest]

thanks - I was able to get it to install from the download just fine. But I
still think that telling me I'm updated when I'm not and refusing to find the
update from the program counts as a bug!

I also wonder if it's a good idea to get updates from a non MS site? I know
bandwidth can be a faff on MS, and MajorGeeks is a good site, but I think
it's a good idea to only trust MS downloads from the MS site. There's a fake
SP3 floating around now!

 

[Stephen Boots MVP-MSN Client]

I received the update 3 times via the notification that a newer
version was available. It downloaded, installed, and announced that it
was successfully update. However, it was not.
Shutting down AntiSpyware and manually pulling the download and
installing allowed it to upgrade. A reboot and I'm back in business.
-steve

 

[Bill Sanderson]

That's interesting. I don't know where the autoupdate pulls the bits from.
If it is getting them the same place as the rest of us, and if it really is
the case that there are some caches still handing out the old version, that
might explain your failures.

Mary--doing File, check for update ONLY checks for definition updates as far
as I've ever been able to determine. To get the program bits, go to the
download center.

I absolutely agree with your thinking about 3rd party sites. However, I've
been forced to make this suggestion a couple of times here, in situations
where a user has apparently repeatedly tried to get the bits from the
download center and always ended up with the old version.

I don't know whether this is a failure with Microsoft's download system, or
a cache somewhere that going to the different site works around--but it has
helped, to my dismay.

 

[msnntp]

As of a few minutes ago, the MS site is still distributing build 615 , not
the 701 build.

I finally got the file from majorgeeks.

Of course, I still have the error 1904 issues with build 701.

Lyal

That's interesting. I don't know where the autoupdate pulls the bits from.
If it is getting them the same place as the rest of us, and if it really is
the case that there are some caches still handing out the old version, that
might explain your failures.

Mary--doing File, check for update ONLY checks for definition updates as far
as I've ever been able to determine. To get the program bits, go to the
download center.

I absolutely agree with your thinking about 3rd party sites. However, I've
been forced to make this suggestion a couple of times here, in situations
where a user has apparently repeatedly tried to get the bits from the
download center and always ended up with the old version.

I don't know whether this is a failure with Microsoft's download system, or
a cache somewhere that going to the different site works around--but it has
helped, to my dismay.


--