Windows 10: Need help reading CBS log after running sfc /scannow

Hello, I recently encountered a blue screen error, so I opened command prompt and ran "sfc /scannow."When it completed, I got the 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. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.I went into the CBS log file and did a ctrl + f for "cannot repair," but I'm not extremely technically savvy so I have no idea what to do with the i

:)

 

ran a SFC Scan and it suggested I run the CBS process

As mentioned, I had some odd behavior and ran SFC /Scannow. It said I had corrupted files it could not fix and suggested I run a CBS process. A log file was produced but I don't know what I'm reading. Can someone help?

Should I post the log here? I have no idea if it contains personal info... and it's pretty large (78KB)

Suggestions?

 

The SFC scannow misisng windir\Logs\CBS\.log

I ran a sfc scannow command prompt to fix my windows 10 and computer files. It could not fix some corrupted files. It did give this - windir\logs\cbs\cbs.log but none of that is on my computer. I've searched an there is nothing on the c drive.

Is there something I can do to find these and fix the issues, please help?

 

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?