Charley,
Here is a more Step by Step version of the fix by Bill Sanderson:
=====Bill Sanderson Said=====
I know of no change to this issue. However, we do have a set of registry
editing instructions to create a new key which will modify this behavior--so
if doing that is acceptable to you I'll post that ...
------------------------------------------------------------------------------
Steve Dodson has posted a workaround to eliminate the behavior, and I
have taken the liberty of expanding on his somewhat terse treatment:
-------------------------------------------------------------------------
It is possible to stop this activity, but it takes some care and registry
editing.
Important: This message contains information about how to modify the
registry. Make sure to back up the registry before you modify it. Make
sure that you know how to restore the registry if a problem occurs. For
more
information about how to back up, restore, and modify the registry, click
the following article number to view the article in the Microsoft
Knowledge Base:
256986 (
http://support.microsoft.com/kb/256986/) Description of the
Microsoft Windows registry .
Start, run, Regedit <enter>
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Scan
Right click that folder in the left tree view, and choose "Permissions"
With your username highlighted, click Full Control in the Allow column,
and "Apply"
With the Scan folder highlighted choose:
Edit, New, DWORD value, and type in "DisableRestorePoint"
and hit enter.
Double-click DisableRestorePoint in the right column, and set the Value
to 1, hexadecimal.
Right-click Scan in the left tree view, and choose "Permissions"
With your username highlighted, Uncheck "Full Control" in the Allow
column, and "Apply"
Close the registry editor by hitting the X in the upper right corner, or
File, Exit.
=====End of Bill Sanderson's Message=====