How to repair corrupt files identified by sfc /scannnow

[Guest Bertram12]

My wife's Windows 10 computer failed a couple of days ago. Wouldn't boot, just went into the dreaded "Preparing Automatic Repair / Diagnosing your PC" loop. But never actually repaired anything. After booting and rebooting for a few hours, in despair, I had no choice but to reinstall Windows 10, using a repair CD which I'd created when we first set up the PC.

 

Windows 10 is now working again, but sfc /scannow is reporting as follows:

 

"Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag."

 

Looking at the above CBS.log file, there are numerous lines of gobbledygook such as:

 

"2019-07-24 14:56:51, Info CSI 0000033c Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.

Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.

Actual: {l:32 b:22454077de87f1cb3bff79e0acf51befbf929c31231f8c780fb9f254825f97ad}.

2019-07-24 14:56:51, Info CSI 0000033d [sR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted

2019-07-24 14:56:51, Info CSI 0000033e Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.

Actual: {l:32 b:905248df4310b3bfe79b60dfe69b82517b81c16864e2e12677c50f6a66ca0459}.

2019-07-24 14:56:51, Info CSI 0000033f Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.

Actual: {l:32 b:905248df4310b3bfe79b60dfe69b82517b81c16864e2e12677c50f6a66ca0459}.

2019-07-24 14:56:51, Info CSI 00000340 [sR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted

2019-07-24 14:56:51, Info CSI 00000341 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.

Actual: {l:32 b:12f7403a57636e10490a52a2caf3010c56e0a86da83fda2c055e9534293039fb}.

2019-07-24 14:56:51, Info CSI 00000342 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.

Actual: {l:32 b:12f7403a57636e10490a52a2caf3010c56e0a86da83fda2c055e9534293039fb}.

2019-07-24 14:56:51, Info CSI 00000343 [sR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted

2019-07-24 14:56:51, Info CSI 00000344 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.

Actual: {l:32 b:b4035789fec4e2e1ee3dd5e97a50a0cf5837308773d9ac1af3550f2ea04e9385}.

2019-07-24 14:56:51, Info CSI 00000345 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.

Actual: {l:32 b:b4035789fec4e2e1ee3dd5e97a50a0cf5837308773d9ac1af3550f2ea04e9385}.

2019-07-24 14:56:51, Info CSI 00000346 [sR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted

2019-07-24 14:56:51, Info CSI 00000347 Hashes for file member [l:13]'Defender.psd1' do not match."

 

I suppose I should be flattered that Microsoft thinks an end-user would understand this guff, but this particular end-user does not.

 

Could someone explain why, having just reinstalled Windows 10, some of its files are corrupt? It has taken two days to reinstall Windows 10, my wife's apps and all of her settings. If sfc /scannow knows which files are corrupt, why cannot it simply replace them?

 

So frustrating - and an utter time-waster. Does anyone have any idea how I can repair or replace the (apparently numerous) corrupted files?

 

BTW, Windows 10 is hopefully up to date - the most recently installed update is "Feature update to Windows 10, version 1903".

 

More...