Windows 10: 'SFC /scannow' errors on clean install

I decided to run 'SFC /scannow' on my recent clean install of Windows 10 and was surprised that it reported so many errors that cannot be repaired. I installed on a 256GB Samsung Pro SSD. After trying a few recommended fixes that all failed I decided to do clean install on a second SSD which I just finished doing. The only thing I've done is install Win10 Pro from a USB flash drive, install the motherboard drivers and then let Windows do an update. The update also downloaded and installed the NVidia graphics driver. Then when I ran 'SFC /scannow' the errors were there. Many seem related to the openCL.dll as well as other files that seem related to the Nvidia driver.

I have 4 other PCs running Win10 and they all pass 'SFC /scannow' without any problems.

Have any other folks noticed anything strange about Nvidia drivers?

Next step is to do a refresh install and run 'SFC /scannow' before the video driver installs...

:)

 

sfc /scannow error

just for checking for any errors in my computer just like that. i had done this as well on my old computer and had that problem even after it had been formatted.

 

sfc /scannow error

sfc / scannow ----- ERROR

 

Seems it's a known issue:

http://answers.microsoft.com/en-us/w...89d137b?page=6

 

The Nvidia drivers replace this opencl.dll file by their own version, it certainly is a known issue that is easily fixed, though it is also an issue that doesn't do any harm to the system.

 

Do you know how to fix it on a system that's already installed??

I started over again with a clean install, but this time I disconnected the Ethernet cable, installed the basic motherboard drivers, installed the latest NVidia driver (368.39) that I had previously downloaded, and then turned off auto install device drivers in the Device Installation Settings. I then connected to the Web and proceeded with updates, etc..

Running Scannow currently reports no errors. From what I've read on that MS thread the error seems to be caused by allowing MS to install the NVidia driver, or perhaps it's the version of driver they use. But after installing the newest NVidia driver (368.39) the problem seems resolved.

Perhaps performance is not impacted. But I would prefer it if 'sfc /scannow' did not report problems that it cannot fix, nor can the various DISM commands.

 

I have helped fixing this issue many times, but it can return if a Nvidia driver is being installed again afterwards.
I believe Microsoft had fixed this issue some time again, but I'm not 100% certain though.

 

Just read more about configuring "dism /online /cleanup-image /restorehealth" to access a mounted Windows 10 ISO:

Dism problem - Windows 10 Forums

Perhaps that will work as DISM previously resulted in "The source files could not be found.".

Seems easy enough ...

PS: Just saw your reply AXE. I'll see if the above fix works and also look for previous replies to similar reports of the same issue on this forum. Thank you for helping

 

What fix do you mean? I did not yet post any fix/suggestion in this thread.

 

I've never seen this Opencl.dll issue fixed yet myself, its still the only problem sfc finds on my computer for many months. What sfc will do is delete 2 files from Nvidia, then replace them with the MS files dated 10/30/15 which are VERY OLD. *Sad

 

You wrote "I have helped fixing this issue many times" which pointed me to searching more on this forum as you made me realize that I was finding an old problem. I downloaded the ISO and ran the recommended DISM command to use that ISO to do the repairs and it worked.
After a reboot I ran 'sfc / scannow' and all is well*Thumbs



There were a lot of other reported file errors so this fixed them too. I'll now reinstall the NVIDIA driver and know that it will restore it's own (newer) version of OpenCL.DLL which 'sfc / scannow' will complain about. But at least I now know what is causing the issue and all the file errors other than that one are fixed.

As OldMike65 said - it's still an unresolved issue and I'm sure someone will post any fix on this forum when/if that happens.

 

Oh you meant that way *Smile

Glad to hear.

 

I just uninstalled and reinstalled the NVidia 368.39 driver to see what would happen when I again tried to run 'sfc /scannow'. This time it simply reported that it found and fixed an error - which is a LOT better then what was happening previously where it was unable to repair whatever it found. So in a sense it looks like the opencl.dll problem is fixed as far as running 'sfc /scannow' is concerned.

 

Sorry its not fixed, what sfc did was remove one of the drivers from Nvidia , use to remove 2 now its down to one.
I make screenshots of before and after a new update, so I can confirm this. *Smile On your next update from Nvidia the whole process will be the same IF you run sfc .... Plus those results are in your CBS log too. Way at the Bottom. *Smile

 

RPmtl, the opencl.dll issue is a reporting issue, not an operational issue.

SFC sees a mismatch between component store and the installed version and reports it. SFC shouldn't do that and MS is working to fix the reporting.

The opencl.dll error in SFC can safely be ignored.