System File Checker errors reported...

Hello Peter,

When SFC cannot fix a system file, you can try running the DISM command show under step 4 option 3 below to repair the component store, and then try the SFC command again afterwards.

Run SFC Command in Windows 10

Peter,

The problem is caused by a platform update to Windows defender and others are suffering the same problem. You can ignore it and let MS get around to fixing it sometime or you can use some of the guidance in these TenForums threads in an attempt to fix the problem yourself -

sfc -scannow failing after this latest Defender Platfom update - TenForums
SFC and DISM error when trying to fix corrupt windows files - TenForums
[this thread - System File Checker errors reported - TenForums]
and others with some info about this problem
Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9 Windows Update - TenForums
sfc -scannow found corrupted file that could not be corrected - TenForums

My attempts to fix the problem failed so I am just living with the problem.

By the way, if you ever need to post about an SFC problem again in the future, use the guidance in the tutorial Brink linked you to so that you do not post the entire cbs.log.
- I found what I needed in your cbs.log only because I guessed [correctly] what the problem was.
- In normal circumstances, I would not have been able to guess and would just have given up when I saw you'd posted the whole thing.
- You can even go further than Brink suggests and extract only the lines listing irreparable items using this command

Code:

findstr.exe /c:"[SR] Cannot repair member file" %windir%\Logs\CBS\CBS.log >{{A path of your own choosing to wherever you want the results to be saved}}\SFCResults-Unrepairables.Log"

such as, using an example path D:\Desktop for simplicity,

Code:

findstr.exe /c:"[SR] Cannot repair member file" %windir%\Logs\CBS\CBS.log >D:\Desktop\SFCResults-Unrepairables.Log"

Denis

Great news.