Windows Defender System Checkpoints

[Stuart]

Thanks to JBob and David Lipman for giving me the password to this group. I
will not abuse the trust.

About a month ago I did a major clean of my registry and I have the Defender
Beta. What I am concerned about is the three to six checkpoints per day
Defender is creating and whether the checkpoints are in a push-down-stack
that might cause me to loose the critical manually set checkpoint after my
registry clean a month ago. Do I need to uninstall Defender?
Stuart//

 

[Stuart]

Thanks to JBob and David Lipman for giving me the password to this group.
I will not abuse the trust.

About a month ago I did a major clean of my registry and I have the
Defender Beta. What I am concerned about is the three to six checkpoints
per day Defender is creating and whether the checkpoints are in a
push-down-stack that might cause me to loose the critical manually set
checkpoint after my registry clean a month ago. Do I need to uninstall
Defender?
Stuart//

Sorry for the slip I meant before the registry clean.

 

[Bill Sanderson MVP]

This is a public group--the password details are posted publicly, and HTML
access is available to anyone with access to the web.
Please spread the word!
(But, thanks, JBob, and David H.Lipman!)

It is possible to eliminate these checkpoints, I believe, based on a post
from Steve Dodson, of Microsoft. I don't see them on systems I've worked
with, but here's the method:
------------------------------------
Steve Dodson has posted a registry edit to change this behavior, which isn't
seen on all machines--let me find it:
----------
In the registry editor,

Create a "REG_DWORD" Key named "DisableRestorePoint" and set it to TRUE
under the following location in the registry.

HKLM/Software/Microsoft/Windows Defender/Scan/
--------------------------------------
This needs a little interpretation:

1) find the location named above.
2) Highlight the Scan object, and right click it, choose permissions, and
give your user FULL.
3) create a value as instructed above, and set it to "1."
4) reverse your action in 2)--uncheck Full for your user.

 

[Guest]

Hi Bill:

Could you provide the detail instructions on how to:

"In the registry editor,

Create a "REG_DWORD" Key named "DisableRestorePoint" and set it to TRUE
under the following location in the registry.

HKLM/Software/Microsoft/Windows Defender/Scan/

I am not exactly sure as to what steps need to be taken to accomplish the
above.
If you could provide them I sure would appreciate it.

Thanks

 

[Guest]

If I have correctly understood from Bill the correct sequence it is this:

1) In the registry editor, find the following location.
HKLM/Software/Microsoft/Windows Defender/Scan

2) Highlight the "Scan" object, and right click it, choose permissions, and
give your user FULL.

3) Under "Scan" key, create a "REG_DWORD" value named "DisableRestorePoint",
and set it to "1".

4) Reverse your action in 2) - uncheck FULL for your user.

However I believe that for these operations it is better not to be beginners
with the Windows Registry.
Also I have a " Windows Defender Checkpoint" to every start of Windows, but
a problem doesn't seem me, rather...

 

[Tom Emmelot]

Hi Bill,

works 100%, no restore points anymore!

Regards >*< TOM >*<

Bill Sanderson MVP schreef:

 

[Bill Sanderson MVP]

That's good. Unfortunately, I'm not sure this process can be simplified to
a one-button solution, because of the needed permissions changes. Maybe it
can be done with a script--I don't think a .reg file will do it.

--

Hi Bill,

works 100%, no restore points anymore!

Regards >*< TOM >*<

Bill Sanderson MVP schreef:

 

[Tom Emmelot]

Hi Bill,

i think that for real cleaning and mistakes that a popup must come that
ask you to make a restore point at that moment with a explanation that
it is possible that after cleaning the computer maybe wont start!

Regards >*< TOM >*<

Bill Sanderson MVP schreef:

 

[Bunge]

In

This is a public group--the password details are posted publicly, and
HTML access is available to anyone with access to the web.
Please spread the word!
(But, thanks, JBob, and David H.Lipman!)

It is possible to eliminate these checkpoints, I believe, based on a
post from Steve Dodson, of Microsoft. I don't see them on systems
I've worked with, but here's the method:
------------------------------------
Steve Dodson has posted a registry edit to change this behavior,
which isn't seen on all machines--let me find it:
----------
In the registry editor,

Create a "REG_DWORD" Key named "DisableRestorePoint" and set it to
TRUE under the following location in the registry.

HKLM/Software/Microsoft/Windows Defender/Scan/
--------------------------------------
This needs a little interpretation:

1) find the location named above.
2) Highlight the Scan object, and right click it, choose permissions,
and give your user FULL.
3) create a value as instructed above, and set it to "1."
4) reverse your action in 2)--uncheck Full for your user.

(Snipped a bit)

Can can confirm it works Bill, plain and simple, no more Restore Points in
Restore.

Cheers.

Best.

 

[Guest]

Thanks, your instructions worked great.

If I have correctly understood from Bill the correct sequence it is this:

1) In the registry editor, find the following location.
HKLM/Software/Microsoft/Windows Defender/Scan

2) Highlight the "Scan" object, and right click it, choose permissions, and
give your user FULL.

3) Under "Scan" key, create a "REG_DWORD" value named "DisableRestorePoint",
and set it to "1".

4) Reverse your action in 2) - uncheck FULL for your user.

However I believe that for these operations it is better not to be beginners
with the Windows Registry.
Also I have a " Windows Defender Checkpoint" to every start of Windows, but
a problem doesn't seem me, rather...

 

[Bill Sanderson MVP]

Thanks, everyone. I don't know why some systems are seeing this issue and
others not--maybe I haven't looked closely enough at the systems I work
with--I've definitely checked the SR area on my home machine, but very few
office workstations.

--