Windows 10: Corrupted data and failed SFC, DISM, and CHKDISK

I seem to have files that cannot be fixed no matter what I try. Things I've tried: - sfc /scannow many times, each time stopping at 17% and saying the following: Windows Resource Protection could not perform the requested operation - DISM /online /cleanup-image /scanhealth. It stops at 85.5% and says the following: Error: 23 Data error cyclic redundancy check. - DISM /online /cleanup-image /restorehealth. It stops at 53% and says the same error above. - All three of these in safe mode with the same results. - CHKDSK /r, CHKDSK /f /r c:, and running Check Disk from C drive properties

:)

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.

 

How to get damn DISM to work?

you need to run DISM first before running SFC
SFC query's the local component stores to make repairs
DISM is targeted for rebuilding the component stores and a offline image the 'live' section is still handled by SFC in some cases
except on windows 8.1 and up because they changed it
but only for certain files and only if x part of the store is corrupt
so yea pretty confusing eh

 

Windows 10: sfc and dism cannot repair corruption

I was finally able to repair my Windows installation such that SFC returned a normal result.

Using a freshly downloaded USB image of W10, I did an inplace upgrade as suggested in magicandre1981's comments.

After that, there was a different file that was corrupt and could not be repaired.

Again, DISM did not initially repair this. However, I was able to determine that the file in question was located in the C:\windows\winsxs and also the C:\windows\system32 folders.

Since the previous installation did not flag that file as corrupt, I figured I could use the previous installations copy of that file as a good file.

Before running DISM again, I executed the following from an elevated command prompt and then re-booted the machine, as per instructions in an article at thewindowsclub.com which is not presently accessible. I'm not sure if the reboot is necessary, as that is not mentioned in another article.

By running DISM, and using c:\windows.old\windows\winsxs as the Source, I was able to repair the store. And then running SFC resulted in the original file being repaired.

Why this is happening, I have no idea. On a different machine, (and different internet connection/ISP) the upgraded (from W7) W10 installation also showed a corrupt file when running SFC. On that machine, DISM was able to repair it using the default Windows Update as a source.