Defender Update...download page?

[Guest]

Currently all machines w/ defender are requesting update via the download
button...but is navigating me to the download Beta 2 defender. I currently
have defender beta 2 with version 1.14.1525.2 running on the machines.

 

[Dave M]

There is a new notification in place. It is in fact asking you to update
Windows Defender to version 1.1.1347.0 at the download site, this GUI
version is not updated by using the definition/engine Check for Updates
button that is on Help > About. Simply install the new download over the
version you are currently using. Following that update you should check
your Defender options since some will have changed, for instance the
ability to always show the WD icon in the notification area. Pay
particular attention to your Spynet level of membership as well, since it
probably has been reset to basic.

 

[robin]

I am wondering if they fixed the restore points yet
robin

 

[Guest]

In addition to Dave M mentioned:
Version 1.1.1347.0
http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en
Users who normally select advanced Spynet membership should be aware that
the install process will set you back to basic membership, so it's a good
idea to revisit both the Spynet membership area of Tools, and the Options
area--to see what's different, and check that your old choices have been
preserved.

 

[Bill Sanderson MVP]

No. This update takes users of 1051 code to 1347. I believe many here are
running 1347, and have not found that it fixes this issue, which not
everyone sees.

--

 

[Larry]

".......which not everyone sees."

Is there an XP HE SP2 user out there who doesn't get multiple restore points
created daily?

 

[Bill Sanderson MVP]

Sure--my wife's machine upstairs, and a few laptops I've seen. I'll admit
to not going looking for this symptom on every machine I touch, but I've not
found it on any that I work with --which I'll admit are 99% XP Pro--and are
office desktops, rather than home machines.

I'm reasonably certain that this issue results from some interaction on the
machines it is seen on--not sure whether it is other software, hardware
drivers, or what--but it isn't seen by most users, I'm quite sure.

--

 

[Larry]

"--but it isn't seen by most users, I'm quite sure."

You may be right, but I doubt it. I'm of the opinion the multiple daily
restore point creation is very common behavior. Let's hear from some others.

 

[Guest]

"--but it isn't seen by most users, I'm quite sure."

You may be right, but I doubt it. I'm of the opinion the multiple daily
restore point creation is very common behavior. Let's hear from some others.

There are complaints about this issue all over these Defender newsgroups,
and the seriousness of the issue for those of us who do experience it has not
been fully appreciated yet, in my opinion.

I believe one reason why 'most users' aren't seeing it is because if they
don't check these newsgroups, why on earth would they think to check whether
their system restore points are multiplying? I suspect there are thousands,
possibly millions, of users of Defender, already, who have no 'ordinary'
restore points left because they've all been replaced by Defender
checkpoints. They can no longer restore their systems to a pre-Defender
state, should they need to do so (as per Microsoft's recommendations if
problems arise). That's why I've switched off RTP on Defender. It'll stay off
until they fix this bug.

Microsoft say they don't know why the checkpoints are being created. But if
this issue can be fixed by a registry edit that's already been offered (those
who have tried it report that it works), then why can't it be fixed by a
download patch so that we no longer have to be troubled by it?

In my case the cause of many of the checkpoints seems to be an interaction
with an AOL driver, which Defender doesn't like. But surely the checkpoint
production could be over-ridden by just telling Defender that one checkpoint
per day is enough? Who needs 8 checkpoints per day, no matter how infested
with malware their machine might be?

 

[Bill Sanderson MVP]

I have not heard Microsoft say that they do not know why these checkpoints
are being created.

I don't know--but I am not "Microsoft."

I'm quite sure that Microsoft is aware of this situation.

--

 

[Guest]

I have not heard Microsoft say that they do not know why these checkpoints
are being created.

Sorry Bill, I was being imprecise there. Joe Faulhaber mentioned it in a
post a few days ago, and I incorrectly equated him with Microsoft. Apologies.

 

[Bill Sanderson MVP]

Hmm--it's OK to equate Joe Faulhaber with "Microsoft" I think--I'll check on
what he said--maybe I'm wrong!

--

 

[Guest]

Hmm--it's OK to equate Joe Faulhaber with "Microsoft" I think--I'll check on
what he said--maybe I'm wrong!

Bill, it was in the 'Hidden update button' thread, started on 2nd July.
Joe's post about the checkpoints not being completely understood was on 7th
July in that thread.

 

[Bill Sanderson MVP]

Thanks very much Alan--I was away on vacation from 6/23 'til 7/9 or so, and
hadn't read that message yet--and it is an interesting one. What he says
about the race to get systems patched ahead of the malware folks reverse
engineering the patches is very true, and I'm glad to hear that Defender is
one of the front-line protection mechansms for that situation.

The way I read his message, Microsoft is very clear about the code in
Defender that is creating the restore points--they just aren't clear about
why that code is getting triggered so often on some machines. They have new
code not yet released (this is not the code in the 1347 build update that
some users are currently seeing notices about)--which will alleviate this
symptom further, but not as completely as they would like.

I hope you'll stick with us and watch for that new code to be released, and
see how it does on your systems--clearly they are working on the problem.


--

 

[Guest]

I hope you'll stick with us and watch for that new code to be released, and
see how it does on your systems--clearly they are working on the problem.

I'm still intend to go on using Defender, Bill - just not in RTP mode as
long as this bug remains. So I'm not deserting the ship just yet!

 

[Bill Sanderson MVP]

Great--that's a very hopeful message for those seeing this issue. I've no
idea when new code might be released--but the fact that we are now seeing
update notices within Windows Defender for 1347 is a good sign.
--