Nice article! How deeply does explicit SFC check (content corruption
via MD5 or just correct size, version tab etc.?)
Does it compare against the cache copy?
Does it have an awareness of ChkDsk / AutoChk, i.e. that if one of
these "fixes" a protected file, the damaged file should be replaced?
Does it have an awareness of av software, so that if av "cleans" a
protected file, the damaged file should be replaced?
Outside of these, content checking's required, in cases where RAM
errors bonk the file when moving it during defrag, or when a deranged
write splats stuff over the file, even though the file was never
"opened for writes" or "opened for read/writes" (i.e. hooking into
these known file-changers isn't enough).