Windows 10: SFC/SCANNOW

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-07-19 10:11:31, Info CSI 00003e90 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'


This is just one of many error that i recieved after the scan. It resolved the issue i was having with the update but then it identified many more errors..My PC runs fine so i dont know how this problem will effect my Pc.

:)

 

SFC scannow not working but verify only is working

there is no problem in chkdsk I've checked When I select command prompt and sfc scannow from f8 and repair.. it shows that a reboot is required for pending repair and pending renames folder in winsxs is full of files.. what should I do??

 

sfc /scannow error

Thanks.
After above steps, I rebooted my laptop and did sfc /scannow. It is OK now.

 

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: