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

Page 2 of 2 FirstFirst 12

  1. Posts : 71
    Windows 10 Pro
    Thread Starter
       15 Jun 2016 #11

    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.
      My ComputerSystem Spec

  2.    15 Jun 2016 #12

    RPmtl said: View Post
    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. :) 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. :)
      My ComputersSystem Spec

  3. Slartybart's Avatar
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       15 Jun 2016 #13

    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.
      My ComputerSystem Spec


  4. Posts : 71
    Windows 10 Pro
    Thread Starter
       15 Jun 2016 #14

    After doing a fresh NVidia driver install I searched for all versions of OpenCL.dll in the Windows directory. All 7 instances are v1.2.11.0 even though their dates vary from 2015-2016. It appears that NVidia is installing the same version of OpenCL.dll but with a newer install date and no harm would be done (no features lost) when 'sfc /scannow' replaces it with the older version.
      My ComputerSystem Spec

  5.    15 Jun 2016 #15

    RPmtl said: View Post
    After doing a fresh NVidia driver install I searched for all versions of OpenCL.dll in the Windows directory. All 7 instances are v1.2.11.0 even though their dates vary from 2015-2016. It appears that NVidia is installing the same version of OpenCL.dll but with a newer install date and no harm would be done (no features lost) when 'sfc /scannow' replaces it with the older version.
    That is correct the opencl.dll issue will not affect your system at all. This issue has been going on for at least the last 7 months, and MS has known about this for a VERY Long time. MS is still using Opencl.dll files dated 10/30/15 thou in the system folders!!! But does not do any harm to your computer. :)
      My ComputersSystem Spec

  6.    15 Jun 2016 #16

    Slartybart said: View Post
    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.
    It also REMOVES one of Nvidia's Opencl.dll files also.
    Yes MS should have this issue fixed within the next 4 or 5 years..... Maybe ....
      My ComputersSystem Spec

  7. Slartybart's Avatar
    Posts : 3,506
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       15 Jun 2016 #17

    RPmtl said: View Post
    After doing a fresh NVidia driver install I searched for all versions of OpenCL.dll in the Windows directory. All 7 instances are v1.2.11.0 even though their dates vary from 2015-2016. It appears that NVidia is installing the same version of OpenCL.dll but with a newer install date and no harm would be done (no features lost) when 'sfc /scannow' replaces it with the older version.
    Thanks - all versions the same ... SFC shouldn't report it or (my mistake) replace it . The issue is still that the component store and the dll winners/losers is out of whack.

    opencl.dll is not Nvidia specific, it just shows up there more than from other sources (Intel, AMD, and Game developers might also distribute an opencl.dll with their wares.

    Redstone1 is just around the corner, so we'll see if any resources were allocated to fixing opencl/SFC/SxS

    Thanks for marking your thread solved.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
I have been having these errors right after the upgrade. Once I did a clean install still having these same errors! I did sfc scan and says there is no problem at all. Can you guys kindly take a look and see if you have a solution or any idea...
Clean Install Errors - Bad SSD? in Installation and Upgrade
Was using computer like any other day and it became unresponsive. Music was still playing normally but nothing would respond. Couldn't even use CTRL+ALT+DEL. So I turned computer off. Restart wanted to do a 'Startup Repair', that seemed unresponsive...
Hi all, Operator skill level- medium - its been 4.5 years since my last build, zero experience installing Win8 or Win10 Brand new Clean install from full WIndows 10 USB3.0 retail package Gigabyte GA-970A-D3P motherboard AMD...
After attempting the 1511 upgrade (with disastrous results), I blew away the world and did a clean install of Windows 10, 1511 yesterday. It appears to be better - at least it'll boot consistently and be usable. Last evening, Windows popped up and...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:11.
Find Us