"Terry Pinnell" wrote in message
...
"SC Tom" wrote:



"Terry Pinnell" wrote in message
. ..
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix
some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this
command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in
at
the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?

skip?

Terry, East Grinstead, UK


Sorry, I can't help with the errors, but I changed

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"
to
findstr /c:"[SR] Cannot" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

I made a batch file of it just to trim the output to the items that can't
be
repaired. Made it a lot easier to Google for a fix (if there was one).

Thanks, neat. (I edited the original fairly quickly in my text editor.)

Re 'a fix', see my earlier reply.

Saw that this morning :-) Good deal!

Did SFC actually fix the errors, or just tell you it was going to? Sometimes
it lies :-(
--

SC Tom