Windows 10: Hash mismatch in Defender after update How to remove and reinstall

windows 10 build 18363.329 I ran a SFC scan and found Hash mismatch for windows defender. How would I go about removal and reinstall. I guess I could roll back the latest update but not sure that this problem predates that.


2019-09-09 15:33:34, Info CSI 000002ab Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
2019-09-09 15:33:34, Info CSI 000002ac [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:34, Info CSI 000002ad Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2019-09-09 15:33:34, Info CSI 000002ae [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:34, Info CSI 000002af Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
2019-09-09 15:33:34, Info CSI 000002b0 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:34, Info CSI 000002b1 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
2019-09-09 15:33:34, Info CSI 000002b2 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:35, Info CSI 000002b3 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
2019-09-09 15:33:35, Info CSI 000002b4 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:35, Info CSI 000002b5 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
2019-09-09 15:33:35, Info CSI 000002b6 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:35, Info CSI 000002b7 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
2019-09-09 15:33:35, Info CSI 000002b8 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:35, Info CSI 000002b9 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
2019-09-09 15:33:35, Info CSI 000002ba [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2019-09-09 15:33:35, Info CSI 000002bb Hashes for file member [l:13]'Defender.psd1' do not match.
Expected: {l:32 ml:33 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
2019-09-09 15:33:35, Info CSI 000002bc [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

:)

 

Hashes mismatch while copying data

When i'm copying data I've been getting hashes mismatch error even for basic files, is my hard drive failing?

 

Hashes mismatch while copying data

A hash is a numerical representation of a file. Basically, a complicated formula is applied to all the 0's and 1's and from that a long hexadecimal number is created. That number is called a 'hash.' (Not the same as the hash I smoke - that's different.)

When copying a large file (typically from the internet) you will frequently be shown the original file's hash. After copying the file you can calculate the hash of the copy with the same formula that was used to calculate the hash of the original. Now you
can compare the two hashes; if they are identical then the copy is identical to the original.

Therefore, a hash mismatch means that the file wasn't copied accurately. The cause depends on where you copied the file from and where you copied it to.

 

2019-05 update (KB4494441) corrupted msi.dll (hash mismatch)

Since the second “2019-05 Cumulative Update for Windows 10 Version 1809 for X64-based Systems (KB4494441)” update completed
every time I restart the laptop and every time I run an Office 2010 application I get the following error: “C:\WINDOWS\SYSTEM32\msi.dll is either not designed to run on Windows or it contains an error. …” The version of the Windows installer file
(msi.dll) is 5.0.17763.503. This is happening on my Lenovo Yoga 910-131KB Model 80VF laptop. It does not happen on my HP Pavilion mini-tower which also runs Windows 10 but has Office 2016 on it.
I ran “sfc /scannow” and the CBS.log error is “hash mismatch”. I uninstalled the update and the errors stopped. I reinstalled the update and the errors came back. How can I fix this?