access:WindowsAlthough the resource protection mechanism found corrupted files, it could not fix some of them, and suggested that users check the CBS log files for additional details.
The CBS.log file indicates that the problem mainly stems from the hash mismatch causing the process to fail. This may happen when the hash value of the file does not match the file in the WinSxS folder.
“Interesting, I have the exact same corrupted file issue in the sfc operation on all four Windows 10 laptops today. “One user noticed in the forum post.
This issue seems to be related to the latest definition update for Windows Defender. Some users have also reported that this bug is also affecting the latest version on Windows 10 version 1809 (updated October 2019).
Microsoft has not confirmed the problem of SFC / scannow, but this problem is very troublesome for users, it is expected to solve the problem in a short time.