Windows 10: SFC /scannow after installing 1903 update produces corrupted unrepairable files

Once the Windows 1903 update was completed, I scanned my PC with sfc /scannow, which produced the following CBS.log file:

https://drive.google.com/file/d/1mdyHytDpBo97RgW639FGm6vZcubK3G_T/view

along with the message on the screen: Corrupted files were found, however the program is unable to repair them.


I would appreciate if someone could have a look at the CBS log file and let me know if any actions from my side are needed. Thanks in advance.

:)

 

Many unrepairable corrupted Defender files found by sfc /scannow

The answer is in the file descriptions -
The top one is the arm64 version
The middle one is the x86 version
The bottom one is the amd64 version.





But if you just run a standard WD definitions update, it will include the platform update without your having to do anything about KB4052623.

And, as previously reported by some early adopters, the SFC problem will be back afterwards. And it can be tackled in the same way as before***: restart, SFC, Dism, SFC, SFC {the final one just being for fun}.

*** You need to be connected to the internet for Dism to achieve anything. It uses WU to interrogate an MS web address as its source for file replacements, SFC already having discovered that the component store copy is also corrupt.

Denis

 

sfc /scannow found corrupted file that could not be corrected.


Help needed to repair corrupt files found after running sfc /scannow.



Running W 10 x64 Home Edition 1903 with latest updates installed.

Please redirect this thread if posted on the wrong place.

 

sfc/scannow corrupt file

sfc/scannow keeps finding corrupt files and fixing them