Every time I performed a Clean Fresh installation, then running SFC /SCANNOW, I would get no integrity violations found. Alas, when I perform a Windows 10 Build Upgrade (through Windows Update) then run SFC /SCANNOW, I surprisingly get corrupt files found, some are fixed and some it could not fix.. I don't know the exact reason for this and I am not the only one facing this issue, it probably happens during extracting/expanding or moving/writing of the files. However, I got fed up with this problem and thought I will try to restore the system health using an ISO image; so I tried this: Mounted the latest ISO image that includes install.wim (not "install.esd", I tried it and it did not work) to X: drive (replace X with your appropriate drive letter). Started Command Prompt (Admin) and run the following instructions: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /limitaccess C:\WINDOWS\system32>Dism /Online /Cleanup-Image /ScanHealth C:\WINDOWS\system32>SFC /ScanNow It seems to have worked and I got the message: Windows Resource Protection did not find any integrity violations. Update: The "esd" based statement below does actually work, I must have made a mistake somewhere. C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:X:\sources\install.esd:1 /limitaccess I forgot to add: When I executed "winver" after the above fix, I got [Version 1511 (OS Build 10586.3)]. But I had suspicions that KB3103688 and KB3105211 may have also been partially overwritten by the process, so I placed the two .CAB files in a directory named (C:\Wupdates) and performed a manual Windows Update through Administrator's Command Prompt, like the example below: C:\WINDOWS\system32>dism /online /add-package /packagepath:C:\Wupdates\kb3105211.cab
You could use this string to find out what's the cause of the error(s): Code: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
@Enthousiast, Thank you for the feedback, I have already looked into the CBS.LOG file, and while the error messages may indicate where and why the error message is produced (like file content or version mismatch), it does not tell you what caused the corruption, like is it a problem with the hard disk, memory, or even a hardware or software setting, etc... However, while only experience and experimentation may lead you to find the reason behind some failures, I thought other members may find it helpful in fixing their issues quickly.
this is the best solution :Dism /Online /Cleanup-Image /RestoreHealth after that run sfc /scannow to see if you have any error or run powershell admin this to check health : Repair-WindowsImage -Online -ScanHealth
2015-11-15 16:18:09, Info CSI 00005725 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-15 16:18:09, Info CSI 00005728 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-11-15 16:18:09, Info CSI 00005729 [SR] This component was referenced by [l:80]"Microsoft-Windows-TabletPC-Package~31bf3856ad364e35~amd64~~10.0.10586.0.TabletPC" 2015-11-15 16:18:10, Info CSI 0000572b [SR] Could not reproject corrupted file [l:78 ml:79]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC"\[l:19]"Windows Journal.lnk"; source file in store is also corrupted