Tried everything, but still having update problems.

[Guest]

I know this topic has been discussed to death, but I've followed every
suggestion that I've been able to find and I still am experiencing this
frustrating problem. I'm running XP Pro and was running Anti-Spyware
successfully for months. Today I "upgraded" to Defender and cannot get the
definitions to update. Each time I run the update (either from the main
screen or from the "about" screen) I get a systray dialog bubble indicating
that the program is checking for updates, and then 20 seconds later it tells
me that all of my files are up to date. However, I still have the little
splat castle in the systray, and on the main screen I'm told that my
definition/sig files are 83 days out of date. When I check in "about" I see
they are still version 1.0.0.0

I have installed all updates through windows update (express) and have
rebooted and reinstalled Defender. I have tried the "fix" in
http://support.microsoft.com/?kbid=915105. I have also tried a registry key
deletion that someone else claimed solved their problem. No luck.

Any suggestions would be helpful. I'm about ready to abandon this
frustrating program.

Thanks

 

[Guest]

I'm having the exact same problem. Also tried everything. Running Windows
XP Home.

 

[Guest]

Having the same issue. XP Pro SP2. Has worked at home just fine.

 

[Guest]

Well, now we at least have a quorum of folks with the same problem...we just
need an answer. Chris posted an idea in a thread above this one that I'm
going to look into, but it would nice if someone from MS would tackle this
one when they get a chance.

Best,

Mike

 

[Guest]

This time instead of doing the express install for windows updates (as
instructed in another thread) I chose "custom" install. Windows update
identified the required signature file update and was able to install it
successfully. I now have the latest definitions, but it would still be nice
if the auto-update feature in defender worked correctly.

 

[Guest]

hello SDMike1,
Have a look at this article. It may be relevant to your problem.
Subject: Was this Beta version released too soon?
4/18/2006 7:52 PM PST
By: Sam del Rico
In: microsoft.private.security.spyware.general

I hope this post is helpful.
Let us know how it works ºut.
Еиçеl

 

[Guest]

1. Do this: click Start, click Run, type Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}, and then click OK
2. Open Windows Defender. To do this, click Start, click Programs, and then
click Windows Defender.
3. Check for new definitions. To do this, click the Help options arrow next
to the Windows Defender Help icon, click About Windows Defender, and then
click Check for Updates.

 

[Guest]

1. Do this: click Start, click Run, type Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}, and then click OK
2. Open Windows Defender. To do this, click Start, click Programs, and then
click Windows Defender.
3. Check for new definitions. To do this, click the Help options arrow next
to the Windows Defender Help icon, click About Windows Defender, and then
click Check for Updates.

 

[Guest]

I have tried the above suggested method by Murray, I have tried the msiexec
/x AS_Sigs.msi method as well.

Result: Won't update: My sigs are older than 92 days.

 

[Guest]

OK, just tried the microsoft updates method suggested, and although it keeps
reporting that the update was succesful, I still have the same darn version!

Windows Defender Definition Update 1.14.1410.10 for BETA Windows Defender
(KB915597) Friday, April 28, 2006 Microsoft Update
Windows Defender Definition Update 1.14.1410.10 for BETA Windows Defender
(KB915597) Friday, April 28, 2006 Other Source

That's what the update history has been showing...

I have version:
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1372.0
Definition Version: 1.14.1410.10

any more suggestions folks?

 

[Guest]

Hello Frustrated,

You are all set.
WD v. 1.1.1347.0
Engine v. 1.1.1372.0
Signature v. 1.14.1410.10 created on 4/26/2006 at 8:33PM

 

[Guest]

I had similar issues and could never get WD to update to the most current
version. The only way I was able to resolve it was to "force" an update from
the MS Update website located here:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

When I did this, it recognized I had WD and then downloaded and FINALLY
installed the correct version. Nothing I did with WD fixed the non-updating
problem I had and I did everything everyone suggested on this forum --
multiple uninstalls, deleting folders, running msiexec, etc. The only thing
that fixed it was going to the above website and letting it download the
correct updates.

Joel