Windows 10 - opencl.dll replaced with incorrect version after each upgrade for the last 7 months RRS feed

All replies

  • Hi,

    As I know, during Windows update or upgrade, the driver which manufacturer delivered onto Windows update server will be reinstalled.

    Please understand the driver update process in Windows here:


    For forbidding the driver update automatically, you can try this option:

    How to temporarily prevent a Windows or driver update from reinstalling in Windows 10

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 7, 2016 7:33 AM
  • One piece of information I remembered incorrectly because I first investigated this a long time ago, the correct version of the file is actually completely missing from system32 after the upgrade, and only an incorrect version remains, in SYSWOW64, that seems to be related to RemoteFX. 

    Anyway, that's a plausible explanation, that the driver is replaced with the one from Windows Update that may not include that file.

    However, that doesn't explain why running a SFC scan after installing the latest NVidia driver package reports opencl.dll as corrupted/invalid. The version of opencl.dll provided by the NVidia driver works fine with folding@home, despite the SFC corruption warnings.

    The SFC corruption warning about opencl.dll is related to microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, not to the NVidia driver.

    So I think there's some kind of conflict here between the Windows provided opencl.dll from the RemoteFX package, and the NVidia provided opencl.dll file.

    I'm not even sure opencl.dll is part of the NVidia "driver" itself. It comes with the NVidia driver package, but the display driver is just one component of that package, and opencl.dll seems to be part of a separate component from the driver, so disabling automatic updates for the NVidia driver will probably not fix this, but I'll try this anyway before the next Insider build upgrade.

    In any case, I also reported this to NVidia a few months ago, and NVidia seems to ignore it.


    The internet is full of complaints about this file being missing or corrupted.

    Also, I tried to see if the SFC issue persists in the latest build, but SFC seems to be broken in build 14279:

    C:\WINDOWS\system32>sfc /scannow

    Windows Resource Protection could not start the repair service.

    • Edited by Vlad NC Monday, March 7, 2016 12:59 PM
    Monday, March 7, 2016 12:58 PM