Many users have encountered the error message “Windows Resource Protection found corrupt files but was unable to fix some of them.” when running the sfc.exe /scannow on Windows 10.
Whenever they search for details in the cbs.log file, the system file checker reports that opencl.dll is corrupt.
This issue may occur in Windows 10 Version 1511. When users install Windows, they install a version of opencl.dll. The problem is that hardware drivers may also install their own version of opencl.dll. In other words, SFC may detect this as file corruption because the driver version is different than the one installed by Windows.
When this error message appears, it does not mean the opencl.dll file is actually corrupt. You don’t have to take any action – you can safely ignore the report that opencl.dll is corrupt, confirms one Microsoft’s support engineers.
The same engineer assures users that Microsoft is aware of this problem in Windows 10 and they are working on a resolution.
This brings us to another debate – whether or not Microsoft should continue to use the sfx.exe tool after all. As one user states on Microsoft’s forum:
SFC.exe is a very useful tool. But in my opinion it does not go well with Windows 10. In the first place, it should be replaced with a tool with a modern UI. The main engine under the hood may still be SFC.exe, which is able to cope with different-versions of the same files at the same time ( remember the heading of this forum post ). But the invocation of the SFC.exe must have a contemporary feel and look. Noone should be urged to open a command prompt with administrator privileges and type in SFC.EXE.
SFC.exe can also work, intermittently, in the background, like Windows defender, and do its job.
The SFC tool caused issues in previous builds as well and given the users’ feedback, it is interesting to see whether or not Microsoft decides to keep the tool as it it, upgrade it completely or simply replace it.
READ ALSO: Fix: Adobe Audition CS6 has Stopped Working