New
#11
Many thanks for your help. I will let you know :)
Many thanks for your help. I will let you know :)
Sorry to butt in here lx07, but he has chatted with me earlier about his graphic's card problem, and what he was telling me are the same errors with Opencl.dll file, that is happening with the newer Nvidia cards. This problem is a MS problem, and not a Nvidia problem. These two companies have to get together to solve this issue. Weather they will, or how long this might take is anybody's guess. I am surprised that this same problem affected this users AMD card thou.
Looking at latest log from SFC, it did mention AMD files so maybe AMD/Nvidia supply same files?
That I would not know, as I don't know very much about AMD cards, I've only bought and use Nvidia cards. But even in my CBS log files it never mentions Nvidia, it reports on the drivers, in this case Opencl.dll files, which Windows 10 will replace one of them and delete another one. Everytime.
Ok so i have got the ISO downloaded now and mounted it. Please can you someone confirm the command?
EDIT: Believe i've found it but its still saying Source files not found
I think i've done it. Going to reboot now and do a SFC scan just to ensure :)
All sorted! Many thanks for your help/advise guys.
Technical details:
The correct fix will be to remove wrongly installed and activated by Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 directory (Microsoft RemoteFX Display driver, 32bit part, which contains opencl.dll with reduced functionality, which overwrites correct Nvidia/ATI/Intel \SysWoW64\opencl.dll on upgrade or attempt of DISM recover from install.wim) from WinSxS (64bit counterpart is in amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586 .0_none_5fcf2a87752df0d7 directory, but is inactive and does no harm). But I know no tool for correct selective remove or deactivate of specific directory from WinSxS. Since \SysWoW64\opencl.dll is hardlink to WinSxS one, attempt to install Nvidia/ATI/Intel driver corrupts two Microsoft opencl.dlls at once (so sfc /scannow fails to recover), and attempt to recover WinSxS one from install.wim via DISM damages Nvidia/ATI/Intel display driver's opencl.dll from other hand.