'SFC /scannow' errors on clean install

Page 2 of 2 FirstFirst 12

  1. Posts : 84
    Windows 10 Pro 1909
    Thread Starter
       #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 Computers


  2. Posts : 134,174
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #12

    RPmtl said:
    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 Computers


  3. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #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 Computer


  4. Posts : 84
    Windows 10 Pro 1909
    Thread Starter
       #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 Computers


  5. Posts : 134,174
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #15

    RPmtl said:
    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 Computers


  6. Posts : 134,174
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #16

    Slartybart said:
    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 Computers


  7. Posts : 3,502
    Win_8.1-Pro, Win_10.1607-Pro, Mint_17.3
       #17

    RPmtl said:
    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 Computer


 

  Related Discussions
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 23:37.
Find Us




Windows 10 Forums