Windows 10: Error from Windows 10 after doing SFC /scannow

Discus and support Error from Windows 10 after doing SFC /scannow in Windows 10 Installation and Upgrade to solve the problem; Hi all, I am trying to update this laptop running windows 10 but it keeps being stopped. So I did an sfc scan and found that were some corrupt files... Discussion in 'Windows 10 Installation and Upgrade' started by JamesL5, Aug 28, 2019.

  1. JamesL5 Win User

    Error from Windows 10 after doing SFC /scannow


    Hi all,


    I am trying to update this laptop running windows 10 but it keeps being stopped. So I did an sfc scan and found that were some corrupt files it couldn't fix.




    Here is a copy of the log


    Any help in finding a solution would be great.



    2019-08-29 12:56:38, Info CSI 00005d8c [SR] Beginning Verify and Repair transaction

    2019-08-29 12:56:38, Info CSI 00005d8d Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.

    Expected: {l:32 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.

    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.

    2019-08-29 12:56:38, Info CSI 00005d8e [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d8f Hashes for file member [l:13]'Defender.psd1' do not match.

    Expected: {l:32 b:7e31d923de2553b5328f1f8e221efd83836dab0a8deeac39c997827242cd39c2}.

    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.

    2019-08-29 12:56:38, Info CSI 00005d90 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d91 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

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

    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.

    2019-08-29 12:56:38, Info CSI 00005d92 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d93 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

    Expected: {l:32 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.

    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.

    2019-08-29 12:56:38, Info CSI 00005d94 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d95 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.

    Expected: {l:32 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.

    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.

    2019-08-29 12:56:38, Info CSI 00005d96 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d97 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.

    Expected: {l:32 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.

    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.

    2019-08-29 12:56:38, Info CSI 00005d98 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d99 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

    Expected: {l:32 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.

    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.

    2019-08-29 12:56:38, Info CSI 00005d9a [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d9b Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.

    Expected: {l:32 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.

    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.

    2019-08-29 12:56:38, Info CSI 00005d9c [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d9d Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.

    Expected: {l:32 b:d4514f62d0aa3e2cbb99e2f5993496ab095d897449360f57d5880bbe9e5cdbde}.

    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.

    2019-08-29 12:56:38, Info CSI 00005d9e [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005d9f@2019/8/29:02:56:38.956 Primitive installers committed for repair

    2019-08-29 12:56:38, Info CSI 00005da0 Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.

    Expected: {l:32 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.

    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.

    2019-08-29 12:56:38, Info CSI 00005da1 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005da2 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005da3 Hashes for file member [l:13]'Defender.psd1' do not match.

    Expected: {l:32 b:7e31d923de2553b5328f1f8e221efd83836dab0a8deeac39c997827242cd39c2}.

    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.

    2019-08-29 12:56:38, Info CSI 00005da4 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005da5 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005da6 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

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

    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.

    2019-08-29 12:56:38, Info CSI 00005da7 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005da8 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005da9 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

    Expected: {l:32 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.

    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.

    2019-08-29 12:56:38, Info CSI 00005daa [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005dab [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005dac Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.

    Expected: {l:32 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.

    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.

    2019-08-29 12:56:38, Info CSI 00005dad [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005dae [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005daf Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.

    Expected: {l:32 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.

    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.

    2019-08-29 12:56:38, Info CSI 00005db0 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005db1 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005db2 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

    Expected: {l:32 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.

    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.

    2019-08-29 12:56:38, Info CSI 00005db3 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005db4 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005db5 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.

    Expected: {l:32 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.

    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.

    2019-08-29 12:56:38, Info CSI 00005db6 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005db7 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005db8 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.

    Expected: {l:32 b:d4514f62d0aa3e2cbb99e2f5993496ab095d897449360f57d5880bbe9e5cdbde}.

    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.

    2019-08-29 12:56:38, Info CSI 00005db9 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2019-08-29 12:56:38, Info CSI 00005dba [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2019-08-29 12:56:38, Info CSI 00005dbb Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.

    Expected: {l:32 ml:4096 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.

    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.

    2019-08-29 12:56:38, Info CSI 00005dbc Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.

    Expected: {l:32 ml:4096 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.

    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.

    2019-08-29 12:56:38, Info CSI 00005dbd [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted

    2019-08-29 12:56:38, Info CSI 00005dbe Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.

    Expected: {l:32 ml:4096 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.

    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.

    2019-08-29 12:56:38, Info CSI 00005dbf Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.

    Expected: {l:32 ml:4096 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.

    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.

    2019-08-29 12:56:38, Info CSI 00005dc0 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted

    2019-08-29 12:56:38, Info CSI 00005dc1 Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.

    Expected: {l:32 ml:4096 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.

    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.

    2019-08-29 12:56:38, Info CSI 00005dc2 Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.

    Expected: {l:32 ml:4096 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.

    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.

    2019-08-29 12:56:38, Info CSI 00005dc3 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted

    2019-08-29 12:56:38, Info CSI 00005dc4 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.

    Expected: {l:32 ml:4096 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.

    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.

    2019-08-29 12:56:38, Info CSI 00005dc5 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.

    Expected: {l:32 ml:4096 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.

    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.

    2019-08-29 12:56:38, Info CSI 00005dc6 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted

    2019-08-29 12:56:38, Info CSI 00005dc7 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.

    Expected: {l:32 ml:4096 b:d4514f62d0aa3e2cbb99e2f5993496ab095d897449360f57d5880bbe9e5cdbde}.

    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.

    2019-08-29 12:56:38, Info CSI 00005dc8 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.

    Expected: {l:32 ml:4096 b:d4514f62d0aa3e2cbb99e2f5993496ab095d897449360f57d5880bbe9e5cdbde}.

    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.

    2019-08-29 12:56:38, Info CSI 00005dc9 [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-08-29 12:56:38, Info CSI 00005dca Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

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

    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.

    2019-08-29 12:56:38, Info CSI 00005dcb Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.

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

    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.

    2019-08-29 12:56:38, Info CSI 00005dcc [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-08-29 12:56:38, Info CSI 00005dcd Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

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

    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.

    2019-08-29 12:56:38, Info CSI 00005dce Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.

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

    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.

    2019-08-29 12:56:38, Info CSI 00005dcf [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-08-29 12:56:38, Info CSI 00005dd0 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

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

    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.

    2019-08-29 12:56:38, Info CSI 00005dd1 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.

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

    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.

    2019-08-29 12:56:38, Info CSI 00005dd2 [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-08-29 12:56:38, Info CSI 00005dd3 Hashes for file member [l:13]'Defender.psd1' do not match.

    Expected: {l:32 ml:4096 b:7e31d923de2553b5328f1f8e221efd83836dab0a8deeac39c997827242cd39c2}.

    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.

    2019-08-29 12:56:38, Info CSI 00005dd4 Hashes for file member [l:13]'Defender.psd1' do not match.

    Expected: {l:32 ml:4096 b:7e31d923de2553b5328f1f8e221efd83836dab0a8deeac39c997827242cd39c2}.

    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.

    2019-08-29 12:56:38, Info CSI 00005dd5 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted

    2019-08-29 12:56:39, Info CSI 00005dd6@2019/8/29:02:56:39.050 Primitive installers committed for repair

    2019-08-29 12:56:39, Info CSI 00005dd7 [SR] Repair complete

    2019-08-29 12:56:39, Info CSI 00005dd8 [SR] Committing transaction

    2019-08-29 12:56:39, Info CSI 00005dd9 Creating NT transaction (seq 1)

    2019-08-29 12:56:39, Info CSI 00005dda Created NT transaction (seq 1) result 0x00000000, handle @0x89c

    2019-08-29 12:56:39, Info CSI 00005ddb@2019/8/29:02:56:39.175 Beginning NT transaction commit...

    2019-08-29 12:56:39, Info CSI 00005ddc@2019/8/29:02:56:39.222 CSI perf trace:

    CSIPERF:TXCOMMIT;72905

    2019-08-29 12:56:39, Info CSI 00005ddd [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

    2019-08-29 12:59:04, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

    2019-08-29 12:59:04, Info CBS TiWorker signaled for shutdown, going to exit.

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

    2019-08-29 12:59:04, Info CBS Execution Engine Finalize

    2019-08-29 12:59:04, Info CBS Execution Engine Finalize

    2019-08-29 12:59:04, Info CBS Ending the TiWorker main loop.

    2019-08-29 12:59:04, Info CBS Starting TiWorker finalization.

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: ManifestCacheFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: ExecutionEngineFinalize

    2019-08-29 12:59:04, Info CBS CBS Engine already deativated

    2019-08-29 12:59:04, Info CBS CBS Engine already deativated

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: PackageTrackerFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CoreResourcesUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: SessionManagerFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CapabilityManagerFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: WcpUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: DrupUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CfgMgr32Unload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: DpxUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: SrUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CbsEsdUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: CbsEventUnregister

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: AppContainerUnload

    2019-08-29 12:59:04, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.

    2019-08-29 12:59:04, Info CBS Ending TiWorker finalization.

    2019-08-29 12:59:04, Info CBS Ending the TrustedInstaller main loop.

    2019-08-29 12:59:04, Info CBS Starting TrustedInstaller finalization.

    2019-08-29 12:59:04, Info CBS Ending TrustedInstaller finalization.

    :)
     
    JamesL5, Aug 28, 2019
    #1
  2. Kari Win User

    sfc /scannow errors


    Important thing to remember is that the SFC / SCANNOW cannot always fix all errors at once. It is quite often required to run SFC /SCANNOW several times.

    I have often had a situation that only a third, fourth or fifth run has finally reported "No more errors".

    This is how it should be done:

    • SFC / SCANNOW
    • If SFC reports not all errors were fixed, reboot and run it again
    • SFC / SCANNOW
    • If SFC again reports not all errors were fixed, reboot and run it again
    • And so on
    Screenshot from the TenForums SFC tutorial:


    Error from Windows 10 after doing SFC /scannow [​IMG]
     
  3. Steve C Win User
    SFC /SCANNOW Errors After Update


    I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

    1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
    2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
    3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with Error: 0x800f081f "The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature."
    4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
    5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."

    Please advise:
    1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
    2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
    3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?
     
    Steve C, Aug 28, 2019
    #3
  4. lvgandhi Win User

    Error from Windows 10 after doing SFC /scannow

    sfc /scannow error


    Problem is not with windows update. It is with defender malware update.
    Please do
    DISM /Online /Cleanup-Image /AnalyzeComponentStore
    DISM /Online /Cleanup-Image /StartComponentCleanup
    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth

    After above steps, reboot laptop and do sfc /scannow.
     
    lvgandhi, Aug 28, 2019
    #4
Thema:

Error from Windows 10 after doing SFC /scannow

Loading...
  1. Error from Windows 10 after doing SFC /scannow - Similar Threads - Error doing SFC

  2. Error in sfc scannow

    in Windows 10 Installation and Upgrade
    Error in sfc scannow: Windows 10 sfc scannow could not perform the requested system https://answers.microsoft.com/en-us/windows/forum/all/error-in-sfc-scannow/c215c9d3-ab1e-4df8-9e2f-b2b7b990143b
  3. sfc/scannow error

    in Windows 10 Software and Apps
    sfc/scannow error: 00000253 Hashes for file member [l:14]'System.Web.dll' do not match. Expected: {l:20 b:47cb9b0ad80a6962723f7b601b7941971a388b19}. Actual: {l:20 b:f7d269889aa64c84ebb3f0c69c3705b046b7d751}.2023-07-01 07:32:49, Info CSI 00000254 [SR] Cannot repair member file...
  4. sfc /scannow error

    in Windows 10 Gaming
    sfc /scannow error: I'm running sfc /scannow regularly, and i am getting back wierd results. It seems I have problem with one file, sfc /scannow either finds it corrupt, and repairs it, or does not find any problem at all. 2023-03-18 08:24:08, Info CSI 000001ff [SR] Repairing 1 components...
  5. sfc /scannow error

    in Windows 10 BSOD Crashes and Debugging
    sfc /scannow error: I'm running sfc /scannow regularly, and i am getting back wierd results. It seems I have problem with one file, sfc /scannow either finds it corrupt, and repairs it, or does not find any problem at all. 2023-03-18 08:24:08, Info CSI 000001ff [SR] Repairing 1 components...
  6. sfc /scannow errors

    in Windows 10 Support
    sfc /scannow errors: Hi all, I will appreciate it if you can help me fix my system errors. I am attaching CBS, FRST, Addition text files. Thank you in advance. Regards. 166129
  7. Error in log after sfc /scannow

    in Windows 10 Performance & Maintenance
    Error in log after sfc /scannow: Maybe this is the cause of my dde server errors. I don't know how to try and fix. CSI 0000065c Error - Overlap: Duplicate ownership for directory \?? I have a few for different folders. Can some one point me in the correct direction ? 62743
  8. SFC /scannow - errors

    in Windows 10 Performance & Maintenance
    SFC /scannow - errors: Hey all! I recently upgrade to Windows 10 2 weeks ago and for kicks I decided to run an SFC /scannow .. and It found a whole slew of errors! It's weird because I don't see anything wrong with the OS but I know there are according to the scanner. I ran it a few times,...
  9. SFC /SCANNOW Errors After Update

    in Windows 10 Performance & Maintenance
    SFC /SCANNOW Errors After Update: I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:...
  10. SFC /SCANNOW Error

    in Windows 10 Performance & Maintenance
    SFC /SCANNOW Error: When trying to run SFC /SCANNOW the following error is generated: C:\Windows\system32>sfc /scannow Windows Resource Protection could not start the repair service. Is this a knpown problem with solution? 20898

Users found this page by searching for:

  1. CbsCoreFinalize: DrupUnload 2019-10-29 11:05:59 Info CBS CbsCoreFinalize: CfgMgr32Unload 2019-10-29 11:05:59 Info CBS CbsCoreFinalize: DpxUnload 2019-10-29 11:05:59 Info CBS CbsCoreFinal