New
#170
yes i did that and all is well now it says it fixed something hope that fixes it :)
yes i did that and all is well now it says it fixed something hope that fixes it :)
Hi,
Just updated nVidia driver to release 361.75 & am still getting the hash mismatch for opencl.dll. DISM tells me the store is repairable, so guess I really do have some corruption. RestoreHealth operation failed for version: 10.0.10586.0 = Either the repair source was not found or the component store cannot be repaired.
Sorry if this is a silly question:
So I do not have C:\$Windows.~BT but do have C:\ESD\Windows\sources\install.esd. Is there any reason I cannot use this? If not will proceed with the TechBench Windows ISO.
thanks
If your only problem is Opencl.dll than you are all set, as this is a problem between Windows 10 and Nvidia.....more on the MS side thou. Anyone who has a Nvidia card from like the 700 series and up has this problem. SFC /Scannow will repair it by deleting one of them and replacing 2 others with MS ones......their is no real solution until MS decides to address this issue.
Hi OldMike65,
I do have a GTX 760.
At first figured there was no problem since the hash mismatch is exactly as posted on page 1 of SFC command tutorial, but after running the DISM CheckHealth command & getting The component store is repairable I was afraid there may actually be some corruption.
I am building a new PC (my first) & will be moving the GTX 760 to the new build & reinstalling the old AMD GPU in the current desktop in a couple weeks. Guess I can wait to see what happens after with another sfc /scannow.
Are you saying the DISM commands will come back as Healthy after removing the nVidia card/drivers?
thanks
Guess I think do have another problem. Yesterday ran sfc/ scannow three times with restart in between each per Brink's suggestion but each time I get: (& note it indicates Repairs Complete?)
Since it does not appear to be causing a problem guess I'll wait until old AMD card is in & check all again. Would still like to know if the above referenced file C:\ESD\Windows\sources\install.esd can be used to run the DISM / restorehealth / source:esd command.Code:2016-02-06 17:10:42, Info CSI 000050dc [SR] Beginning Verify and Repair transaction2016-02-06 17:10:44, Info CSI 0000512c [SR] Verify complete 2016-02-06 17:10:44, Info CSI 0000512d [SR] Repairing 1 components 2016-02-06 17:10:44, Info CSI 0000512e [SR] Beginning Verify and Repair transaction 2016-02-06 17:10:44, Info CSI 00005130 [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-02-06 17:10:44, Info CSI 00005133 [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-02-06 17:10:44, Info CSI 00005134 [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-02-06 17:10:44, Info CSI 00005137 [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-02-06 17:10:44, Info CSI 00005139 [SR] Repair complete 2016-02-06 17:10:44, Info CSI 0000513a [SR] Committing transaction 2016-02-06 17:10:44, Info CSI 0000513f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
thanks OldMike