Signature Version 1.14.1315.1 issue

[Guest]

My Windows Defender details:

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.14.1288.5

When I do an windows update, the signature version 1.14.1315.1 gets
downloaded and even after successful install, the version of WD is not
updated and again n again the same version gets downloaded.

Is there any solution to this?

 

[Bill Sanderson]

Use the resolution steps in this document, even though the premise does not
apply to your situation, necessarily.

http://support.microsoft.com/?kbid=915105

 

[Guest]

I also had this problem, with 7 "successful" updates using Automatic updates
and manual updates. The solution listed above worked. I stopped the Defender
program, and restarted it after using Bill's suggestion - the signature was
updated. Thanks.

Robert Laughlin

 

[Bill Sanderson]

Glad to hear it. I hope this won't recur--it does for some, but not all.

--

 

[Guest]

If I may add to this thread - I had the same problem, and followed Bill's
advice to follow the instructions in KB915105. The problem was solved.
However the cause of the problem seems to be that although the signature
update downloads and installs, it does not overwrite the previously installed
update, and thus Defender reports definition files are out-of-date. Removing
the earlier update, via instructions in KB915015, permits the later update to
be visible to Defender's alert program. I hope that this type of problem will
not recur with each signature file update?

 

[Bill Sanderson]

I don't have enough experience yet with the new version, I've seen this on a
few machines, and I don't believe it has recurred--but some users here have
seen it recur.

--

 

[Guest]

Thanks Bill..that worked. But I hope with these kind of issues, one must keep
searching more rather concentrating in securing his/her PC

Sri

 

[Bill Sanderson]

The update mechanism--AutoUpdate--has been around for a good long time, and
is in use by a large volume of users already. I'm not sure what the issues
are that make these updates different--certainly the volume of failures is
far higher than, say, the monthly security patches--but I suspect they are
getting lots of attention from the development team.

There's been a MSFT post stating that they have fixed some update-related
bugs. Since that post, no new code has been distributed--so I think it is
likely that there are some fixes we haven't seen yet.

--

 

[SteveC]

Well, I hope they provide an update fix soon; it is showing up on more and
more computers now that I work with.