Z
zBernie
Updates have been failing on my wife's computer for several months now. It is stuck at version 1903. I've tried various permutations of these commands:
sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
I just tried an update using this link which also failed with the error: "something went wrong error 0x800701b1"
There are errors in the CBS.log file which indicate hash mismatches some of which are shown below. I've read that this was caused by an out of band Windows update.
At this juncture I believe the only solution may be to do a clean install, unless someone has a better suggestion.
C:\Windows\Logs\CBS\CBS.log:
2020-08-15 20:00:41, Info CSI 000002be [SR] Beginning Verify and Repair transaction
2020-08-15 20:00:41, Info CSI 000002bf Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
2020-08-15 20:00:41, Info CSI 000002c0 [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
2020-08-15 20:00:41, Info CSI 000002c1 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2020-08-15 20:00:41, Info CSI 000002c2 [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
Continue reading...
sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
I just tried an update using this link which also failed with the error: "something went wrong error 0x800701b1"
Download Windows 10
www.microsoft.com
There are errors in the CBS.log file which indicate hash mismatches some of which are shown below. I've read that this was caused by an out of band Windows update.
At this juncture I believe the only solution may be to do a clean install, unless someone has a better suggestion.
C:\Windows\Logs\CBS\CBS.log:
2020-08-15 20:00:41, Info CSI 000002be [SR] Beginning Verify and Repair transaction
2020-08-15 20:00:41, Info CSI 000002bf Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
2020-08-15 20:00:41, Info CSI 000002c0 [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
2020-08-15 20:00:41, Info CSI 000002c1 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2020-08-15 20:00:41, Info CSI 000002c2 [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
Continue reading...