SFC some corrupt files can not be fixed

Hi Beast,

No nothing wrong with your hardware everybody running the 359.00 driver will have this "Corruption"

what is happening is Nvidia is replacing the Microsoft OpenCl.dll with one of their own in at least 2 locations probably more

the Nvidia Version is 103 KB the Microsoft version is 27 KB.

I expect this will be fixed either with a windows update or probably by NVidia in the next version of driver This issue did not exist prior to 359.00

I have manually replaced the OpenCl.dll in the C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\ folder and ran DISM and the problem was fixed but in the next reboot the Nvidia one was back again.

My recommendation is just to ignore it and probably the problem will go away soon. Keep in mind it is not really a corruption but just a mismatch between what Microsoft is expecting to be there and what actually is there. the file is NOT corrupted and actually does it's job.

The reason the NVidia is bigger is down to additional library code they have added for one of their features.

hope this helps

@Ratbone
I was on Nvidia's site reading some replies about Opencl problems from their users, the other day. Same problem we have. One of their "tech's" replies was.... "This problem is NOT a Nvidia problem but a Microsoft problem." This does not sound like Nvidia is going to change anything to me. I also agree with Nvidia. You can log on to their web site and read some of the questions and replies on their forum if you wish.

This problem can't be fixed on Nvidia side at all. Nvidia writes \SysWoW65\opencl.dll only and this name and place can't be changed because other programs expects it there. WinSxS copy is replaced too because this file is hardlinked to WinSxS, this hardlink made by Microsoft. Only Microsoft can fix this bug. Ask your Microsoft support to do it for you, you pay for it.

we will have to live with it for a while the only consolation is we know it is reported as a corruption but actually is not. The system works fine with the 103 KB version and as far as I know does not generate errors in the event log.

Ratbone said:

we will have to live with it for a while the only consolation is we know it is reported as a corruption but actually is not. The system works fine with the 103 KB version and as far as I know does not generate errors in the event log.

The conclusion is wrong, it is actually the corruption. Micrisoft's opencl.dll is corrupted. With its last strength Microsoft tries to fix it, but because it made hadrlink, original is corrupted too.
And it is completely unrelated question: what the hell Microsoft mock with opencl.dll?

Hi Ache,
please explain what is the nature of the corruption and how does it translate to system stability? I am currently running the Nvidia version (103 KB) and not the Microsoft version (27 KB). I can't see any obvious issues or error alerts relating to this opencl.dll.

am I missing a trick here?

It is corruption, if we look from the file integrity point, and it does not affect system stability in any variant.
This Microsoft file simple should not be there (corrupted or not corrupted). If it is there, its presence may negatively affects applications which use OpenCL API. This file belongs to Nvidia/ATI/Intel but not to Microsoft.

There already was two updates since 1511 and still opencl.dll is not fixed, regedit is not fixed.

got that. makes sense.
But what I has said to Beast is correct there is no point of rebuilding his system again because there is nothing we can do other than not installing the 350.00 NVidia driver to prevent it or not running SFC until this issue is fixed by Microsoft.

You guys must already know, but we did get a new update from MS last nite. KB3120677 which after installing also changes our build # to 10586.14 But I saw no changes concerning OpenCL.Dll

Hi guys. I'm new but just wanted to say i am glad i'm not the only one having this error! Been racking my brain trying to find a fix but now i know there is nothing wrong its very comforting to know.

I have an AMD Graphics card but i believe Nvidia produces OpenCl files too? This is what it states in the latest SFC log anyway. DISM cant find source files and everything i've tried doesn't work.

0003c5d [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

00003c67 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

CSI 00003c67 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch