New definitions just released, 1.14.1315.1

  • Thread starter Thread starter History Fan
  • Start date Start date
Thank you.
Yeap, the AutoUpdarer kick in with
Definition Update 1.14.1315.1

Actual
WD version 1.1.1051.0
Engine version 1.1.1186.0
Signature version 1.14.1315.1

No problems.
 
Good for you - BAD for me. Same old problems here - updates show but won't
install on either computer - what is going
on???????????????????????????????????????????
I have uninstalled and reinstalled on one pc and the other was an upgrade
from MSAS which worked fine until 1.14.1314. Seems like someone could get
this right JUST ONCE!
 
same here.received 1.14.1315.1 via auto updates.no looping and quick scan
went well with no problems.best regards
 
Windows Defender Live (Beta 1), help needed from Microsoft.
Except for the new download Signature Version 1.14.1314.1, all previous
versions have fallen into a loop to High Priority Definition Update
1.14.1314.1 for Beta Windows Defender (KB915597). The users of the Windows
OneCare Live (Beta) have downloaded automatically the file in excess of 54
times, as per the Update History, with no positive results. Previous results
of the Windows Defender (Beta) Definition Updates that worked are:
1.13.1276.3, 1.13.1272.4, 1.13.1276.16, 1.13.1282.6 and 1.13.1386.1 with KB
892519, 892519, 892519, 915597 and 915597 respectively. The loop failure
started when trying to update to 1.13.1288.5 and 1.13.1314.1 both with
KB915597, from older Signature Versions. Worst of all, no removal of the
Defender beta is possible nor installation of the newer 1314 version ontop of
the other.
Microsoft, please read also the many complains in the Discussion Groups Home
 
Well, as usual, I can't update via autoupdates or via the app. As I
recall, last time I got the update by somehow removing the previous
signatures, but I've forgotten how to do that. What was the trick again?

Dazd
 
Bill said:
http://support.microsoft.com/?kbid=915105
Click to expand...

Thanks, Bill. That did it again, and I've now also bookmarked the MS
fixit webpage for next time :P But it's certainly not too good to have
to update like this every go-round . . . And unlike who the fix is
supposed to be for, this is not a reinstalled Defender; nor have I ever
had the MS Anti-Spyware on this system. It is a first-time install of
Windows Defender on a practically brand-new clean installation of Win2K.

Daze
 
This fix is more broadly applicable than the particular issue that is
described in it--I understand that you probably haven't done the thing that
it is "labelled" for.

I also understand that it is bad that this experience repeats for some
users. It is an occasional experience for some users, and a very few users
have seen it more than once--and many users (based on my own experience with
perhaps 4 dozen users)--don't see it at all.

I don't have any knowledge about the root issues that cause this problem.
There was a Microsoft post in these groups (or perhaps somewhere else I was
reading) that stated that they had "fixed" a number of update-related
issues. Such an announcement may indicate that fixes have been checked into
the code base, but are not yet available to the rest of the world--as far as
I can see, no code changes have been distributed to the rest of us since
that statement was made.

--
 
Bill said:
This fix is more broadly applicable than the particular issue that is
described in it--I understand that you probably haven't done the thing that
it is "labelled" for.

I also understand that it is bad that this experience repeats for some
users. It is an occasional experience for some users, and a very few users
have seen it more than once--and many users (based on my own experience with
perhaps 4 dozen users)--don't see it at all.

I don't have any knowledge about the root issues that cause this problem.
There was a Microsoft post in these groups (or perhaps somewhere else I was
reading) that stated that they had "fixed" a number of update-related
issues. Such an announcement may indicate that fixes have been checked into
the code base, but are not yet available to the rest of the world--as far as
I can see, no code changes have been distributed to the rest of us since
that statement was made.
Click to expand...

Thanks for the comments, Bill. Although I often install protective apps
on my clients' computers, I will be reluctant to pass around Windows
Defender until this updating issue is resolved and I'm able to feel
fairly confident that it can take care of itself. I understand that it's
still in Beta . . .

Daze
 
I've got it on about 50 machines. The worst issue I've seen with it is that
on about 4 of those, I found definitions weren't updating. None of the
users had noticed, and I simply applied the KB 915105 fix and moved on when
I encountered it. This was a one time issue on those machines, I
think--I'll check them over thoroughly again this Tuesday and Wednesday.

--
 
Hello Bill,

i just lookt to the System event and find out that every update take
about 3/4 shots to stick!
Yesterday it wont work even if i go to the download site, this morning
after have a hour i lookt to the system event and there i saw that the
update was done.
So i think the problem is that to many people try to update at the same
time.

Regards >*< TOM >*<

Bill Sanderson schreef:
 
I don't have a sense of what the underlying problems are at all. There was
a post from a Microsoft Staff person stating that they'd fixed some bugs
relating to updates.

I don't know whether the fixes are at the server end or at the client end.
No new code for clients has been distributed since that statement was made.

--
 
Back
Top