i use a batch file i named startsfc.cmd that contains the following (based on the tutorial referenced above)
@echo off
cd\
del /q %windir%\logs\cbs\cbs.log
del /q c:\sfcdetails.txt
sfc /scannow
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >c:\sfcdetails.txt
notepad c:\sfcdetails.txt
exit
it runs the command, filters out the junk in the cbs.log file and opens it in notepad, most of the informative stuff is near the bottom. when you close notepad, it closes the command window. the sfcdetails.txt file stays in your root for reference, until you run the next time.
the end of my just run command:
2013-08-19 07:53:30, Info CSI 000002ee [SR] Verifying 100 (0x0000000000000064) components
2013-08-19 07:53:30, Info CSI 000002ef [SR] Beginning Verify and Repair transaction
2013-08-19 07:53:31, Info CSI 000002f1 [SR] Verify complete
2013-08-19 07:53:31, Info CSI 000002f2 [SR] Verifying 1 components
2013-08-19 07:53:31, Info CSI 000002f3 [SR] Beginning Verify and Repair transaction
2013-08-19 07:53:31, Info CSI 000002f5 [SR] Verify complete
2013-08-19 07:53:31, Info CSI 000002f6 [SR] Repairing 0 components
2013-08-19 07:53:31, Info CSI 000002f7 [SR] Beginning Verify and Repair transaction
2013-08-19 07:53:31, Info CSI 000002f9 [SR] Repair complete
most of the preceding was the same as line 1, checking and logging in groups of 100, if it replaces something or cannot for some reason, it stands out as you scroll down, and is noted in the last four lines.