Microsoft Fixing opencl.dll issue in SFC /SCANNOW soon

OldMike65 · 04 Aug 2016

Geneo said:

This appears to be fixed in the anniversary update. I get a clean SFC now.

Yup was actually fixed about 4 weeks ago on mine, BEFORE our anniversary update :)

MrBill · 04 Aug 2016

Yep, mine is clean too. Makes me happy.

Ohwell · 04 Aug 2016

Hi
I to can confirm that both 10pro devices now report no corruption of sfc folder...

Geneo · 04 Aug 2016

Some interesting new news. I tried to run Realbench - an Asus benchmark - and it fails with an error that says there is no opencl.dll on my computer! I am going to reinstall the NVidia drivers. Then run this and SFC. Sigh.

Geneo · 04 Aug 2016

I reinstalled the Nvidia driver, verified that programs using opencl work, and ran SFC with no errors.

So it is fixed, but be aware. The update removed the NVidia opencl.dll on my system, probably yours as well.

awalt · 05 Aug 2016

Not for me - it's in the NVIDIA folder, in System32\DriverStore\.....\, Windows\SysWOW64, and two WinSXS folders - I assume that's where it is supposed to be.

Geneo · 05 Aug 2016

and windows\system32 ? I see two versions there now. opencl.dll and nvopencl.dll. Bot are used.

OldMike65 · 05 Aug 2016

Geneo said:

and windows\system32 ? I see two versions there now. opencl.dll and nvopencl.dll. Bot are used.

Have not changed anything since our AU reguarding Opencl.dll here is my screen shot the way it looks now.

Microsoft Fixing opencl.dll issue in SFC /SCANNOW soon-opencl_latest.png

EdTittel · 05 Aug 2016

It is fixed on both of my unaltered Win10 Current Branch test machines, following the update. Hadn't checked status since before the last cumulative update though, so can't say definitively if it was fixed earlier on those machines or not. I can say it is fixed now, though.
--Ed--

bilateral · 03 Sep 2016

Hi, I had this problem with Opencl.dll error too, and my researches started with getting the SFC corruption message and difficulties using DISM to correct it (as so many had). I was also having serious display issues, but oddly, in my case, once I was able to clear corruption messages with SFC and DISM, my display problems also cleared up. (I say "oddly", because so many others said they felt a recent Nvidia driver worked better.) Except in my case, I never installed a display driver from Nvidia myself. So staying with the driver MS provided as correct and not corrupt, seems to be working better now, and I don't know how the "corrupt" driver installed by MS got corrupt. Heck, maybe it really was corrupt, and just giving the same corrupt message in SFC as others described here!?

My experiences sorting through these multiple issues are detailed on pp. 30-31 of this thread, particularly in posts #292-299:
DISM - Repair Windows 10 Image--Page 30

I am now getting ready to update to Ver 1607, so my question is, once Win 10 has done that, how many have stayed with the MS provided Nvidia driver for that version, and has anyone found it is worthwhile to go to the Nvidia driver page and install a different driver from there? If so, what benefit did you get?

Michael