R
robin
Just normal Restore Points daily- but no check points like I had with beta 2
robin
robin
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
Robin,
Did you ever figure out what specifically was triggering the Checkpoints in
your case? Most seemed to find a particular unknown (not yet classified)
driver or startup.
It would be interesting to note if that item itself has changed in the
descriptions found in Defender's Software Explorer.
Bitman
Did you ever figure out what specifically was triggering the Checkpoints in
your case? Most seemed to find a particular unknown (not yet classified)
driver or startup.
It would be interesting to note if that item itself has changed in the
descriptions found in Defender's Software Explorer.
Bitman
J
JS
My systems just the opposite, checkpoints for each day but no Restore
Points.
JS
Points.
JS
J
John Allen
Ditto
John
--
John
Just normal Restore Points daily- but no check points like I had with
beta 2 robin
--
R
Robin
the first thing that was triggering it was to have the two boxes checked for
if WD should notify you of new programs and already installed programs. I
only had already installed programs checked and had to take both checks off.
Now I only have checked "already installed programs" and so far no check
points. I still have the other one unchecked.
robin
if WD should notify you of new programs and already installed programs. I
only had already installed programs checked and had to take both checks off.
Now I only have checked "already installed programs" and so far no check
points. I still have the other one unchecked.
robin
G
Guest
No, these settings affected the creation of checkpoints for those who had
them, but had no real effect for those who didn't. A daily checkpoint
(roughly every 24 hours) is always created, but did have it's name modified
as a side effect, so this was really otherwise normal. Any checkpoints
created when software was installed would also have been normal, though
again, the names might not have properly reflected what created them, though
I'm not certain this was an issue for anyone.
The real issue was extra, often several checkpoints being created daily,
which almost everyone could relate to a specific action by Defender such as
detecion/removal of some spyware. The difference in cases such as Alan's
where that some 'not yet classified' piece of software, usually a driver, was
causing the triggring of a checkpoint for no apparent useful reason, except
that 'maybe' the unknown might be malware. This was generally easy to
determine by simply comparing the times of the checkpoints against Defender
detections listed in the Event Viewer.
I'm not certain that absolutely everyone with extra checkpoints was able to
make this coorelation, but everyone I'm aware of who tried seemed to be able
to. This is why I'm wondering if those with the original problem who
identified the original trigger are still having the problem. If not, it
would imply that either the items originally being detected are now
classified as allowed, removed from the PC, or the creation of these
particular 'not yet classified' checkpoints has been suppressed.
Only someone who had identified the original item creating the additional
checkpoints would be able to tell us, since the rest of us never had the
issue.
Bitman
them, but had no real effect for those who didn't. A daily checkpoint
(roughly every 24 hours) is always created, but did have it's name modified
as a side effect, so this was really otherwise normal. Any checkpoints
created when software was installed would also have been normal, though
again, the names might not have properly reflected what created them, though
I'm not certain this was an issue for anyone.
The real issue was extra, often several checkpoints being created daily,
which almost everyone could relate to a specific action by Defender such as
detecion/removal of some spyware. The difference in cases such as Alan's
where that some 'not yet classified' piece of software, usually a driver, was
causing the triggring of a checkpoint for no apparent useful reason, except
that 'maybe' the unknown might be malware. This was generally easy to
determine by simply comparing the times of the checkpoints against Defender
detections listed in the Event Viewer.
I'm not certain that absolutely everyone with extra checkpoints was able to
make this coorelation, but everyone I'm aware of who tried seemed to be able
to. This is why I'm wondering if those with the original problem who
identified the original trigger are still having the problem. If not, it
would imply that either the items originally being detected are now
classified as allowed, removed from the PC, or the creation of these
particular 'not yet classified' checkpoints has been suppressed.
Only someone who had identified the original item creating the additional
checkpoints would be able to tell us, since the rest of us never had the
issue.
Bitman
R
robinb
once i had unchecked it- the chk points stopped on beta2
when i had it checked i had 3 or 4 chk points a day
robin
when i had it checked i had 3 or 4 chk points a day
robin