odmvazquez
Member
- Dec 19, 2017
- 6
[10v1511b10586 x64] SFC /scannow - Cannot repair member file [l:10]"opencl.dll"
Greetings,
I'm getting this error and also I have some BSOD screens related to the display driver that probably are related [tried using DDU and installing the drivers once again without success]:
2017-12-20 05:41:43, Info CSI 00004cc1 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 Db26iUb5LZP0PSQ0h0uSOa6V13RPjduYy4S7YFkhOtU=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc2 [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
2017-12-20 05:41:43, Info CSI 00004cc3 [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"
2017-12-20 05:41:43, Info CSI 00004cc4 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 LNzReokuT7zHGFpMbn79U5UjJu0LKx6RLdcTg9zbT0Q=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc5 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 Db26iUb5LZP0PSQ0h0uSOa6V13RPjduYy4S7YFkhOtU=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc6 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
Any help would be much appreciated.
Thank you
PS. The file is bigger than the allowed size so I used WeTransfer instead, don't know if this would be a problem.
WeTransfer
Greetings,
I'm getting this error and also I have some BSOD screens related to the display driver that probably are related [tried using DDU and installing the drivers once again without success]:
2017-12-20 05:41:43, Info CSI 00004cc1 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 Db26iUb5LZP0PSQ0h0uSOa6V13RPjduYy4S7YFkhOtU=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc2 [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
2017-12-20 05:41:43, Info CSI 00004cc3 [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"
2017-12-20 05:41:43, Info CSI 00004cc4 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 LNzReokuT7zHGFpMbn79U5UjJu0LKx6RLdcTg9zbT0Q=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc5 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 Db26iUb5LZP0PSQ0h0uSOa6V13RPjduYy4S7YFkhOtU=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2017-12-20 05:41:43, Info CSI 00004cc6 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
Any help would be much appreciated.
Thank you
PS. The file is bigger than the allowed size so I used WeTransfer instead, don't know if this would be a problem.
WeTransfer