New
#1
Deciphering The CBS.log
I ran SFC a few hours ago, hoping to fix some network corruption. At the end, it said that it did find corruption (somewhere) that it couldn't fix, and referred to the cbs.log for details. That log is cumulative, so the only way to reference SFC results was by day and time, and even with that, the amount of lines involved is massive and cryptic.
Is there a way to see if it has dealt with specific files (network), without needing a computer for a brain?