SFC /SCANNOW shows opencl.dll bad

My box is windows 10 pro x64 and I tried to "SFC /SCANNOW", and got "opencl.dll bad" message as follows.

2016-02-12 11:46:45, Info CSI 00004f51 [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-02-12 11:46:45, Info CSI 00004f5b [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-02-12 11:46:45, Info CSI 00004f5c [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-02-12 11:46:45, Info CSI 00004f5f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-02-12 11:49:06, Info CSI 00006527 [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-02-12 11:49:06, Info CSI 0000652a [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-02-12 11:49:06, Info CSI 0000652b [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-02-12 11:49:06, Info CSI 0000652e [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

Please let me know how to resolve this.

Thanks in advance.

/bro67
I've googled and found this link, but not solved.
SFC SCANNOW report opencl.dll bad - Microsoft Community

JohnC/

Yhakns a lot for your kind comment. I'll try the thread you linked.

Just a little NEW information on the Opencl.dll issue's After downloading the latest drivers from Nvidia few days ago, Version 361.91
Then running sfc /scannow after installing the latest drivers, for the 1st time in the last 4 months, sfc found NO ERRORS!! Then I went and looked at my Opencl.dll drivers and location of them. Nvidia has changed how they install and where they place their drivers in this latest update. They do not replace the MS Opencl drivers like they did in the past with their updates, so looks like Nvidia has fixed the problem with Opencl errors .... at least for THIS latest update. I was VERY surprised to see this, as I kept thinking it was a problem from MS, not Nvidia.

Just thought I would post my results on the Opencl.dll errors that lots of us USED to get ... Until THIS new update. :)

bro67 said:

Everyone has known about the opencl-dll problem since 7, because it has been mainly with NVidia. When 10 came out, NVidia was late on putting the latest drivers in Microsoft's repository, so Microsoft used the drivers from Windows 8.1, until NVidia released updated the drivers aprox. 2 weeks after 10 was released out to the wild in Aug.

That's not correct as Windows 7 did not have issues with Nvidia drivers. Windows 10 the early version 10240 also had no problems with Nvidia drivers. I ran both versions on 2 computers, never had problems with any Nvidia drivers, until the release of Windows 1511, then lots of people starting have problems with any Nvidia driver, or updates. Until this latest release of 361.91 just recently.

bro67 said:

Not to argue, but it is correct. You will find a lot of Linux posts about the NVidia driver issues, same as some people were having issues with 7. It was more of a smaller percentage then what happened with 10.

Yes I did hear of Linux having issues with Nvidia cards, which was a Linux issue, not Nvidia's . Also heard Linux fixed this issue a while back......not just recently. But this being more of a Windows forum then Linux, we never discussed it as much in here. Windows 7 never had any issue with Nvidia drivers, as I ran it for a long time on both computers. Actually still got a 3rd computer with Windows 7 still installed, but I don't use that one anymore, its stored and offline. All my versions of Windows 7 was either Pro or Ultimate versions. :)