How to fix SFC Scannow Corrupted files

Hello,

Being a novice with computers I thought to ask you all before I try something which may make things worse. I've neglected to tun SFC Scannow for a while and I've now fun it a few times as Administrator. I got the "Some corrupted files could not be fixed" result. The log file shows may were fixed except for eight files and those all appear to be Windows Update related. Just that part reads as follows:

"2019-11-16 15:46:27, Info CSI 0000548b [SR] Beginning Verify and Repair transaction
2019-11-16 15:46:27, Info CSI 0000548c [SR] Verify complete
2019-11-16 15:46:27, Info CSI 0000548d [SR] Repairing 1 components
2019-11-16 15:46:27, Info CSI 0000548e [SR] Beginning Verify and Repair transaction
2019-11-16 15:46:27, Info CSI 0000548f Hashes for file member [l:13]'SBCModel.json' do not match.
Expected: {l:32 ml:4096 b:50ae0541f62e1300f751b474c9eca1402b09805b0000b7076fa8b38ab3d03bb9}.
Actual: {l:32 b:3220dc53bb415e664555d61f902ac3ddcfbc447331ab78c1585746578a74a020}.
2019-11-16 15:46:27, Info CSI 00005490 [SR] Cannot repair member file [l:13]'SBCModel.json' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-11-16 15:46:27, Info CSI 00005491 Hashes for file member [l:12]'SBCModel.txt' do not match.
Expected: {l:32 ml:4096 b:49c81d806f195d3db749f0e491cf6a4f6e5bebde2febe95ea4da6f0f037ecc0c}.
Actual: {l:32 b:d0fafe94915001dee8768d6e618dd9a3d6c7a119dab6894b04fd5ca231e508dc}.
2019-11-16 15:46:27, Info CSI 00005492 [SR] Cannot repair member file [l:12]'SBCModel.txt' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-11-16 15:46:27, Info CSI 00005493@2019/11/16:20:46:27.848 Primitive installers committed for repair
2019-11-16 15:46:27, Info CSI 00005494 Hashes for file member [l:13]'SBCModel.json' do not match.
Expected: {l:32 ml:4096 b:50ae0541f62e1300f751b474c9eca1402b09805b0000b7076fa8b38ab3d03bb9}.
Actual: {l:32 b:3220dc53bb415e664555d61f902ac3ddcfbc447331ab78c1585746578a74a020}.
2019-11-16 15:46:27, Info CSI 00005495 [SR] Cannot repair member file [l:13]'SBCModel.json' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-11-16 15:46:27, Info CSI 00005496 [SR] This component was referenced by [l:143]'Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.17763.1.AE0CBA517C8F43D4129AAD2AABE60AF47DA6BB5C39DD2EB3FBB1243 DEAB2AC38'
2019-11-16 15:46:27, Info CSI 00005497 Hashes for file member [l:12]'SBCModel.txt' do not match.
Expected: {l:32 ml:4096 b:49c81d806f195d3db749f0e491cf6a4f6e5bebde2febe95ea4da6f0f037ecc0c}.
Actual: {l:32 b:d0fafe94915001dee8768d6e618dd9a3d6c7a119dab6894b04fd5ca231e508dc}.
2019-11-16 15:46:27, Info CSI 00005498 [SR] Cannot repair member file [l:12]'SBCModel.txt' of Microsoft-Windows-Update-UX-UserPredictionModel, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-11-16 15:46:27, Info CSI 00005499 [SR] This component was referenced by [l:143]'Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.17763.1.AE0CBA517C8F43D4129AAD2AABE60AF47DA6BB5C39DD2EB3FBB1243 DEAB2AC38'
2019-11-16 15:46:27, Info CSI 0000549a Hashes for file member [l:13]'SBCModel.json' do not match.
Expected: {l:32 ml:4096 b:50ae0541f62e1300f751b474c9eca1402b09805b0000b7076fa8b38ab3d03bb9}.
Actual: {l:32 b:3220dc53bb415e664555d61f902ac3ddcfbc447331ab78c1585746578a74a020}.
2019-11-16 15:46:27, Info CSI 0000549b Hashes for file member [l:13]'SBCModel.json' do not match.
Expected: {l:32 ml:4096 b:50ae0541f62e1300f751b474c9eca1402b09805b0000b7076fa8b38ab3d03bb9}.
Actual: {l:32 b:3220dc53bb415e664555d61f902ac3ddcfbc447331ab78c1585746578a74a020}.
2019-11-16 15:46:27, Info CSI 0000549c [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.json; source file in store is also corrupted
2019-11-16 15:46:27, Info CSI 0000549d Hashes for file member [l:12]'SBCModel.txt' do not match.
Expected: {l:32 ml:4096 b:49c81d806f195d3db749f0e491cf6a4f6e5bebde2febe95ea4da6f0f037ecc0c}.
Actual: {l:32 b:d0fafe94915001dee8768d6e618dd9a3d6c7a119dab6894b04fd5ca231e508dc}.
2019-11-16 15:46:27, Info CSI 0000549e Hashes for file member [l:12]'SBCModel.txt' do not match.
Expected: {l:32 ml:4096 b:49c81d806f195d3db749f0e491cf6a4f6e5bebde2febe95ea4da6f0f037ecc0c}.
Actual: {l:32 b:d0fafe94915001dee8768d6e618dd9a3d6c7a119dab6894b04fd5ca231e508dc}.
2019-11-16 15:46:27, Info CSI 0000549f [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Models\\SBCModel.txt; source file in store is also corrupted
2019-11-16 15:46:27, Info CSI 000054a0@2019/11/16:20:46:27.882 Primitive installers committed for repair
2019-11-16 15:46:27, Info CSI 000054a1 [SR] Repair complete"

If they are Windows Update related, is the fix to find and download the applicable Windows Update package and re-install that again? If so, where do I find it and if not, what's the fix?

Thank you.

Have executed following command:

Code:

Dism /Online /Cleanup-image  /Restorehealth

In case there are error messages running dism commands another troubleshooting step could be an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade

Thanks for the suggestions. I thinks it's fixed. However I don't completely understand what happened so here's what I did:
1- In CMD (Admin) I entered "Dism /Online /Cleanup-image /Restorehealth". The readout at the CMD window concluded with "The restore was completed successfully. The operation completed successfully" and the CBS log suggests
that that command initiated a tool which identifies the corrupted files then automatically downloads
and installs them. If this is the case, it's a dream come true. No more endless hours fixing Windows files???
Here's the CBS summary:

"2019-11-18 17:45:46, Info CBS Summary:
2019-11-18 17:45:46, Info CBS Operation: Detect and Repair
2019-11-18 17:45:46, Info CBS Operation result: 0x0
2019-11-18 17:45:46, Info CBS Last Successful Step: Entire operation completes.
2019-11-18 17:45:46, Info CBS Total Detected Corruption: 2
2019-11-18 17:45:46, Info CBS CBS Manifest Corruption: 0
2019-11-18 17:45:46, Info CBS CBS Metadata Corruption: 0
2019-11-18 17:45:46, Info CBS CSI Manifest Corruption: 0
2019-11-18 17:45:46, Info CBS CSI Metadata Corruption: 0
2019-11-18 17:45:46, Info CBS CSI Payload Corruption: 2
2019-11-18 17:45:46, Info CBS Total Repaired Corruption: 2
2019-11-18 17:45:46, Info CBS CBS Manifest Repaired: 0
2019-11-18 17:45:46, Info CBS CSI Manifest Repaired: 0
2019-11-18 17:45:46, Info CBS CSI Payload Repaired: 2
2019-11-18 17:45:46, Info CBS CSI Store Metadata refreshed: True
2019-11-18 17:45:46, Info CBS
2019-11-18 17:45:46, Info CBS Total Operation Time: 1427 seconds.
2019-11-18 17:45:46, Info CBS Ensure CBS corruption flag is clear
2019-11-18 17:45:46, Info CBS All WCP store corruptions were fixed
2019-11-18 17:45:46, Info CBS Ensure WCP corruption flag is clear
2019-11-18 17:45:46, Info CBS All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2019-11-18 17:45:46, Info CBS Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-11-18 17:45:47, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2019-11-18 17:45:47, Info CBS Count of times corruption detected: 1
2019-11-18 17:45:47, Info CBS Seconds between initial corruption detections: -1
2019-11-18 17:45:47, Info CBS Seconds between corruption and repair: 0
2019-11-18 17:45:47, Info CBS Reboot mark cleared
2019-11-18 17:45:47, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-11-18 17:45:47, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-11-18 17:45:47, Info CBS Exec: Processing complete, session(Corruption Repairing): 30776926_2550460251 [HRESULT = 0x00000000 - S_OK]
2019-11-18 17:45:47, Info CBS Session: 30776926_2550460251 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-11-18 17:46:23, Info CBS Session: 30776930_14051751 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2019-11-18 17:48:23, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2019-11-18 17:48:23, Info CBS TiWorker signaled for shutdown, going to exit."

2- To double check, I then ran SFC /VerifyOnly and the result was "Windows Resource Protection found integrity violations."

3- Oh no... So I thought maybe the clean files were downloaded ok but not installed and maybe SFC /Scannow will complete the repair, so I ran that and the result was "Windows Resource Protection found corrupted files and successfully repaired them." Sounded great but I thought a reboot and re-check should confirm.

4- I shut down, then restarted and ran SFC /VerifyOnly and the result was "... did not find any integrity violations."
I then created a System Restore point.

Does it seem fixed to you?

Success! It's great to have everything back as God intended. I'll be cloning my C: drive and performing a system backup too.

Great info. on your post - very helpful!

Thanks to all for your help.