SFC some corrupt files can not be fixed

Saltgrass said:

I am not sure why folks are having problems with this. I have not seen it so far and am running the 353.82 version of the Nvidia drivers. My install is an updated 10240 version which hasn't been used much.

Since the opencl.dll file seems to be part of the WDDM driver which update apart from the Nvidia drivers, has anyone seen one of those drivers being installed? Nvidia is using an nvopencl.dll file on my system although I cannot be sure it doesn't interact with the other one.

We have seen SFC errors like this before. When Microsoft was changing the servers around we have several files which showed the problem, but one update cleared that up. I am still seeing Metadata errors and DeviceSetup warning messages in Event Viewer.

Has anyone with a problematic system checked the DISM log after trying that fix. Maybe it would yield more info about the situation. I know there are some listings in this thread so I will go back and check if any of them come from the dism.log file.

I thought this problem started from 359.00?

This problem started on 64bit systems only with so-called TH2 or 1511 or 10586 Windows version with any Nvidia/ATI driver.

Well, that's weird then because I have the same problem with the base build of Windows 10 (TH1) and 359.00?

Perhaps they recently update their RemoteFX driver for TH1 too. I don't have this problem before.

kevindd992002 said:

Well, that's weird then because I have the same problem with the base build of Windows 10 (TH1) and 359.00?

You do know that Nvidia just released a new driver today, version 359.06 Just thought I'd mention it.

I was reading some complaints a few min's ago on Microsoft Support forum. users were complaining about their Opencl problems and SFC showing corrupt files after updating their Nvivida drivers. Here is one users reply. Think some of us already know this, but thought I would post this persons response.

"Yeah. As far as I can tell, part of the problem is that the opencl.dll file is from NVidia. It is a new version of said file from an updated graphics driver that I downloaded and installed from the NVidia website. However, for whatever reason, Windows appears to have an outdated cache (or whatever) of what the file is supposed to look and/or be like. That said, I believe the SFC gives a false positive for corruption.

In short: Windows believes the file is corrupt when actually the file may just be a very new version and therefore not recognized.

TL;DR ver.: Just ignore the error message for that specific file (for now). Windows is just being dumb again."

That last line he wrote, kinda somes it right up!!! :)

Hmmmm, I am also using Nvidia drivers. I literally just posted my issue at the end of this thread. Is it the same thing? I also had SFC errors after updating to the latest drivers today.

Error DISM restorehealth - Page 5 - Windows 10 Forums

OldMike65 said:

You do know that Nvidia just released a new driver today, version 359.06 Just thought I'd mention it.

Release notes show no mention of this issue, thanks for update !
http://us.download.nvidia.com/Window...ease-notes.pdf

OldMike65 said:

You do know that Nvidia just released a new driver today, version 359.06 Just thought I'd mention it.

Yes, I actually just downloaded it now and will try to see how it goes. I kinda figured that it's just Windows not recognizing that the updated opencl.dll from NVIDIA is not a corruption to the system.

And yes, I immediately searched for opencl.dll in the release notes and do not see any mention of a fix to the problem.

kevindd992002 said:

Yes, I actually just downloaded it now and will try to see how it goes. I kinda figured that it's just Windows not recognizing that the updated opencl.dll from NVIDIA is not a corruption to the system.

And yes, I immediately searched for opencl.dll in the release notes and do not see any mention of a fix to the problem.

So soon for a new one, released based on 2 games, game ready driver update, Just Cause 3 and Rainbow Six Siege.