Windows 10: my SFC /Scannow cannot fix the error so it exports CBS.log, Please check

my SFC /Scannow cannot fix the error so it exports CBS.log, Please check

http://s000.tinyupload.com/index.php?file_id=22595963675053319236

:)

 

sfc /scannow error

That's why Im asking the question. Am I correct in thinking that its perfectly normal that after the second running of sfc /scannow in your list you would get :-

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Then after that..its the third sfc /scannow that you list that comes up clean .
Ivghandi was saying that he presumed that the second sfc /scannow you list showing "Windows Resource Protection found corrupt files and successfully repaired them" meant that he still had a problem.

The way I understand that DISM works is that it repairs the Component Store. Then when you run SFC /scannow again it can then repair the file corruptions it detected originally. Have I got that correct?

 

CBS log: How to fix findstr in Windows 10 for sfc /scannow 'SR' filter

Hi everyone and Kyhi!

I am new to the forum and my Win 10 is experiencing some sfc /scannow errors.
Tested in Powershell and also cmd with the same error.
After reading the posts #61 and #62 at Sevenforum thread 'Windows 7: How do you fix corrupted files found by SFC /SCANNOW?', also I tried to use the following comand (after sfc /scannow in elevated cmd) to extract only the SR rows from the CBS.log:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"
But while it actually works in Windows 7 , under Windows 10 simply continues to blink and the sfcdetails.txt is empty.

How to fix that findstr command, please? *Confused
P.S. Screnshot shows the txt file out of the desktop because I tried to generate it also in C:\ but without results.

Thank you,

 

SFC errors - how to identify/fix?


As one (not particularly hopeful) step in trouble-shooting a problem (Cortana not opening reliably) I used sfc /scannow from an elevated command. At its conclusion I got this message:

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."

I opened that log file - but it's 52,000 lines long! How could a user be expected to isolate it from that? More important, what are suggested ways for me to proceed please? Apart from ignoring the unidentified problem(s).

--
Terry, East Grinstead, UK