Windows 10: SFC some corrupt files can not be fixed

It can't be solved on Nvidia side. For compatibility reasons Nvidia can't change the name and directory of that dll nor accept functionally stripped Microsoft dll, i.e. can't change anything. It can be fixed only by Microsoft itself or by some tool which gracefully removes wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 from WinSxS

 

I know others who did this build and have NVIDIA and had no integrity violations. If there was an issue with OpenCL.dll used in place of, should get system errors in some way, not talking sfc violation issues.

 

It is possible that 32bit systems don't have this error or Nvidia card is pre-DX11.

 

For a second thought yours was, did say 64bit ? If this is correct not all systems, we would see a lot more posts on it then 2 or so.

 

I don't have this bug on 32bit notebook, but there is DX10 card too, I don't know which one plays role.
All that mess from Microsoft is part of RemoteFX Display driver which needs DX11.

 

Possibly count 3 posts including mine here on similar issue, you commented in same way on them.

 

It will be rather strange, if I'll say 4 different things on the same mater, isn't?

 

True, just happen to notice this and you joined on 18th. Appreciate input on matter.

 

Ok make it 4 posts. Been reading the posts here, same problem as both of you, and I agree this is an MS problem not Nvidia.
Here is a pic.....shows what you guys are talking about I believe.

 

Agreed I got it and I only have Intel Graphics and the OpenCL.dll that was corrupt was signed by Microsoft. DISM with /source fixed it though.

 

You should read more of these posts. SFC also fixed mine too, BUT it replaces the correct OpenCL from Nvidia to the in-correct version from MS. Look at the file sizes. MS one is 27kb Correct one from Nvidia is 103kb BIG difference.

 

Sorry to just jump in but I've just made an account so that I can give some input on this issue.

None of the DISM commands even in order worked for me (the source files could not be found) so I proceeded to take the install.esd file from C:\$WINDOWS.~BT\Sources and use the ESDtoISO tool in order to create a source to repair from.

It worked, 0 integrity violations. I thought I'd poke around a bit more, restart my machine, try and stream, play games etc and it was still fine until...

Last night I shut down my machine and upon returning to it this morning and running sfc /scannow the same problem arises, corrupt files and CBS.log showing it to be Opencl.dll

I've installed the new NVIDIA drivers (359.00) this morning and will try the fix again, although it seems likely after a few restarts or leaving the machine powered down for awhile the problem will come back.