Windows 10: 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.

Please let me know how to resolve this.

Thanks in advance.

:)

 

SFC /SCANNOW report opencl.dll bad

Just to confirm what PiKohler posted later in this thread, Anniversary Update has cured the inability of sfc /scannow to complete. Whether they fixed the bad opencl.dll thing or it was something else, no idea. But sfc /scannow now works and reports all
is well with my Windows 10 Pro 64 bit Anniversary Update.

 

SFC /SCANNOW report opencl.dll bad

Just executed the Windows 10 Anniversary Update and it works now, finally

 

Have you tried searching for solutions yet, or just wanting us to walk you through the easy steps to fix this issue. Your problem is not with Windows 10, it is with your Video Chipset driver.

 

Opencl.dll hash mismatch is a known problem with Nvidia drivers. See the SFC command tutorial here SFC Command - Run in Windows 10 - Page 12 - Windows 10 Forums . The advice has been to ignore it when running the SFC command.

 

/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.

 

Again your problem is not with SFC or Windows. It is with OpenCL.dll which is caused by the Video Drivers. Try using the correct search, instead of the command that gave you the error.

 

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. *Smile

 

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.

 

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. *Smile

 

We have to look at both sides, because the OpenGL standard is what we are dealing with. Also Windows 10 has a lot more Updated code that was not in 7 & 8.

NVidia has always been behind the curve. You have to keep an eye on the Linux forums, since they are going to discuss any issues with video and audio more then the Windows forums.

 

The main point is the fact the Linux issue was a Linux programming problem and NOT a Nvidia problem. Nvidia did nothing to correct THEIR drivers for Linux. It was Linux that made the changes. But on the Windows 10 side of this, Nvidia has made a change in how its installed into Windows 10. MS has not as of yet anyhow made ANY changes to address the issue, so Nvidia changed into which directories it installs their Opencl.dll files in their latest release, which for now, has fixed the issue with the Opencl.dll file not passing the SFC Scannow process, as it no longer overwrites the MS opencl.dll files.

We HAVE been discussing this issue for MONTHS on THIS Forum bty..... I know cause I have been doing it myself along with others since we changed to Windows 1511 builds. We did not discuss this prior to the release of Windows build 1511 because their was no problem with Nvidia drivers BEFORE Windows 10 build 1511.

 

Again Linux is not different programming. It uses C & C++. The drivers for NVidea do not care about if it is Windows, since they are written on the OpenGL platform.

OpenGL does not care if it is Linux, Mac OS-X or Windows. DirectX has not been used by NVidea or AMD for about two years now. That is because OpenGL and OpenGL ES is Cross Platform capable, where as Microsoft's proprietary DirectX and Direct3D are not.

The problem when 10 came out. Microsoft did not update NVidea plane and simple.

Microsoft has a very bad habit in using extortion on chipset manufacturers to play by their rules.