The MS AntiSpyware updates do not install and it freezes

[Helper]

When i go to update MS AntiSpyware it comes up, and if
there are new updates it goes a head and updates them,
but as it is, the screen freezes and i have to use
ctrl+alt+delete to get out of it. When i go back on it
says the updates are installed. Plz help.

 

[plun]

Hi

House clean your PC with CCleaner and remove
all junk. www.ccleaner.com

Also use Lavasoft Adaware.
http://www.download.com/Ad-Aware-SE-Personal-Edition/3000-8022-10399602.html?tag=list

Now your freezes probably are gone after CCleaner and Adaware.

 

[Bill Sanderson]

If you go to Help, About, in Microsoft Antispyware, what definition version
do you see?

Currently, 5761 is the latest.

If you see that, the update has worked. I wouldn't worry about the freeze
at this point--you've got the update. Lets see what happens next week.

 

[Dave M]

Bill;
I think you might be having the signature update problems that many are
having here. My definitions are at 5763, and have been since September
29th.. But it required a Manual overlay Update from Spynet to avoid
repetitive updates of 5763.

 

[Bill Sanderson]

I'm not sure whether it was lack of sleep, or the appearance bug that lead
to that post--sorry about that. Here's what it really says, at the moment:

Microsoft AntiSpyware Version: 1.0.615
This version expires on: 12/31/2005
Spyware Definition Version: 5763 (9/30/2005 2:57:54 PM)


--

 

[Dave M]

What I was seeing were repeated downloads of the SAME definitions, no mater
if MSAS said it was at (5763 or 5761)... seemed to depend on if MSAS was
terminated or not, as to what MSAS claimed even before any downloading takes
place. If you get another download of 5763, you do in-fact have the
problem, just hit the check for updates again, maybe shutting down &
re-starting MSAS between, betting that you get another download, and
another if you do it again. I never was able to fully trace why this was
happening even though I spent a lot of time on it (see General Forum on 9/29
by Connor "New defs question..") although I suspected it was the way
Diagnostics show Definitions Increment Version: varying between 114/114,
114/116, & 116/116
and maybe it will self-correct in the next update cycle, although I was able
to overcome it by doing a Manual overwrite download, yet there are a large
number of these problems happening spread around these discussion groups,
some may not even realize it yet, so I really think it should be bug
reported, however one does that in this Beta... Yes I know... somebody at
Big Brother is listening...

 

[Bill Sanderson]

They are listening, but I believe that they are also convinced (I think
rightly...) that there's nothing that needs fixing.

I know that sounds cold in the context--You've seen this, I've seen it (many
months ago) and there were a few builds--613,614--where lots of people saw
it--but the causes are not always the same, and they aren't necessarily at
the client end--sometimes they appear to be at the server end.

Additionally, this beta1 code will probably not be used beyond the next
three months, if all goes according to plan--so even if there is a bug that
has this result for a few people, it isn't likely that they would rev the
beta code, encouringing an update by all 18,000,000 users.

You definitely saw a glitch on this update--this kind of glitch has occured
throughout the beta--all the way from January 'til now. In some cases, it
seems to self-correct, and for others--well--all the right advice was
posted, and you took it!

I don't think this kind of issue will carry over into beta2--but there will
probably be something else to help relieve the boredom!
--