SFC /SCANNOW report opencl.dll bad

Hello,

Been running the latest 10525 build and I believe since then I have SFC reporting a bad file in the SYSWOW64 folder: opencl.dll.

This file is associated with my GPU drives, however no kind of reinstallation or cleanup will get rid of the SFC error.

I'm not overly concerned by this, as 1) I'm running a test-build and 2) no problems in the OS or games.

However I do prefer a system without errors, so I thought to report this. Also what I find funny is the name RemoteFX-clientVM... what does that have to do with my GTX980??

This is detailed info:

015-08-25 07:52:16, Info                  CSI    00003bf5 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10525.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-08-25 07:52:17, Info                  CSI    00003c2a [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10525.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-08-25 07:52:17, Info                  CSI    00003c2b [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10525.0.RemoteFX clientVM and UMTS files and regkeys"
2015-08-25 07:52:17, Info                  CSI    00003c2e [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted

So, is this a build 10525 error or is it something else? I would appreciate a little detail.

Thank you.

 

Question Info


Last updated May 10, 2019 Views 20,853 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi,

Thank you for using Windows 10.

The missing DLL is typically associated with gaming drivers, however as the information says about Remote access.

Let us know are you using a virtual machine. If yes, then I would suggest you to post your question in the Technet Forum, where we have support professionals who are well equipped with the knowledge on such issues. I suggest you to refer to the following link to reach out to them and post your query there: 

https://social.technet.microsoft.com/Forums/en-US/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc

Regards,

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Anand,

I am aware that the DLL comes with the GPU driver. In fact, I confirmed that when I uninstalled the Nvidia driver the DLL was deleted from the SysWOW64 folder. However, I didn't do the SFC test without it.

But to answer your question about VM: no, I am not using any kind of VM. I used to have VMWare installed a week ago, but right now it's not installed any more. I ran the SFC without VMWare installed of course.

I do however wonder what do gaming driver and remote access have in common??

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Kosta2,

I'm facing the same although my envrionment differs from yours:

I didn't check in Build 10525 but checked in 10532: Same issue here. Build is installed in a separate partition.

And my GPU is a little bit older and very small compared to yours: It's a GTX770M.

@Anand:

Productive environment is 10240: No problems there although the drivers used for Intel HD 4600 and Nvidia GTX770M are exactly the same.

I'm looking forward for a solution although I know that an Insider Preview might not be error free.

Kind regards

Wolfgang

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Interesting, I too am having this issue, and the common denominator seems to be video drivers and this particular build.. and like you, I have gone up and down the upgrade/downgrade path to get this issue addressed, and in my case, it's having real world impact... the only difference in our experiences so far seems to be that on both of my machines, I am running a fairly straightforward Intel integrated graphics adapter, not any nVIDIA hardware.

For the record, I have two systems exhibiting this behavior, one is running Windows 10 Enterprise Build 10532 and is a machine I often RDP into, and lately had been noticing some performance issues.  The other system is running Windows 10 Pro Build 10532 and lately has been exhibiting network errata in general.

The particular files I am getting SFC validation failures on are as follows:

 2015-09-11 22:25:02, Info                  CSI    00003c1a [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-11 22:25:04, Info                  CSI    00003c83 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-11 22:26:49, Info                  CSI    00004e5a [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-11 22:26:49, Info                  CSI    00004e5d [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10532.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Anyone have any ideas, it appears to be a permissions issue...

Thanks!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Having the same issue, build 10547:

2015-10-03 13:34:45, Info                  CSI    00003e87 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e88 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:34:45, Info                  CSI    00003e89 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10547.0.RemoteFX clientVM and UMTS files and regkeys"
2015-10-03 13:34:45, Info                  CSI    00003e8a Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e8b Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e8c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted

....

2015-10-03 13:36:20, Info                  CSI    00005011 [SR] Verify complete
2015-10-03 13:36:20, Info                  CSI    00005012 [SR] Repairing 1 components
2015-10-03 13:36:20, Info                  CSI    00005013 [SR] Beginning Verify and Repair transaction
2015-10-03 13:36:20, Info                  CSI    00005014 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    00005015 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:36:20, Info                  CSI    00005016@2015/10/3:10:36:20.123 Primitive installers committed for repair
2015-10-03 13:36:20, Info                  CSI    00005017 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    00005018 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:36:20, Info                  CSI    00005019 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10547.0.RemoteFX clientVM and UMTS files and regkeys"
2015-10-03 13:36:20, Info                  CSI    0000501a Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    0000501b Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    0000501c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-10-03 13:36:20, Info                  CSI    0000501d@2015/10/3:10:36:20.149 Primitive installers committed for repair
2015-10-03 13:36:20, Info                  CSI    0000501e [SR] Repair complete
2015-10-03 13:36:20, Info                  CSI    0000501f [SR] Committing transaction

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Having the same issue, build 10547:

2015-10-03 13:34:45, Info                  CSI    00003e87 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e88 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:34:45, Info                  CSI    00003e89 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10547.0.RemoteFX clientVM and UMTS files and regkeys"
2015-10-03 13:34:45, Info                  CSI    00003e8a Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e8b Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:34:45, Info                  CSI    00003e8c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted

....

2015-10-03 13:36:20, Info                  CSI    00005011 [SR] Verify complete
2015-10-03 13:36:20, Info                  CSI    00005012 [SR] Repairing 1 components
2015-10-03 13:36:20, Info                  CSI    00005013 [SR] Beginning Verify and Repair transaction
2015-10-03 13:36:20, Info                  CSI    00005014 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    00005015 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:36:20, Info                  CSI    00005016@2015/10/3:10:36:20.123 Primitive installers committed for repair
2015-10-03 13:36:20, Info                  CSI    00005017 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    00005018 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10547.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-10-03 13:36:20, Info                  CSI    00005019 [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10547.0.RemoteFX clientVM and UMTS files and regkeys"
2015-10-03 13:36:20, Info                  CSI    0000501a Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    0000501b Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10547.0_none_3dda4545566fc5b5\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
  Found: {l:32 b:/Q8Wvg60D6q+rZT/A6Nwr1+ugP9PG3OiXosFlIIxVJc=} Expected: {l:32 b:snLvZ4/kUEcuORaJlH6v/8zmd4nfMlrIotUCFm9uMkY=}
2015-10-03 13:36:20, Info                  CSI    0000501c [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2015-10-03 13:36:20, Info                  CSI    0000501d@2015/10/3:10:36:20.149 Primitive installers committed for repair
2015-10-03 13:36:20, Info                  CSI    0000501e [SR] Repair complete
2015-10-03 13:36:20, Info                  CSI    0000501f [SR] Committing transaction

Exact same problem with build 10586.  I am running both Intel integrated HD Graphics 4600 and NVIDIA GeForce GT 750 M in my laptop.  Which graphics driver is responsible for opencl.dll being corrupt?

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

In the end I reinstalled windows <sigh>

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

That won't help, holmes...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I'm in the same boat. Tried couple of solutions already. None of the work... like ever.

Currently I'm on my 3rd repair of this Windows10 installation. Doesn't matter really... but is annoying that Microsoft can't bring out a CLEAN OS without any bugs, in the initial state.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

The correct fix will be to remove wrongly installed and activated by Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 directory (Microsoft RemoteFX Display driver, 32bit part, which contains opencl.dll with reduced functionality, which overwrites correct Nvidia/ATI/Intel \SysWoW64\opencl.dll on upgrade or attempt of DISM recover from install.wim) from WinSxS (64bit counterpart is in amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586 .0_none_5fcf2a87752df0d7 directory, but is inactive and does no harm). But I know no tool for correct selective remove or deactivate of specific directory from WinSxS. Since \SysWoW64\opencl.dll is hardlink to WinSxS one, attempt to install Nvidia/ATI/Intel driver corrupts two Microsoft opencl.dlls at once (so sfc /scannow fails to recover), and attempt to recover WinSxS one from install.wim damages Nvidia/ATI/Intel display driver's opencl.dll from other hand.

10 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.