Hell NO I posted that after THIS upgrade from Nvidia I have not run sfc.....noway.....I am scared it will mess up my graphics again!! Also in my 2nd pic....look at the SYSWOW64 dir......then look at pic #1 No Opencl.dll file before this latest upgrade, NOW its in that dir too!!! Also have noticed even my facebook screens look sharper, colors look better, even the text looks better, now it could be just me.....but graphics seem to be sharper now than before. :)
I had those issues before th2 upgrade......like I said they were minor issues, but they were their before th2 and after. Now graphics ARE BETTER......but I have not run sfc.........last time I ran sfc was 2 days ago, and it found errors (opencl.dll) fixed them, and and removed my Nvidia drivers and replaced them with MS drivers. So I left them alone, till today. Now I don't want to run SFC.
Hello
I have run SFC /SCANNOW right after installing today's NVIDIA driver. That file you have referred to has the size of 27 KB (or something) after SFC "fixed" my system... Then I have clean-installed the latest NVIDIA driver again and now that file has the size of 103 KB.
I have done this in both of my Windows 10 Pro installations. My main OS and my Insider build. Both are 10586.11
Thank you for clarifying what is going on with this topic. I have already reported this on Windows Feedback.
Well I could have RIGHT AFTER the TH2 upgrade....and most likey found no errors SIR......but I re-installed the Nvidia drivers AFTER the TH2 upgrade.....then.....few more days later, I re-ran sfc, and then it found errors, repaired them, I rebooted, ran sfc again, no errors this time, and it was then I found out about this opencl.dll problem. Also before I even had done the TH2 upgrade I was having those minor display issues too, so that must have been related to this NEW update today, because NOW my displays and text look better. Ok??
Seems installing or reinstalling your NVIDIA drivers and never run sfc and dism will solve this issue. Question will be how will we ever know this to be resolved in windows.
Just wondered how we will know when this will be fixed as seems to be a MS issue. I installed the new driver now and did not run anything, leave it be. Reasons i needed to do what i did from the beginning in this thread was because sfc would not repair files and DISM source could not be found, that is corrected now. Even though reasons to fix were due to this issue now with openCL.dll i still had an issue with SFC and DISM to begin with, which is corrected.
Quote
