Windows 10: SFC some corrupt files can not be fixed

When i had the issue could not be fixed one opencl.dll was dated the same date or close to date of NVIDIA Driver, but again this whole issue has only happened in build 105860 of Win 10 for me.

 

Let me just say before and now this issue it had not caused me any issues with PC crashes or anything else.

 

It must be the same because of hardlink between them. The size 26.5k means it is Microsoft one, not from Nvidia driver. Check C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_15545327b539cefa\OpenCL32.dll (or some name like this started with nv_disp) for size which must be if Nvidia driver is not damaged by Microsoft. Nvidia copies this OpenCL32.dll to syswow64\opencl.dll

 

There you go, 11/5/15

 

Similar issue, you commented Corrupted files - DISM or SFC results more accurate?

 

So, correct syswow64\opencl.dll must be 103kb in your case. If you achieve opencl.dll size 103kb and no error from sfc /scannow in the same time, it means problem is solved. Any other case means not.

 

Come again, SysWOW is not 103kb, the other is in mine C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_15545327b539cefa\OpenCL32.dll ?

 

errors were fixed as you saw after the run of sfc and dism

 

1) It is because you restore wrong one by SFC. Just reinstall the Nvidia driver and will get correct one (maybe after reboot).
2) SFC error is fixed, but Nvidia DLL is damaged by Microsoft.

 

I just showed you when i reinstalled the driver and yes sfc fixed it now. So if i reinstall it again, saying not run sfc or dism again so it keeps correct driver ? And do you feel this will cause an error on system if i do it this way instead, by reinstalling the driver and not making sfc correct it ? What is this going to do for me as there is no performance issue shown with display adapter even in dxdiag or on system.

Reran sfc just now

 

How or did you fix your own issue then , this way? Oh, i missed part about reboot after driver reinstall, but i did that and ran sfc it corrected it.

 

1) Yes. There is no needs to run SFC or DISM to damage perfectly valid Nvidia dll. Microsoft replacement dll have reduced functionality, about 2/3 of code removed.
2) I live with SFC error on that file for now.

 

Not sure which one is damaged or cause of this,NVIDIA's drivers or MS Build. As your issue happened before this build, mine did not.

 

It is recent Microsoft bug, Nvidia does nothing new or wrong here. Nvidia always installs this two opencl.dll's that way, before too.

 

Kind of figured this, NVIDIA puts out driver updates often. Hopefully be a windows update to resolve it, read on GeForce sites about this issue when researching it.