Windows 10: SFC some corrupt files can not be fixed

there is a Restorehealth tool in my sig below

 

I don't think so. Restoring via DISM opencl.dll from Micrisoft is wrong move, since it is obsoleted.

This bug can be really fixed if some tool will be able to uninstall wrong C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22
which conflicts with NVidia's C:\Windows\SysWOW64\opencl.dll

 

Ache, how did you or did you update to new build 10586 ? You have same exact issue shown from CBS.log as i did if this is where you took your post now from.

 

1) Just by regular windows update.
2) Yes, and it is Microsoft opencl.dll vs. Nvidia opencl.dll bug, attempt to restore Microsoft one will give you obsoleted version and no CBS.log error, but attempt to install Nvidia driver restores Nvidia one, which will give you recent version and CBS.log error.

 

I knew what the issue was from, like you are stating now shown from the CBS.log when i had this fix that would not be fixed from SFC, because i researched it and saw exactly what you are stating now. You are telling me you updated to 10586 through update still get files can not be fixed in SFC and error in DISM source file can not be found.

Downloaded the ISO from TechBench and ran exactly what i did and same result ? I never tried to copy those OpenCL.dll into either folder path to resolve this issue, way shown worked fine and still is fine with newest NVIDIA Drivers for my card.

 

I don't try clean install (too many programs), just upgrade, so can't say what happens in clean case.
Prerequisite for this bug is DX11-capable card. My old notebook have DX10 and so there is no Remote FX driver installed and no this bug (conflicting opencl.dll).

 

So basically you tried this method i did after update from windows to 10586 with a mounted ISO from techbench and it did not help you ? Although this SFC & DISM happened to me after my clean install of TH2.

 

I restore Microsoft version of opencl.dll using install.wim as described at this forum already many times in many threads. Error is gone. Then I reinstall Nvidia driver, reboot and check what happens. Error returns.

 

Not from here you mean restoring opencl.dll ? I knew fault was that because i tried a second clean install at the time and the error was not there till the drivers installed from windows update, but then i removed them and installed latest, but errors prevailed.

If did not try this method i did yet or you said you did and it did not work

then try kyhi method

 

Post # 29 was one i did.

 

then try post #45, he has a link

 

All they do the same thing, which works, but temporarily, until the next Nvidia installer run.
Permanent fix will remove wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 but I can't find the way to do that anywhere.

 

Not going to say it is wrong or right. I fixed mine almost 5 days ago , i reran sfc just today and no integrity violations.

 

So what is the permanent fix ? Either could i at the time, except fix for DISM

 

1) The next step: install Nvidia driver, reboot and run SFC again (bad surprise).
2) Permanent fix will survive Nvidia driver install or upgrade.
3) Right now if SFC says no integrity violations it means you have obsoleted 32bit opencl.dll and not one from the Nvidia driver. I.e. no integrity violations is bad thing.