SFC some corrupt files can not be fixed

Page 15 of 21 FirstFirst ... 51314151617 ... LastLast

  1. Posts : 54
    Windows 10
       #141

    I can't reproduce this success story.
    1) I have 27kb opencl.dll in WinSxS and 103kb opencl.dll in SysWoW64
    2) I run sfc /scannow and got
    "Windows Resource Protection found corrupt files and successfully repaired them."
    3) Now have 27kb opencl.dll in both directories (as hardlink).
      My Computer


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

    Ache said:
    I can't reproduce this success story.
    1) I have 27kb opencl.dll in WinSxS and 103kb opencl.dll in SysWoW64
    2) I run sfc /scannow and got
    "Windows Resource Protection found corrupt files and successfully repaired them."
    3) Now have 27kb opencl.dll in both directories (as hardlink).
    Yup, that IS the SAME problem we both have.....exactly.....
      My Computers


  3. Posts : 1
    Win 10 Pro 64
       #143

    Ratbone said:
    SFC is not able to fix it I still got the same error.

    took a copy of \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll


    Attachment 50009



    took ownership of the containing folder \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\

    took a copy of the new opencl.dll and renamed it to opencl_New_NVidia.dll

    Attachment 50011

    Prompt path How do I find these two files
      My Computer


  4. Posts : 23
    Windows 10 Professional
       #144

    right let's clarify what my issue was.

    I was having a problem with the opencl.dll in
    C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

    Microsoft was not happy with the NVidia (103 KB) version and wanted to replace it with the Microsoft version (27 KB) but failed.

    running both

    SFC /scannow

    and

    DISM.exe /Online /Cleanup-image /Restorehealth /Source:wim:K:\sources\install.wim:1 /limitaccess

    did not fix the corruption
    the version in SysWOW64 was never my issue because DISM health check did not take issue with the NVidia (103 KB) version and did NOT report any corruption. That was fine by me.

    BUT if you ignore DISM not finding any corruption and do run SFC /scannow anyway, the file in SysWOW64 will be replaced.

    I tend not to use SFC (I only use it as the "last chance saloon" for file corruption prior to re-imaging my OS). From my experience if DISM fails to fix corrupted files then SFC will also fail.

    So as long as DISM health Check does not report corruption I am happy to stop there and leave things alone.

    Now regarding the Opencl.dll in SysWOW64 and WinSxS I suspect (but I stand to be corrected) NVidia driver does not even use them and quite possibly might call them from C:\Program Files\NVIDIA Corporation\OpenCL.

    If you use a program like process hacker or System Information\Loaded modules, it appears the Opencl.dll in SysWOW64 (or anywhere else) is not actively used.

      My Computer


  5. Posts : 54
    Windows 10
       #145

    You need 32bit application or game which directly use OpenCL API to see this dll loaded. The driver itself does not need it.
    This demo for example: Scenic by UnRAVeL :: pouët.net
      My Computer


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

    Ratbone said:
    right let's clarify what my issue was.
    BUT if you ignore DISM not finding any corruption and do run SFC /scannow anyway, the file in SysWOW64 will be replaced.
    Well what I found out that Opencl.dll is not just replaced from this folder, but it IS REMOVED. After you run SFC this file is removed from the SysWow64 folder.
      My Computers


  7. Posts : 23
    Windows 10 Professional
       #147

    Ache said:
    You need 32bit application or game which directly use OpenCL API to see this dll loaded. The driver itself does not need it.
    This demo for example: Scenic by UnRAVeL :: pouët.net
    OK I 'll give it a try and see

    did you try running the demo with both versions? any difference?
      My Computer


  8. Posts : 54
    Windows 10
       #148

    This is scene demo, designed to work on bare minimum of OpenCL API, so MS one works too.
      My Computer


  9. Posts : 23
    Windows 10 Professional
       #149

    Ache said:
    This is scene demo, designed to work on bare minimum of OpenCL API, so MS one works too.
    yep it's being used

    SFC some corrupt files can not be fixed-nvopencl.pngSFC some corrupt files can not be fixed-process-hacker.png

    So If you want to run the Nvidia version just replace it with the 103 KB version and do not run SFC.

    I suspect there will be a lag before Microsoft - NVidia agree on a version to be defaulted on the OS don't forget the Windows Update of the Nvidia driver is always older than the Nvidia current WHQL release.
      My Computer


  10. Posts : 5
    win 10 pro x64
       #150

    I've read the entire thread, i also have win 10 build 10586, and in sfcdetails i have this line:
    Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-25 07:48:37, Info CSI 00003c6b [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-25 07:48:37, Info CSI 00003c6c [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
    2015-11-25 07:48:37, Info CSI 00003c6f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted


    I have the gtx 970 with 359.00 driver and i've reinstaled this windows 3 times. The opencl.dll file has 103 kb.
    Is this normal or do i have a hardware problem?
      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 05:05.
Find Us




Windows 10 Forums