Can't repair some files sfc scannow


  1. Posts : 4
    Windows 10
       #1

    Can't repair some files sfc scannow


    Hi everyone,

    I installed Windows 10 today and after setting up everything, tweaking etc. I decided to re-overclock my GPU except I forgot what I used to have my core clock at so I accidentally pushed it a bit further than it could handle. Needless to say it crashed during a game, just froze basically and I had to press the reboot button. Since I'm a bit paranoid I decided to run sfc /scannow just to check on things and this came u:

    Code:
    2016-01-29 03:30:23, Info                  CSI    00004eb3 [SR] Beginning Verify and Repair transaction
    2016-01-29 03:30:23, Info                  CSI    00004eb4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
      Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-29 03:30:23, Info                  CSI    00004eb5 [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
    2016-01-29 03:30:23, Info                  CSI    [email protected]/1/29:03:30:23.902 Primitive installers committed for repair
    2016-01-29 03:30:23, Info                  CSI    00004eb7 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
      Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-29 03:30:23, Info                  CSI    00004eb8 [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
    2016-01-29 03:30:23, Info                  CSI    00004eb9 [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"
    2016-01-29 03:30:23, Info                  CSI    00004eba Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
      Found: {l:32 jCmkCA0mNZb0snMaNo0DIhNAS+gDvbwn885A6iOX8Tk=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-29 03:30:23, Info                  CSI    00004ebb Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
      Found: {l:32 Ui1iPYLRlrK/KdPVb2btwB5JqasIeak0eCk42vnG8bQ=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-01-29 03:30:23, Info                  CSI    00004ebc [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2016-01-29 03:30:23, Info                  CSI    [email protected]/1/29:03:30:23.921 Primitive installers committed for repair
    2016-01-29 03:30:23, Info                  CSI    00004ebe [SR] Repair complete
    2016-01-29 03:30:23, Info                  CSI    00004ebf [SR] Committing transaction
    2016-01-29 03:30:23, Info                  CSI    00004ec0 Creating NT transaction (seq 2), objectname [6]"(null)"
    2016-01-29 03:30:23, Info                  CSI    00004ec1 Created NT transaction (seq 2) result 0x00000000, handle @0x5b4
    2016-01-29 03:30:23, Info                  CSI    [email protected]/1/29:03:30:23.927 Beginning NT transaction commit...
    2016-01-29 03:30:23, Info                  CSI    [email protected]/1/29:03:30:23.930 CSI perf trace:
    CSIPERF:TXCOMMIT;2907
    2016-01-29 03:30:23, Info                  CSI    00004ec4 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

    As you can see a few files couldn't be repaired, are they important? Should I do something about it? If so, how?

    Many thanks!
      My Computer


  2. Posts : 3,865
    Windows 3.1 to Windows 10
       #2

    opencl.dll

    is a known issue between Nvidia and MS

    you can fix it using Dism, but will come back with Nvidia driver

    so until it is addressed by MS - no worries,,
      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 06:02.
Find Us




Windows 10 Forums