Hello VBs, :)
The hash mismatch for the opencl.dll file found by SFC is only a bug for the NIVIDIA driver. It's safe to ignore until NIVIDIA fixes it in the next driver release.
He may have an Intel graphic chip, but he may also have NVIDIA as well like mine.
Either way, there's no need to do anything to fix it.
Oh ok, got it. Thanks for the clarification.
Thank you for fast response.
PC that has error definitely doesn't have any GPU other than one integrated with Intel CPU. It's operating as headless server (mostly for running hyper-v and storage spaces), so no other graphics card is necessary (it's not laptop with hybrid graphics). Scan was performed in RDP connection from PC with nVidia card, but strangely enough that PC with nvidia card shows no errors when running sfc /scannow. Does running sfc /scannow when connected in RDP has anything to do with errors?
It shouldn't. The main issue is a has mismatch with the opencl.dll file.
This was an issue recently from NIVIDIA, but was fixed in the current driver release. Maybe Intel has the issue now?
Hopefully the latest Intel graphics driver or next will sort it.
Really the opencl.dll issue was fixed by Nvidia in the latest release?? If you run sfc /verify its still shows the same error. I used that command 1st, because I didn't want Windows to remove 1 of the opencl.dll files. like it would if I ran sfc / scannow are you sure its fixed Shawn???
I did see where in one of the new releases of the Insider builds it WAS fixed, by Microsoft, but I don't run any of the Insider builds.
Update: After I read where one of the folks who are in the Insider program, reported this issue was fixed in one of the new Insider releases, It made me VERY happy knowing that at some point MS will release a future update that will fix this issue. :)
Last edited by OldMike65; 25 Dec 2015 at 11:19.
Hey Mike,
I just ran SFC /SCANNOW as a test using the latest 361.43 NIVIDIA driver, and SFC came back with no issues. Looks like it's sorted now.
Quote
