system is working fine, i'm a bit scared to start tinkering and to try to fix this if I don't have to ,

thx

as follows:

2016-07-05 10:11:44, Info                  CSI    00005ed2@2016/7/5:20:11:44.661 Primitive installers committed for repair2016-07-05 10:11:44, Info                  CSI    00005ed3 [SR] Verify complete2016-07-05 10:11:44, Info                  CSI    00005ed4 [SR] Repairing 1 components2016-07-05 10:11:44, Info                  CSI    00005ed5 [SR] Beginning Verify and Repair transaction2016-07-05 10:11:44, Info                  CSI    00005ed6 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}2016-07-05 10:11:44, Info                  CSI    00005ed7 [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 mismatch2016-07-05 10:11:44, Info                  CSI    00005ed8@2016/7/5:20:11:44.676 Primitive installers committed for repair2016-07-05 10:11:44, Info                  CSI    00005ed9 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}2016-07-05 10:11:44, Info                  CSI    00005eda [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 mismatch2016-07-05 10:11:44, Info                  CSI    00005edb [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-07-05 10:11:44, Info                  CSI    00005edc Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}2016-07-05 10:11:44, Info                  CSI    00005edd 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 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}2016-07-05 10:11:44, Info                  CSI    00005ede [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted2016-07-05 10:11:44, Info                  CSI    00005edf@2016/7/5:20:11:44.700

Do you have a Windows Repair disk? If so run that. It looks like a DLL file is missing and the repair disk will fix that

If you don't have a repair disk missing DDL files can be downloaded using a software called DDL-file Fixer. It isn't a freeware but it is good and worth the price. At USD 29.95 it isn't expensive.

https://www.dll-files.com/

you do realize windows 10 is basically Malware right?

http://www.extremetech.com/extreme/229040-microsofts-latest-trick-clicking-x-to-dismiss-windows-10-upgrade-doesnt-stop-upgrade-process

Last week, ZDNet hailed these changes as a positive step for Microsoft, since there’s now a “Click Here” link to cancel the upgrade as opposed to no clear method of doing so. The problem is, Microsoft just changed one of the core behaviors of the GWX.exe application without telling anyone it did so. PC World’s Brad Chacos wrote about how his wife was caught up in the upgrade, and reports have been coming in from Reddit as well.

Literal standards vs. perceived dishonesty

Microsoft would undoubtedly argue that this change isn’t actually a change at all. There are many, many modern applications that don’t automatically exit when you click the “X” button — and Microsoft’s formal guidelines as far back as Windows 95 instructed developers that they should treat the X as a “Close” button, not an “Exit” button. The problem is, X generally is interpreted as exit, and there are plenty of Microsoft applications, including Office, Internet Explorer, and Edge, that still follow this behavior.

In other words: Microsoft has technically done nothing wrong with flip-flopping on treating the X as a “Close this dialog” option as opposed to a “Cancel this process” option. It can even argue that it’s now operating according to its own best practices, especially since GWX.exe runs in the background anyway unless you kill it via GWX Control Panel or Task Manager (and it restarts itself if all you use is Task Manager, so not much luck there.)

I am good with W10,,,,,Using W7,,,,,, No probs

Why are you running SFC ? if no problems .If it aint broke, dont fix it.

Answer is right here.

http://answers.microsoft.com/en-us/windows/forum/windows_10-update/the-system-file-checker-sfcexe-may-incorrectly/7a85d1f3-8573-4687-8980-507cd4dadd8b?tm=1458857817995

This issue may occur in Windows 10 Version 1511. When you install Windows, it installs a version of opencl.dll. However hardware drivers may also install their own version of opencl.dll, and if the driver version is different than the one installed by Windows, SFC may report this as file corruption and may not replace the file.

When this happens, the opencl.dll file is not actually corrupt. It is not necessary that you take any action – the report that opencl.dll is corrupt can be safely ignored.

Windows Repair Disk will do absolutely nothing other than waste about 2 hours of your life, it is useless, it simply does not work and repairs nothing. He needs to find the repair for SFC using the live / online repair, the bundled repair that comes with your local installation is about as much use as the repair disk...useless!

you do realize windows 10 is basically Malware right?

http://www.extremetech.com/extreme/229040-microsofts-latest-trick-clicking-x-to-dismiss-windows-10-upgrade-doesnt-stop-upgrade-process

Last week, ZDNet hailed these changes as a positive step for Microsoft, since there’s now a “Click Here” link to cancel the upgrade as opposed to no clear method of doing so. The problem is, Microsoft just changed one of the core behaviors of the GWX.exe application without telling anyone it did so. PC World’s Brad Chacos wrote about how his wife was caught up in the upgrade, and reports have been coming in from Reddit as well.

Literal standards vs. perceived dishonesty

Microsoft would undoubtedly argue that this change isn’t actually a change at all. There are many, many modern applications that don’t automatically exit when you click the “X” button — and Microsoft’s formal guidelines as far back as Windows 95 instructed developers that they should treat the X as a “Close” button, not an “Exit” button. The problem is, X generally is interpreted as exit, and there are plenty of Microsoft applications, including Office, Internet Explorer, and Edge, that still follow this behavior.

In other words: Microsoft has technically done nothing wrong with flip-flopping on treating the X as a “Close this dialog” option as opposed to a “Cancel this process” option. It can even argue that it’s now operating according to its own best practices, especially since GWX.exe runs in the background anyway unless you kill it via GWX Control Panel or Task Manager (and it restarts itself if all you use is Task Manager, so not much luck there.)

Malware is software that infects your internet browser. Chrome, edge etc. Unwanted toolbars, changes your default search engine, browser redirects/popups and in extreme cases adds a proxy server to your browser. I am not understanding your statement that "windows 10 is malware".

Windows Repair Disk will do absolutely nothing other than waste about 2 hours of your life, it is useless, it simply does not work and repairs nothing. He needs to find the repair for SFC using the live / online repair, the bundled repair that comes with your local installation is about as much use as the repair disk...useless!

There is nothing to repair, as my post above says.

"the opencl.dll file is not actually corrupt. It is not necessary that you take any action – the report that opencl.dll is corrupt can be safely ignored."

So far...have refused to upgrade from Windows 8.1 to Window 10...

Additionally, refusing MS updates...their update have established a history of causing unintended consequences when allowing Microsoft to just update my system each time a new version comes out...

System runs smoother for me without their built in crashes and errors following their updates...

thanks peter, i did do some searching, but bit over my head i guess

Late last year when I noticed a "sfc /scannow" command said I had some corrupt files although my Win 10 was running fine, I couldn't stand it and wanted to fix it.

I used the guidance at this website to fix the problem...the corrupt files were replaced/fixed....been fine since....sfc /scannow now reports no corrupt files. The Option 2, Step 6/7 worked for me....in my case I think it was specifically Step 6.

Beyond what the above website instructs, I Know Nothing, I Know Nothing, so don't ask.

Late last year when I noticed a "sfc /scannow" command said I had some corrupt files although my Win 10 was running fine, I couldn't stand it and wanted to fix it.

I used the guidance at this website to fix the problem...the corrupt files were replaced/fixed....been fine since....sfc /scannow now reports no corrupt files. The Option 2, Step 6/7 worked for me....in my case I think it was specifically Step 6.

Beyond what the above website instructs, I Know Nothing, I Know Nothing, so don't ask.

Most 3rd party hardware drivers will replace the generic windows DLL files with a third party DLL. A DLL file, Dynamic Link Library, contains specific information relevant to that piece of hardware. Windows SFC will sometimes see the replacement DLL file as corrupt, ie not the original windows file. Its not corrupt.

Windows knows about these replacement DLLs (a big list of compatible hardware) and SFC will usually not flag it. Sometimes a 3rd party will make a new DLL and not inform microsoft windows etc, microsoft forgets to add it to the list etc. (will probably get fixed in a future windows update).

Replacing the DLL file with original windows file will in most cases cause problems.

SFC, is not a general tune up/ maintenence tool. Its purpose is to replace a certain file, if you know its corrupt.

Stop using SFC as a maintenance/health check tool, its not.

If it aint broke, dont fix it.

If you don't have a repair disk missing DDL files can be downloaded using a software called DDL-file Fixer. It isn't a freeware but it is good and worth the price. At USD 29.95 it isn't expensive.

https://www.dll-files.com/

If you're a good swimmer, you might find one at the bay.

I'm with Peterw42. Leave it alone if nothing is broken.

I'm with Peterw42. Leave it alone if nothing is broken.

Maybe some "little experiments" where you finally help the OP to get back to normal?

Create a restore point. Then Google how to scan for errors with DISM. Should keep you busy for a while:)