Windows 10: SFC Corrupt Issue Regarding OpenCl.dll

Hi guys.

I am hoping you can help me as i don't wish to do a full reinstall. Spoke to Microsoft who couldn't help. I have looked through the excellent tutorial posted on here with regards to SFC issues but i'm unsure if i am doing something incorrect as, the ISO i got from Microsoft website, has an install file with a .wmd extension.

I am on the following build:





When i run SFC i get corrupted files could not be repaired message:





I have saved the log of the above scan which i have attached. Please forgive me for the possibly dumb question but do i know download the 1511 iso? DISM is saying source files not found.

Any help would be greatly appreciated as the Tutorial steps don't seem to fix the problem unless its me which most likely is!

Apologies and thank you

Unfortunately unable to attach via thread so here is link for log Download CBSLog.txt from Sendspace.com - send big files the easy way

:)

 

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

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.

 

How to fix corrupted opencl.dll in Windows 10

Hi Martin,

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.

Thank You.

 

You need to supply more details of your computer, specifically if you have a Nvidea graphics card (there are some issues with that)

you can check the version you have as described here DISM - Repair Windows 10 Image - Page 13 - Windows 10 Forums

 

Windows 10 Pro 64bit.
AMD Radeon HD 7970
16GB Ram
I'm on latest build of W10 also.

 

OK please let us know what version of windows you arerunning (shown by winver) and what ISO you have as shown here DISM - Repair Windows 10 Image - Page 13 - Windows 10 Forums

You need to run dism with the option /source but with the same version as you are running.

 

Do i get the Techbench iso or MCT iso? The MCT iso didn't have a .wim file only .esd

Many thanks for your help

 

You need Techbench version.

EDIT: (and probably the correct language). You need the same one as you installed. Run this from elevated cmd prompt: Code: %systemroot%\system32\WindowsPowerShell\v1.0\powershell.exe -noexit [CultureInfo]::InstalledUICulture[/quote]

 

Many thanks. I will download and let you know.

Sorry but is there a way to determine the language? English or English international i am on? I live in UK.

 

English international. But run %systemroot%\system32\WindowsPowerShell\v1.0\powershell.exe -noexit [CultureInfo]::InstalledUICulture.

If it says en-US you want English. If it says en-GB you want International English.

 

Don't shoot the messenger *Wink

If it says this: Code: C:\Windows\system32>%systemroot%\system32\WindowsPowerShell\v1.0\powershell.exe -noexit [CultureInfo]::InstalledUICulture LCID Name DisplayName ---- ---- ----------- 1033 en-US English (United States) PS C:\Windows\system32>[/quote] Then you want English. If it says en-GB you want English International.

 

Many thanks for your help. I will let you know *Smile

 

Sorry to butt in here lx07, but he has chatted with me earlier about his graphic's card problem, and what he was telling me are the same errors with Opencl.dll file, that is happening with the newer Nvidia cards. This problem is a MS problem, and not a Nvidia problem. These two companies have to get together to solve this issue. Weather they will, or how long this might take is anybody's guess. I am surprised that this same problem affected this users AMD card thou.

 

Looking at latest log from SFC, it did mention AMD files so maybe AMD/Nvidia supply same files?

 

That I would not know, as I don't know very much about AMD cards, I've only bought and use Nvidia cards. But even in my CBS log files it never mentions Nvidia, it reports on the drivers, in this case Opencl.dll files, which Windows 10 will replace one of them and delete another one. Everytime.