Windows 10: Opencl.dll on sfc /scannow

hey guys long time lurker here, usually i find solutions on my problem but this time around, i have no idea what to do!

Short story: ran sfc /scannow and got the message "found corrupt files but cannot repair," specifically regarding Opencl.dll. Can i fix this w/o doing a reset?

Long Story (in outline form):
- got a new SSD
-with my old HDD still in place(with w7) installed w10 thru usb in the SSD
-It worked, and thru the desktop i transferred files from my old HDD to the SSD
-tried to format the HDD thru my computer, did not work, got some error
-proceeded to format the hdd through w10 installation usb - worked
-changed the boot order so SSD load first
-got an error saying no OS is found
-plugged in w10 usb and did "repair my computer" - worked
-able to access desktop, play games, etc.
-decided to run sfc /scannow to be sure, and got that error
-did a disk cleanup and then ran sfc again, still the same

also i have attached the log that i got from the sfc

:)

 

SFC /SCANNOW report opencl.dll bad

Just to confirm what PiKohler posted later in this thread, Anniversary Update has cured the inability of sfc /scannow to complete. Whether they fixed the bad opencl.dll thing or it was something else, no idea. But sfc /scannow now works and reports all
is well with my Windows 10 Pro 64 bit Anniversary Update.

 

SFC /SCANNOW report opencl.dll bad

Just executed the Windows 10 Anniversary Update and it works now, finally

 

Perhaps not, even if you were to do a clean install at this point - see here: SFC some corrupt files can not be fixed

Normally, folks would advise that the next step is using DISM to repair this problem but, if you check the thread I linked above, you may decide you don't want to reinvent the wheel.

P.S. - Welcome to TenForums! (now that you no longer lurk)

 

I thoroughly enjoyed that thread. haha! Well as of right now, I'm not getting any Errors and can play my games fine. So from what I understand the error may eb caused by conflicts b/w the Microsoft Opencl.dll and the nvidia Opencl.dll.

 

That was my take from the thread - looks like everyone's stuck with tolerating the situation (doesn't impact me, however) until MS fixes it. I would suggest monitoring for any update on it.

 

...and we're all tearing our hair out trying to find a solution to a problem-in-name-only that is not within our control.

You saved me a lot of work, although I wish I'd found this thread sooner (because that would have saved even more).

I bought this laptop right before Christmas, and so far, I've refreshed it and reset it, not to mention all the tinkering to clean up errors cluttering my Event Viewer. I was on the verge of a clean install, but I'm not going to waste my time.

I'm not in love with Microsoft at the moment, but at least the flippin' thing works even if looking at the Event Viewer drives me right out of my mind.

Thank you again.

 

That's the great thing about TenForums - you may have to dig around a bit but can nearly always find someone who's worn your shoes and either shined them up or else stuck them in the closet.*chuckle