New
#41
It is waste of efforts to restore opencl.dll since NVIDIA driver overwrites it on the next install again and error returns back.
For some reason after running cmd 3, DISM cannot locate the source. I did everything as specified too
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).