Windows 10: Microsoft Fixing opencl.dll issue in SFC /SCANNOW soon

Source:
The System File Checker (sfc.exe) may incorrectly report that opencl.dll is corrupt in Windows 10-Microsoft community

 

C/P
Anannya Podder replied on March 24, 2016

• Microsoft Support Engineer
  
  
  Hello,
  
  This issue may occur in Windows 10 Version 1511. When you install Windows, it installs a version of opencl.dll. However hardware drivers may also install their own version of opencl.dll, and if the driver version is different than the one installed by Windows, SFC may report this as file corruption and may not replace the file.
  
  When this happens, the opencl.dll file is not actually corrupt. It is not necessary that you take any action – the report that opencl.dll is corrupt can be safely ignored.
  
  Microsoft is aware of this problem with Windows 10 Version 1511 and is working on a resolution.

:)

 

Windows 10 perflib 1008 error

I am getting the same wmiaprpl error about once a day. sfc /scannow doesn't find any relevant issues, and I can't run DISM until Microsoft finally fixes the false opencl.dll errors that you get if you're using the latest NVidia drivers. Running DISM would
replace NVidia's 100k+ opencl.dll with Microsoft's 30k limited functionality one.

At any rate, I don't think DISM would fix this issue anyway, since no related errors appear in sfc /scannow.

My antivirus is Bitdefender Total Security 2016, by the way, just in case it's somehow relevant.

 

Sfc error CBS.log in windows 10

I too find Windows 10 Build 1511 problematic for the exact same reason: OpenCL.dll is accused of being "corrupt" by sfc /scannow and no amount of DISM calls will fix it.

This one is on you, Microsoft.

Fix it.

 

Should have already been fixed IMO.

 

FWIW, when I checked one of the Insider Preview builds a while back (maybe 3 or 4 releases ago), it was fixed in that branch of the code. I opined at the time in my Windows Enterprise Desktop blog that when the Redstone branch converges with the Current Branch, the repair will also come through. This sounds like it may actually happen sooner than that...
HTH,
--Ed--

 

Microsoft Acknowledges System File Checker Issue in Windows 10 Version 1511
A fix is on its way, the company says in a Statement

Microsoft has recently acknowledged an issue with the System File Checker (sfc.exe) in Windows 10 version 1511 (November Update), explaining that the company is already working on a fix that should be released very soon to users.

Read more: http://news.softpedia.com/news/micro...1-502258.shtml

The System File Checker (sfc.exe) may incorrectly report that opencl.dll is corrupt in Windows 10




http://answers.microsoft.com/en-us/w...4dadd8b?auth=1

 

Thanks for the info. *Smile

 

even a minor issue take good time to fix... maybe because its not critical it got delayed many times ?

anyway ms have yet to fix plaguing TDR issue on win10

 

Thank you so much for your complementary info Sumit Dhiman, Kyhi, Geneo, EdTittel, Cluster Head, Pendaws and slyphnier !
Warm regards.

 

Thanks for this update guys, this still plagues me even though some users are no longer affected by this issue.
I do not bother running SFC lately after updating a Graphics driver, last time i did it showed this.

 

So I spent insane number of hours for nothing.
At least now I know it isn't my computer corrupted.

 

Been so many posts on this here in the past, we kind of knew it was an MS issue then.

 

This right after myself having to restore after an SFC 'repair'

 

Easy for you to say.
I do not have the computer expertise to make such a bold determination by myself.
The only thing in my mind was to find a solution. I suppose that is normal for most people.