Windows 10: Microsoft Fixing opencl.dll issue in SFC /SCANNOW soon

Actually was not easy for me to say, since it took me many posts here and participating in many others on this for quite sometime to come to this assumption. From what i see here from your reputation you seem to be pretty knowledgeable.

 

I doubt it is a difficult fix *Rolleyes

 

I copy the file from another PC and it went away and haven't seen the error in months.

 

I have been dealing with it since November.

What i found out is that this issue does not exist on Windows 8.1 and below.

 

It is now 6 months since ms pushed bad update....finally acknowledged 'they' had a problem 2 months ago. Is it fixed with an update? I have 2 different devices upgraded from 8.1 pro to 10 pro with this issue. Spent days trying many different fixes(even ms tech support had NO idea!) and then returning to 8.1 pro. Lets hope they have replaced their QA department...oh probably never had a department to start with!

 

So here we are in July and evidently not fixed, at least in the production build, because I got this today. Like others, drove me nuts for awhile. Hopefully it goes away in the anniversary release. Honestly, based on everything I have read, this should have been an easy hotfix sort of thing rolled out with a security release.

At least for me, it makes me question any error I get now. Makes it very hard to troubleshoot an issue if they have you snipe hunting. Honestly expected more from Windows 10, and Microsoft, by this point.

 

...with the last updates from ms on 07/12, the problem is still not fixed on my two 10 pro devices...real shame they can not get it together...now 8 months since ms broke their flagship with Threshold...BUT hay, they bought LinkedIn!
NOTE to ms: 'just buy a real software company'...please.

 

And that is the reason I have sadly gone back to Windows 7 for my tower. I was growing fond of Windows 10 on my desktop, until this happened. I've decided to stand by and wait. I have another computer that is Windows 10 that's a 2n1, so it does not have this issue. I'll hold off until someone confirms this bug is fixed. Windows 7 is stable on my tower, and it is my gaming machine as well. I prefer stability over gee whiz when it comes to the OS on this device.

 

Seems to me like a weak reason to abandon Windows 10. It is annoying, but doesn't affect the operation or performance. Windows 10 has so much in performance improvements, support for new protocols, etc. over Windows 7.

 

Actually not weak at all. It was causing an issue. I was noticing quirks in my inputs with some games. Video performance was off, and I/O on some desktop programs would stutter at times. That's how I backed into this. I originally assumed I had an I/O driver or kernel corruption problem. When I found out it was my graphics driver I tried several things, remove/replace driver. Roll back to earlier versions, clean installs, then running sfc before every driver install. etc. etc.

At the end of the day, the NVidia driver, at least the last few versions that have been released, does not work correctly with Windows 10. Based on other forum threads, here and other sites, it's a known issue in Windows 10 that came out several months ago. Microsoft has not fixed it, and it appears the anniversary version is still broken. This isn't like NVidia is cheap hardware or used by a minority of people. My 970 card is not something I would expect to have an issue.

Interfacing with common hardware, such as ASUS and NVidia is core to the operating system. It's more important than gee whiz features. Additionally it's a bug, not a feature. It's a break fix. Something they should roll out in a monthly update. Sorry, but it's piss poor programming. If they can't fix the basics on Windows 10 yet, I'll wait before I upgrade my hardware that is solid on Windows 7.

 

You are getting the error in scan because Microsoft thinks you have the wrong opencl.dll, when in fact you have the correct, Nvidia version.

Yeah, he graphics driver problems aren't with Windows 10, they are with Nvidia recent drivers, even with simple stuff like streaming a video would hang. I couldn't use anything after 362.00 until the latest 368.69. I haven't had any issues with 368.69 but I don't have all recent games.

 

Hi Geneo
Neither of my two 'corrupt sfc' 10 Pro devices have Nvidia graphics drivers installed inside the can! Only intel graphic drivers...HP & ms (Surface Pro 2) manufacturers. There is NO excuse for shoddy workmanship unless it comes from ms!...less, an excuse when ms breaks it, finally knowledge's it has broken its own software; and even less, when it(ms) can not correct/repair the failure. I would be unable to find any associate/friend or Family member...anyone in fact. Who would tolerate a broken item in their possession for this long without returning such item as "not fit for purpose". As I said; shoddy practices/workmanship...

 

There may be other things going on for other folks but I agree with you Geneo, I see this too. I am on 362.13 so I am going to check for NVIDIA updates, I have a third-party application I run that is a very sophisticated use of graphics hardware even though it's a business app, and I regularly see the "Your display driver has crashed and restarted" with it. I never saw this once over years of work prior to Windows 10. That said I really like Windows 10...

 

I have been clean installing the latest stable NVIDIA driver on each new Insider Preview. Right afterwards I was heading to the Feedback Hub and I was reporting the "openCL.dll" issue together with the OS build [number]. Nothing happened and...actually...this specific feedback of mine was not getting (almost) any upvotes!...

Recently, like four days ago, I've quit the Insider builds and I have installed Linux Mint "Sarah" on my second SSD, as an alternative OS, feeling I have already gotten a good sense on how the Anniversary will be. My main (primary) OS still is Windows 10 Pro.

The best thing you can do is clean-install the NVIDIA driver after each upgrade, never run SFC and report + upvote this issue.

 

I would appreciate an update on how the newly released version works for you. As I said, I like Windows 10, but the flaky graphics driver issue needs to stop. I can appreciate how this might be a no man's land. Being in IT it's often hard to tell if the issue is the vendor or the OS. However, Windows 7 is rock solid with the NVidia drivers, including 368.69. This makes me think it's something with Windows 10. It could be the gee whiz touch capability is doing something wonky with how the drivers behave, it's hard to tell. It appears it showed up with Threshold, based on user comments. For me, once there is confirmation of a fix, and we've gone through at least one update cycle without issue, I'll consider going back to Windows 10. Until then, Microsoft's QA and testing have become too unreliable. Introduction of bugs, slow to fix bugs due to seeming fetish with new and shiny(introducing more bugs) and worst of all, reintroduction of old bugs at times, point to a code release QA problem. Once/if they can get their act together I'm all for going all in with Windows 10.