Beta 1 v1.0.701

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Today I downloaded the update to bring AntiSpyware to version 1.0.701 but it
installed v1.0.615. It did not update the license expiration to July 31st,
2006 as it was supposed to. This happened on two Windows XP SP2 computers
and a Media Center SP2 computer. Is anyone else experiencing the same
problem?
 
What you downloaded, unfortunately, was .615

Please give it some time to percolate out to all the download servers--it'll
get there eventually.
 
Is anyone else experiencing the same problem?

Yes.

I downloaded and installed today (2005/11/22) and experienced the same
problem. I went back to the download site and re-ran the download/install
and it came up telling me that it was continuing an interrupted install.
This time it got all the way to a prompt to reset the computer. After the
system rebooted it is now at version 1.0.701 with the July 31, 2006
expiration date.

My recommendation: Try it again.

If it still won't work after two or three attempts, post your results.

HTH,
 
I have tried a number of times to update V 1.0.615 (uninstalling, cleaning
folders with msi install packages etc, but I still cannot get 1.0.710 and the
updated expiry date). I defintley have the updated .exe file with size
6,860,424 bytes, but it won't update.

Is this because I am in NZ and using a remote update server?

Regards

Roger Holman
 
I'm in the UK - same problem. tried downloading new version 5 times. Tried
uninstalling old version first. Still 1.0.615. Still 31 Dec 05 expire
date..........Losing the will to live here! Any other suggestions MS???
 
Hi Robb

Maybe your IE cache is overfilled with junk and
also include ver 1.0.615 ?

Remove this junkyard with CClenaer, www.ccleaner.com

Download again, save the file to desktop, do not run it from
download location. After download run setup.

Good luck.

--
plun




Robb wrote :
 
Come on MS. What gives. You published details of this update 2 days ago and
I still cannot get the supposed update that you recommend people use. Why
doesn't the .exe file in the download contain the new code. Some people have
obviously got it, why can't everyone. Are we supposed to keep trying a new
download or wait until the updating procedure in the original app works.

Please explain the process we are supposed to use and how it works and
advise asap.
 
I can't recommend anything except giving it some time. I had the same
problem, and I'm in the U.S. The third party download sites do seem to be
more reliable, but I'm not going to stoop to posting those here in public,
if I can help it.

--
 
Well, here it is on 2 December 2005 and I've downloaded the update from
Microsoft 4 times, (last time today) run cclean and it still won't update to
v1.0.701. I'm told that the update has taken, but no reboot message and when
opened it's still v1.0.615! Further when I try the auto update I'm told that
I have the latest software version installed. Nice to see I'm not alone...
Any suggestions?
 
You can't trigger the automatic update--going to File, check for update only
gets you definitions, not new code. (There are new definitions--5781,
fwiw.)

If you aren't behind a known caching server (some ISP's run caching servers,
I believe) then the best bet would be to go to a reputable third-party site,
I think. I'm not sure even that will work around an ISP cache.

Hmm--download.com is still showing the old version.
Tucows has something dated in February--surely that's expired by now!
Here--this should be good:

http://www.majorgeeks.com/download4466.html

Let me know if this works--I believe the issues are outside your machine,
but maybe I'm wrong!

--
 
It did thanks, seems that the mirror site is more up to date than nthe
official Microsoft site. The update files I downloaded from Microsoft
(latest today) were signed in July 2005, the one from the mirror site were
signed on 16 November 2005! Hardly fills one with faith in Microsoft!
 
The Microsoft download operation is not a simple single server, or even a
cluster of machines acting as one. I don't know enough detail to describe
it accurately, but I don't think the issue is an easy one to fix, or that
the problem is necessarily under Microsoft's control--there may be caching
servers at your ISP.

At any rate, I'm glad that the workaround solved the problem.

I agree with you--it is really against my principles to refer folks to a
third party site for a Microsoft Binary. I don't know if this worked simply
because the third party site worked around a cache somewhere along the line,
or whether there really is a server in a cluster or load balancing
arrangement somewhere which still has the old bits. It's annoying that this
is persisting now about two weeks into the availability of the new version.

--
 
Can you check with your internet provider about whether they are running a
cache of some kind?

--
 
Back
Top