This is what has been posted in the Windows Defender forums.
The file that is displayed in the user interface as being scanned at the
time you get the error actually turns out to be unrelated to the problem.
The scan will typically always show the same file because the series of
actions taken during the scan is deterministic, and when the error happens
(while trying to load one of the registry hives from disk) the scan will
normally be in the same spot every time. But, rest assured that the file
is
not relevant.
Yes, the next engine build should fix this issue.
As to whether you are protected, the answer is yes and no. In general the
realtime protection facility should continue to work, which does offer
some
protection, but you will not be able to successfully perform either a
quick
scan or full scan of your computer until the next engine release. This
means
that it is possible that some spyware will not be detected during the
intervening period.
Thanks
-Mike
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting
http://www.winhelponline.com
No clues right now, spinlock. Have an eye on the Windows Defender forums.
I'll also post the solution if find any.
--
Regards,
Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting
http://www.winhelponline.com
Thanks for the feedback, I have autoupdate selected, so I assume they are
the latest.
Check with a manual update to confirm.
Current versions:
1.1.1051.0, 1.1.1186.0, and 1.13.1282.6
Still getting same error.
"