How to analyse the CBS.log

Sorry how do I enter elevated cmd while the system crashed

I suppose I was in elevated cmd as RE shows : administrator:x:\windows\system32\cmd.exe. But still said findstr not recognised.

I cannot tell one how to analyze the CBS.log file. What I did to cut down on the volume of data is to open the log file in MS Word (2007), goto Page Layout, set the size of the document to 11x22. Then, select all text, goto Insert->Table, Convert text to table, separate fields by commas and click OK. After deleting all the info lines and extraneous columns, what is left is a manageable amount of data that is easier to go through. I noticed in my cursory look, many of the files were corrupt and were also corrupt in the Windows file storage area as well. These files could not be "replaced". Many files also reported a "hash mismatch". It seems a re-install of Windows would be needed to repair these files.

I have the same problem. Once you found the problem files how did you fix them?
Did you install an app in order to fix? I include the file that was generates just the way you detail explanation

How did you fix these files?

I have the same problem. Once you found the problem files how did you fix them?
Did you install an app in order to fix? I include the file that was generates just the way you detail explanation