-
12-14-2015, 01:10 PM #1Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
[Win10 Upd1511 TH2] GUIDE: opencl.dll corruption in SFC/DISM
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
Read More:
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.Code:2015-12-13 04:11:37, Info CSI 00004a0c 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 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 corrupted
How to perform a DISM scan
Read More:
Now, if you can confirm that your opencl.dll file is indeed corrupt, you can follow the instructions below to perform the fix.Code:(p) CSI Payload Corrupt wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll Repair failed: Missing replacement payload.
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.
- 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);
SFCFix.zip
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.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 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. 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-----------------------
Last edited by Aura; 07-11-2016 at 08:50 AM.

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
Ad Bot
- Beep.
-
12-14-2015, 04:41 PM #2Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: Guide: How to repair opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (T
How does it looks? Anything I should add/remove/modify?

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
12-15-2015, 03:30 AM #3Administrator
Windows Update Expert
Contributor
- Join Date
- Mar 2012
- Location
- Adelaide, South Australia
- Posts
- 5,853
Re: Guide: How to repair opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (T
Looks good Aura :)
-
12-15-2015, 08:43 AM #4Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: Guide: How to repair opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (T
Good :) In that case am I free to sticky it in the Windows Update section? Didn't you went to create a "Tutorial/Guide" subsection inside Windows Update for these threads, since we're beginning to have too many stickies?

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
12-18-2015, 02:15 PM #5
Re: Guide: How to repair opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (T
Might want to use zcomputerwiz instead of my actual name
I am usually online 1PM - 4PM CST Monday - Friday.
If your thread has not received a new reply within 3 days, please make a post here: Not Received Help? so another helper can continue to assist you.
-
12-18-2015, 03:19 PM #6Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Edited :P Thanks!

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
12-19-2015, 04:32 PM #7Moderator
- Join Date
- Dec 2013
- Location
- World, Europe, Italy
- Posts
- 1,457
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Hi Aura (and all).

After the two introduction paragraphs, I'd modify the guide/tutorial in this way:
1) Run the SFC tool (leave the command prompt open till it finishes).
How to perform the scan.
If it will show/report/say/write that it didn't find integrity violations, it's ok and you shouldn't continue to read.
If it will show/report/say/write integrity violations, here's the lines you'll find in [...].
2) Perform a dism restore (leave the command prompt open till it finishes).
How to perform a dism restore.
If it will show/report/say/write that it completed successfully, re-try the sfc tool to ensure it says there are no integrity violations; if this is the case, you can finish to read at this point.
If it will show/report/say/write that the component store is (still) corrupted, then:
3) SFCFix - Fix Time
Hope you like it!
-
12-20-2015, 10:36 AM #8Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
I don't think it's necessary to do that. Mostly because your version includes the fact that the first SFC scan might comeback clean. This guide is for users who are aware that they have opencl.dll corruption already (so this most likely how/why they'll have found this thread in the first place), so it's safe to assume that their first SFC scan won't comeback as clean :)

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
12-22-2015, 06:38 PM #9Moderator
- Join Date
- Dec 2013
- Location
- World, Europe, Italy
- Posts
- 1,457
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Hence:
[introduction]
After you have ran the sfc tool, you'll find these lines: [...]
1) Perform a dism restore (leave the command prompt open till it finishes).
How to perform a dism restore.
If it will show/report/say/write that it completed successfully, re-try the sfc tool to ensure it says there are no integrity violations; if this is the case, you can finish to read at this point.
If it will show/report/say/write that the component store is (still) corrupted, then:
2) SFCFix - Fix Time
:)
-
12-23-2015, 12:48 PM #10Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
I'm already addressing this.
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 (which implies that SFC returned another message than the two ones I listed), 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.
Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
12-23-2015, 02:48 PM #11Moderator
- Join Date
- Dec 2013
- Location
- World, Europe, Italy
- Posts
- 1,457
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Ok.
-
01-19-2016, 12:45 PM #12Registered Member
- Join Date
- Jan 2016
- Posts
- 27
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Does anyone know what the actual difference between the two opencl.dll files are? Which one is better? If either one doesn't change the way Windows operates does nVidia know what they're doing with their drivers more than Windows? Or are these files with the same code in them but simply have a different hash that doesn't match Windows? Or does Windows know what they're doing with their operating system more than nVidia?
-
01-19-2016, 01:06 PM #13Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
Two identical files cannot have different hash :) One opencl.dll file is from NVIDIA, and the other is from Microsoft. To be honest, it doesn't really matter unless you use OpenCL programs (not a lot of users do however) and even there, I'm sure you wouldn't even notice the difference.

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
01-19-2016, 07:44 PM #14Registered Member
- Join Date
- Jan 2016
- Posts
- 27
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
cool; I had tried to move an opencl.dll file I thought was known to be good manually into where I thought it should go at one time too to no avail, so I appreciate you're doing the hard work of knowing where the file should go and the permissions on the file.
-
01-26-2016, 08:55 AM #15Registered Member
- Join Date
- Jan 2016
- Posts
- 1
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
I joined to say thank you for the assistance you provided. If it happens again, I know what to do. :)
-
01-26-2016, 10:13 AM #16Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
I spotted your thread on BleepingComputer :)
No problem redazure, you're welcome!
Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
01-27-2016, 11:59 PM #17Registered Member
- Join Date
- Jan 2016
- Posts
- 27
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
the program is going into an endless loop that goes: checking for updates .... downloading then closes, then opens and starts again
-
01-28-2016, 02:14 AM #18Registered Member
- Join Date
- Jan 2016
- Posts
- 2
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
this worked for me a few days ago, now updated my nvidia drivers and I get the same opencl.dll issue... tried running the fix but I get the same result as calebtree... endless loop of update found, downloading update... I re-downloaded both the zip and exe just now and still the same thing...
-
01-28-2016, 07:28 AM #19Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
There's currently an issue with SFCFix.exe (as a new version just got released). The developer is aware of it and is already working on a fix :) I can let you know when it gets fixed.

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
-
01-28-2016, 09:49 AM #20Moderator
Windows Update Senior Analyst
Security Analyst
- Join Date
- Mar 2015
- Location
- Québec, Canada
- Age
- 23
- Posts
- 8,009
Re: GUIDE: opencl.dll corruption in SFC/DISM, Windows 10 Update 1511 (TH2)
I've just been that the issue should have been solved by now, is it possible for both of you to try SFCFix again and see if it works properly? I suggest you to re-download it before so you get the latest version.

Windows Update Senior Analyst | BleepingComputer Malware Response Team
If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.
Similar Threads
-
[SOLVED] Corrupt opencl.dll file. Not fixed by Aura's guide
By brak512 in forum Windows UpdateReplies: 1Last Post: 07-14-2016, 08:58 PM -
opencl.dll corruption and more
By staidk in forum Windows UpdateReplies: 2Last Post: 12-26-2015, 12:56 PM -
[SOLVED] SFC & DISM fails to repair corruption WIN10
By Kersh86 in forum Windows UpdateReplies: 5Last Post: 10-10-2015, 11:24 AM
System Specs
System File Checker (SFC)
Reply With Quote