- Mar 16, 2015
- 8,061
Hi everyone :)
Recently, we noticed an increase in threads in the Windows Update section, related to a corrupt Windows system file after the upgrade from Windows 10 RTM to Windows 10 Update 1511 (also known as Treshold 2, or the "November Update"). The corrupt file is opencl.dll and is caused by the NVIDIA driver installer that overwrites the opencl.dll from Windows with it's own. So everytime you install the NVIDIA drivers (new install or update) for your graphic card (via the NVIDIA GeForce or Windows Update), the opencl.dll file will become corrupt. Luckily, this corruption doesn't affect the system nor your graphic features in any way (thanks to zcomputerwiz for testing and validating this claim, and also for the explanation).
This guide will help you determine if your opencl.dll file is indeed corrupt, and if so, how to replace it. Follow the instruction below carefully, and make sure that all the lines matches the ones in your logs before proceeding to the replacement, otherwise you could end up damaging your system.
Here's the lines you'll find in a CBS.log after running SFC if your opencl.dll file is corrupt and cannot be repaired.. There's two important parts in the lines below: the folder where opencl.dll is located, and the expected hash for it.
How to perform a SFC scan
Here's the lines you'll find in a DISM.log and/or CBS.log after running DISM if your opencl.dll file is corrupt and cannot be repaired. The important part here is the folder in which the opencl.dll file is located, and it's name.
How to perform a DISM scan
Now, if you can confirm that your opencl.dll file is indeed corrupt, you can follow the instructions below to perform the fix.
SFCFix - Fix Time
WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.
Follow the instructions below to download and execute a SFCFix fix, and provide the log.
This is how your SFCFix.txt log should look like after performing the fix.
Once done, you should run SFC again and it'll tell you that either no integrity violations were found, or that corrupt components were found but successfully repaired (if the fix worked). If after following the instructions in this guide, your opencl.dll file is still corrupt, please create a new thread in the Windows Update section, provide your CBS.log after a SFC scan, and a Windows Update Analyst will assist you shortly.
Recently, we noticed an increase in threads in the Windows Update section, related to a corrupt Windows system file after the upgrade from Windows 10 RTM to Windows 10 Update 1511 (also known as Treshold 2, or the "November Update"). The corrupt file is opencl.dll and is caused by the NVIDIA driver installer that overwrites the opencl.dll from Windows with it's own. So everytime you install the NVIDIA drivers (new install or update) for your graphic card (via the NVIDIA GeForce or Windows Update), the opencl.dll file will become corrupt. Luckily, this corruption doesn't affect the system nor your graphic features in any way (thanks to zcomputerwiz for testing and validating this claim, and also for the explanation).
This guide will help you determine if your opencl.dll file is indeed corrupt, and if so, how to replace it. Follow the instruction below carefully, and make sure that all the lines matches the ones in your logs before proceeding to the replacement, otherwise you could end up damaging your system.
Here's the lines you'll find in a CBS.log after running SFC if your opencl.dll file is corrupt and cannot be repaired.. There's two important parts in the lines below: the folder where opencl.dll is located, and the expected hash for it.
How to perform a SFC scan
Read More:
Code:
2015-12-13 04:11:37, Info CSI 00004a0c Hashes for file member \SystemRoot\WinSxS\[b][color=red]wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll[/color][/b] do not match actual file [l:10]"opencl.dll" :
Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} [b][color=red]Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}[/color][/b]
2015-12-13 04:11:37, Info CSI 00004a0d [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-12-13 04:11:37, Info CSI 00004a0e@2015/12/13:12:11:37.574 Primitive installers committed for repair
2015-12-13 04:11:37, Info CSI 00004a0f 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 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-13 04:11:37, Info CSI 00004a10 [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-12-13 04:11:37, Info CSI 00004a11 [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-12-13 04:11:37, Info CSI 00004a12 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-13 04:11:37, Info CSI 00004a13 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 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2015-12-13 04:11:37, Info CSI 00004a14 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corruptedHere's the lines you'll find in a DISM.log and/or CBS.log after running DISM if your opencl.dll file is corrupt and cannot be repaired. The important part here is the folder in which the opencl.dll file is located, and it's name.
How to perform a DISM scan
Read More:
Code:
(p) CSI Payload Corrupt [b][color=red]wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll[/color][/b]
Repair failed: Missing replacement payload.Now, if you can confirm that your opencl.dll file is indeed corrupt, you can follow the instructions below to perform the fix.
WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.
Follow the instructions below to download and execute a SFCFix fix, and provide the log.
- Download SFCFix and move the executable on your Desktop;
- Download the attached SFCFix.zip and move the archive to your Desktop;
Note: Make sure that the file is named SFCFix.zip, do not rename it. - Save any work you have open, and close every programs;
- Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
- SFCFix will launch, let it complete;
- Once done, a file will appear on your Desktop, called SFCFix.txt;
- Open the file, then check if the replacement worked (look at the example below);
This is how your SFCFix.txt log should look like after performing the fix.
Code:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-12-11 13:51:22.691
Microsoft Windows 8.1 - amd64
Using .zip script file at C:\Users\Aura\Desktop\SFCFix.zip [0]
PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
[b][color=blue]Successfully copied file C:\Users\Aura\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll to C:\Windows\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll.[/color][/b]
Successfully restored ownership for C:\Windows\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
Successfully restored permissions on C:\Windows\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-12-11 13:51:23.037
Script hash: SPhJgk57HkoTrdMLtWrtMfeOccJRwa6Z8fwFua8SZKg=
----------------------EOF-----------------------Once done, you should run SFC again and it'll tell you that either no integrity violations were found, or that corrupt components were found but successfully repaired (if the fix worked). If after following the instructions in this guide, your opencl.dll file is still corrupt, please create a new thread in the Windows Update section, provide your CBS.log after a SFC scan, and a Windows Update Analyst will assist you shortly.
Last edited:
Thanks!