I don't know if this is related, but it kinda leads to another post I was planning.
For a while now, most of the times I run sfc /scannow, it reports problems were found and repaired.
I have a cbs.log. Would it possibly help to post it?
There are two types of errors that SFC /ScanNow can report that it has found and corrected.
The first is a trivial 'ownership or permissions set twice' error. This appears to have no detrimental effect on the OS if left uncorrected, the ownership/permissions are set correctly both times. If you open the CBS.log in Notepad and search for "owned twice' you may find entries like these:
Code:
2020-12-06 17:54:11, Info CSI 000001dc Warning: Overlap: Directory \??\C:\Windows\SysWOW64\drivers\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-12-06 17:54:11, Info CSI 000001dd Warning: Overlap: Directory \??\C:\Windows\SysWOW64\wbem\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-12-06 17:54:11, Info CSI 000001de Warning: Overlap: Directory \??\C:\Windows\help\mui\0409\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.18362.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
The second type of error is a significant one which can disrupt the OS behaviour until repaired. It is where a file has been corrupted and has had to be replaced with a copy from the component store. There are many entries in CBS.log, it can be confusing to read it as only a few of them are from SFC. Option Five in this tutorial tells you how to extract just the SFC scan results from the CBS.log.
Run SFC Command in Windows 10
If the only errors SFC has corrected are the ownership/permission type then there is nothing to be worried about. If SFC is regularly finding corrupted files to repair that that is cause for concern.
Quote
