Run SFC Command in Windows 10  

Brink said:

Yep, it's for the NVIDIA "opencl.dll" bug. Nothing to worry about. :)

Thanks. I did a scan right after the OS installed and it found the same Nvidia bug, probably because a older Nvidia driver was installed when the OS was started for the first time.

OldMike65 said:

Shawn with the NEWEST update from Nvidia they have FIXED the Opencl.dll issue. They have changed the way it installs into the different directories, which fixes the problem. Now when I run SFC /Scannow it finds NO ERRORS

I have the lastest Nvidia driver for my GTX 980Ti 361.91. I used Display driver uninstaller before I installed it too. Windows downloaded a old July Nvidia driver after starting the OS for the first time though.

MUGEN02 said:

I have the lastest Nvidia driver for my GTX 980Ti 361.91. I used Display driver uninstaller before I installed it too.

That's the same version I have installed, and for the 1st time in months, sfc shows no errors due to Opencl.dll Strange that yours still does??

MUGEN02 said:

I have the lastest Nvidia driver for my GTX 980Ti 361.91. I used Display driver uninstaller before I installed it too. Windows downloaded a old July Nvidia driver after starting the OS for the first time though.

Then that's why, as I don't let Windows install any drivers, I only want the drivers from the Manufacture NOT from MS maybe that's why ???



Check in your device manager for the version, should look something like this.

OldMike65 said:

Then that's why, as I don't let Windows install any drivers, I only want the drivers from the Manufacture NOT from MS maybe that's why ???



Check in your device manager for the version, should look something like this.

I show the same on my PC. Is there a way I can fix the Opencl.dll files or I don't have to?

MUGEN02 said:

I show the same on my PC. Is there a way I can fix the Opencl.dll files or I don't have to?

Only fix I know of was downloading NVidia's latest driver. If it didn't work for you, not much else you can do.

Actually I am surprised sfc /scannow didn't repair the problem, with me, it always fixed the opencl.dll issue by deleting 1 of the opencl files and replacing 2 others. THEN sfc /scannow would run without errors.

OldMike65 said:

Only fix I know of was downloading NVidia's latest driver. If it didn't work for you, not much else you can do.

Hopefully doing the same install steps on the next Nvidia drivers will fix this problem, I bet a new one will be released this or next week. Based on the OP I can safely ignore this bug anyway?

MUGEN02 said:

Hopefully doing the same install steps on the next Nvidia drivers will fix this problem, I bet a new one will be released this or next week. Based on the OP I can safely ignore this bug anyway?

Yes its ok, will not harm or affect your computer :)

Here is my latest screenshot of what Nvidia did to change the way it installed their opencl.dll files, which gives me NO ERRORS.



Notice the file dates.....these are the latest ones from Nvidia and did not change the ones installed by MS.

MUGEN02 said:

Hopefully doing the same install steps on the next Nvidia drivers will fix this problem, I bet a new one will be released this or next week. Based on the OP I can safely ignore this bug anyway?

I upgraded to 362.00 and still have the nvidia bug. I used DDU and clean install.

sfcdetails.txt