Windows 10: SFC Reports Corruption Issues on all 4 of my PCs (after recent update)

Greetings All,

A recent update (presumably the last Cumulative) caused SFC to uncover corrupted files (and the CBS files stuff) on three computers. On the first two I believed it involved a conflict between Malwarebytes and Windows, but on the third one I believe it's simply the update.

I run SFC after all major and minor Windows releases. Almost always perfect. This time? 4 for 4.

Anyone else?

Oh, the only fix I've managed for the first three was some relentless DISM RestoreHealth sessions. At least 3 times in a row.

:)

 

SFC reports corrupt files that cannot be repaired

Hi Jay,

For to better assist you with the SFC reports issue, we'd like to know the following:

• Have you installed any Windows updates prior to this issue?
  
• Please provide us a CBS logs for us to determine what is the file that cannot be repaired.
  

To get the logs, please follow the steps below:

• Open a Command Prompt (Admin).
  
• Copy and paste findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfclogs.txt”, then hit
  Enter. (This will create a sfclogs.txt file on your desktop).
  
• Open the sfclogs.txt and check the result of SFC scan.
  

Note: SFC cannot always fix corrupted files.

We're looking forward to your reply.

 

SFC reports corrupt files that cannot be repaired

My Surface Pro 4 does not appear to have any problems. But I periodically run System File Check. SFC now reports corrupt files that it cannot repair. I've tried running DISM using the basic restorehealth options. This never has worked without downloading
a fresh .iso copy of Windows, which is no longer available for download. I even tried the DISM from the repair environment. It ran successfully, but SFC still reports corrupt files that it cannot repair. What should I do? I don't want the Windows OS files
on my Surface to be corrupt. From the number of posts on this forum, this must be a common problem. None of the threads I've read suggests anything that I haven't already tried. As I said above, most of the suggestions involve running DISM without referring
to an ISO file. That's strange, since I've never seen that work.

 

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?