What's new

SFC Scan Finding Corrupt Files Post Update


I have read elsewhere that the sfc/scannow issue is related to there being more than one version of opencl.dll. The version on the SB is fine, but sfc expects to see a different version, so it throws an error. The sources I read said that it is not a concern.

You are right about opencl.dll - but the DSIM rebuild process solved a whole bunch of other problems for me. Together with the two most recent updates, I now have a perfectly functioning SB.


New Member
The DISM thing is annoying. It seems to happen after windows updates on both my SP4's. I've found that I had to download an image of Windows 10 from MS. Then mount it and run DISM like this.

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess

Replace x with the drive letter of the mount.

Then run SFC /scsnnow again to fix the problems

Hope that's helpful