SFC some corrupt files can not be fixed

Just an update, on my system running the 353.82 drive, which was running fine I installed 359.0 and 359.06. Both drivers resulted in the SFC errors you are seeing.

Possibly, the way the driver files are checked is different from earlier version of Windows and since Microsoft has not yet allowed the Update process to go to these new drivers, SFC and DISM cannot find information on the Microsoft server to correct the error.

I am running the new drivers and they seem to be running fine. If I want to stop the SFC errors, I will probably have to revert to the current Windows Update version of the Nvidia driver.

When I did the upgrade, the opencl.dll ~26 K file was replaced by one that was around 103 K.

Would you be kind enough to perform a "winsat formal -restart clean" process for me and see if it finishes?

kevindd992002 said:

Would you be kind enough to perform a "winsat formal -restart clean" process for me and see if it finishes?

Yes, it finished. Is there some specific information you need about the run?

Saltgrass said:

Yes, it finished. Is there some specific information you need about the run?

I'm just trying to make sure that this opencl.dll problem is not connected with my winsat problem described here. I've read in some forum that the graphics driver was causing this same problem to him.

Can you check if you see any similar error in the end of your winsat.log (C:\Windows\Performance\Winsat)? And just to confirm, your system currently has the opencl.dll and you're running Windows 10 TH2, correct?

kevindd992002 said:

I'm just trying to make sure that this opencl.dll problem is not connected with my winsat problem described here. I've read in some forum that the graphics driver was causing this same problem to him.

Can you check if you see any similar error in the end of your winsat.log (C:\Windows\Performance\Winsat)? And just to confirm, your system currently has the opencl.dll and you're running Windows 10 TH2, correct?

Without causing a problem on the thread, I see nothing like you show, but I am not running the Enterprise version.

I think that the latest nvidia driver (361.43) has resolved this issue in my system, on Build 11082 only. See here.

Joanne said:

I think that the latest nvidia driver (361.43) has resolved this issue in my system, on Build 11082 only. See here.

Thanks Joanne for that update and information, right now i am using Build 10586.36, so i will have to wait and see, thanks again.

I also had same problem Windows 10 ver 1155 - could not get scannow to repair and could not get DISM to work with either install.esd or install.wim from any source or by any method that Brink had graciously supplied. Tried this by topgundcp and it worked perfectly. Was finally able to use DISM and then scannow fixed the rest. Much appreciated topgundcp!

topgundcp said:

I got exactly the same problem and here's how I fixed it. Everything was done from desktop.
1- Create a folder on desktop: mount
2- Copy install.wim to desktop. (used the ISO downloaded from techbench)

Open Admin Command prompt, copy/paste each line and run:

1. Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount
2. Dism /Online /Cleanup-Image /CheckHealth
3. Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess
4. Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
5. re-run: sfc /scannow

Now i feel this OpenCL.dll issue is from Windows 10 and possibly just this build 10586.36 of it. Recently i setup an older PC with clean install of Windows 8.1 Pro and put in one of my NVIDIA Graphics card with the newest drivers 361.43 and SFC came up clean, no integrity violations and DISM was fine also. OpenCL.dll was not changed.

jds63 said:

Now i feel this OpenCL.dll issue is from Windows 10 and possibly just this build 10586.36 of it. Recently i setup an older PC with clean install of Windows 8.1 Pro and put in one of my NVIDIA Graphics card with the newest drivers 361.43 and SFC came up clean, no integrity violations and DISM was fine also. OpenCL.dll was not changed.

No, Our opencl.dll problem happened AFTER the last major update to build 1511, when we were on build 10240 their was no opencl.dll problem, sfc ran fine with no errors.
The reason your Windows 8.1 Pro has no errors, is because their is no problem with older windows versions This is only a Windows 10 problem AFTER build 10240. Right now if you had the latest Insider build, this problem with Opencl IS FIXED. Which means Microsoft has addressed this problem in the test versions being used by the Insiders now. How long it will take MS to release this update for this problem is anybody's guess? But at least MS has fixed this problem.