Windows 10: SFC errors - how to identify/fix?

As one (not particularly hopeful) step in trouble-shooting a problem (Cortana not opening reliably) I used sfc /scannow from an elevated command. At its conclusion I got this message:

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."

I opened that log file - but it's 52,000 lines long! How could a user be expected to isolate it from that? More important, what are suggested ways for me to proceed please? Apart from ignoring the unidentified problem(s).

--
Terry, East Grinstead, UK

:)

 

How do I identify and fix registry errors in Windows 10

Jim,

What problems have you encountered that you think might be resolved by fixing registry errors

`~`

 

How do I identify and fix registry errors in Windows 10

How do I identify and fix registry errors in Windows 10

 

Meanwhile I thought I'd search that huge log file for the string 'cannot repair' in my text editor. These were the only two lines, almost identical. Do they provide the experts with any clues I can pursue please?

2016-07-14 16:07:10, Info CSI 00005561 [SR] Cannot
repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2016-07-14 16:07:10, Info CSI 0000555e [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8b:31bf3856ad364e35} in the store, hash mismatch

Searching my OS drive I found three examples of the (implicated ?) file, all different sizes:

OpenCLDLL C:\Windows\$ystem32 98 KB 17/06/2016 00:16

opencl.dll
C:\WindowsRWinSxSKamdf?evgwddmd?1.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf238??52df0d7
34 KB 13/02/2016 18:13

opencl.dll
C:\WindowskWinSxSRwow?Lmicrosoft-windows-r..mddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22
102 KB 17/06/2016 00:16

--
Terry, East Grinstead, UK

 

Hi Terrypin,

Welcome to the 10forums *Smile

The opencl.dll is a known issue, kinda a bug with SFC, it is quite easy to resolve it but it is not harmful and does not affect anything on the system *Smile

In many cases this issue starts due to driver updates from Nvidia, these driver updates replaces the opencl.dll from Windows with their own (newer) version.
In other cases I'm not sure how it happens.

 

It's best to delete the CBS.log + Dism.log before running sfc or dism commands. Windows will create a brand new log file for each which contains only the latest error/problem.

NOTE: CBS.log sometimes is locked by tiworker.exe process, you'd need to keep trying until it's deleted.

 

Thanks both, appreciate those helpful (and rather reassuring!) replies.

Terry, UK