Windows 10: SFC says it fixed corrupted files BUT run it again and I get the same result. BTW - DISM...

SFC says it fixed corrupted files BUT run it again and I get the same result. BTW - DISM All options runs clean.

:)

 

Dism says files are clean but sfc claims corrupt

Hello from NC, I usually run sfc on a periodic basis..monthly or so. I tested out the MS offer to download and install the Feature update to Windows 10, version 21H1. Everything seemed to go OK but then I ran sfc. The claim was unrepairable corrupt files. I tried DISM /RestoreHealth but it too claimed it couldn't fix the image. Since I couldn't find a version 19043 I backed out the Feature update which put me back to 19042 and Rufus located a matching copy and I mounted it. The commands I used were: DISM /Online /Cleanup-Image /StartComponentCleanup DISM /Online /Cleanup-Image /AnalyzeComponentStore and DISM /Online /Cleanup-Image /RestoreHealth /source:N:sources\install.wim:6 /LimitAccess Dism seemed happy so after a reboot I ran sfc which claimed it couldn't repair corrupt files. So now I have sfc saying 'dirty' and DISM saying 'clean'. Anybody any ideas as to how to get sfc to agree with Dism? I looked at the log files that sfc produced and they were pristine with no complaints. Thanks for any ideas,

 

Corrupted files - DISM or SFC results more accurate?


I've just built a completely fresh installation of the latest build of Win 10 Pro x64 (10586.3, also referred to as 1511).

I've done the necessary apps installs, software configuration and ended up with running SFC scan, which suggested my 'opencl.dll' library (related to some remote VPN, not nVidia drivers) was corrupted. I've run DISM that wasn't able to repair the issue by itself but when linked to source, it fixed the problem (well, at least it claimed to have fixed it). However SFC scans still end up with presenting the same issue... *Sad

I've tried DISM repair multiple times, each time apparently with success, but SFC still returns a hash mismatch for this dll. At the same time DISM integrity scans show no errors. *Huh

I've read that DISM is commonly considered a more reliable tool than SFC and SFC can sometimes return false positives when run. However, all discussions I've scanned referred to Windows 7 or 8/8.1 - none of them addressed the issue in Windows 10.

Moreover - I run SFC on my other machine that had been upgraded to Win 10 (from 8.1) some time ago and the same error appeared. Surprisingly here, after running DISM fix, SFC doesn't find any errors! The machine runs Win 10 Pro x64, exactly the same build! The only difference is that this one was upgraded and the other was freshly installed. *Mad

Thus, the question is - shall I be bothered by the fact SFC returns an error? Or shall I rather stick to DISM output which say everything is fine?

 

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