SFC Corrupt Issue Regarding OpenCl.dll

Ache said:

Technical details:

The correct fix will be to remove wrongly installed and activated by Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 directory (Microsoft RemoteFX Display driver, 32bit part, which contains opencl.dll with reduced functionality, which overwrites correct Nvidia/ATI/Intel \SysWoW64\opencl.dll on upgrade or attempt of DISM recover from install.wim) from WinSxS (64bit counterpart is in amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586 .0_none_5fcf2a87752df0d7 directory, but is inactive and does no harm). But I know no tool for correct selective remove or deactivate of specific directory from WinSxS. Since \SysWoW64\opencl.dll is hardlink to WinSxS one, attempt to install Nvidia/ATI/Intel driver corrupts two Microsoft opencl.dlls at once (so sfc /scannow fails to recover), and attempt to recover WinSxS one from install.wim via DISM damages Nvidia/ATI/Intel display driver's opencl.dll from other hand.

Only problem is, we only have a FEW people that actually KNOW about this problem. Most people don't either know about this Opencl.DLL problem or care about the problem. So our chances of Microsoft fixing this any time soon, is VERY slim.

I try to make people aware at least on first few forums google show about the problem. Sorry I have absolutely no contacts with Microsoft developers and Microsoft support do their best to guard developers from users with template robotic answers like "reinstall your windows", so it is not easy task to bypass them, mission impossible. Probably someone from enterprise environment have.

EdTittel said:

I, too, have fallen prey to this issue, BUT my problem is even more *interesting* (in the sense of the Chinese curse): while SFC /scannow reports the opencl.dll files from Nvidia (>100K) as "corrupt", dism /online /cleanup-image /checkhealth tells me that my component store is fine, and not at all corrupted. Seems like waiting for a fix from MS is the only solution now, isn't it? Knowing now what Ache has shared, I don't want to replace the good, but reported corrupt Nvidia opencl.dll files with the bad, but reported good Microsoft opencl.dll files. Other suggestions?
--Ed--

Only suggestion is....wait for MS to fix their problem. That's it. Unless some computer expert can figure out how we can fix this problem ourselves.

After reading Ache's post, I ask myself, did I jump into windows 10 a bit too soon. Anyway, I'm interested in any feedback about a old-fashion solution and that is to remove all the drivers and return my video adapter card to an earlier version... say Geforce 9800.


Originally I had a GEforce 9800 in the system running Windows 8.1 32 bit with two DMI displays and life was good.

When I jumped to Windows 10 64-bit, I decided to move ahead in a newer adapter Gigabyte Nvidia GTX 750 Ti.

And there are the opencl.dll complaints given by the sfc /scannow.

Two items... is this complaint that I found in the windows log viewer something to really be concerned over at this point?

has anyone found that backing up to an older graphics card, seems to resolve this complain, or, once the damage is done, well the party is over until Microsoft comes up with a solution...

catholicfocus said:

After reading Ache's post, I ask myself, did I jump into windows 10 a bit too soon. Anyway, I'm interested in any feedback about a old-fashion solution and that is to remove all the drivers and return my video adapter card to an earlier version... say Geforce 9800.


Originally I had a GEforce 9800 in the system running Windows 8.1 32 bit with two DMI displays and life was good.

When I jumped to Windows 10 64-bit, I decided to move ahead in a newer adapter Gigabyte Nvidia GTX 750 Ti.

And there are the opencl.dll complaints given by the sfc /scannow.

Two items... is this complaint that I found in the windows log viewer something to really be concerned over at this point?

has anyone found that backing up to an older graphics card, seems to resolve this complain, or, once the damage is done, well the party is over until Microsoft comes up with a solution...

Well you have the exact same card as I am running on Windows 10. The problem with Opencl.dll is only a Microsoft problem, and when you run SFC /scannow it reports it. If this is the only problem sfc finds, then do not worry about it. Your system will run just fine. Now, their IS some good news about this issue. Some of our members who are in the Insider program, and are running newer versions of future windows updates, (beta) have reported that the issue with Opencl IS FIXED. This means that finally Microsoft has addressed this issue and fixed it. Also thou means that unless you are in the Insider program and testing future windows releases. You and I are going to have to wait a while longer until MS gives us this fix in a future update. But, just knowing that Microsoft has finally fixed this issue is good news for me, even if I have to wait a while longer for it to appear in an update.

I hate Microsoft... I hate Windows 10!!! But I dont want to go back Windows 8.1 or older Windows 10 have too many problems... and corrupted files are the big big big problem!!! Hope Microsoft fix this soon!

SeCrEt BoY said:

I hate Microsoft... I hate Windows 10!!! But I dont want to go back Windows 8.1 or older Windows 10 have too many problems... and corrupted files are the big big big problem!!! Hope Microsoft fix this soon!

Calm down.......we should be getting "some" updates tomorrow afternoon. Tomorrow is Update Tuesday.....what will be in this update....who knows....:)

Definitely a Windows 10 issue, as i posted in my thread on this same issue. I recently restored an older PC to either sell or keep and put Windows 8.1 Pro on it and a NVIDIA Graphics card and no reported issues from SFC at all on the OpenCl.dll.