Microsoft has recently acknowledged an issue with the System File Checker (sfc.exe) in Windows 10 version 1511 (November Update), explaining that the company is already working on a fix that should be released very soon to users.
Reports of errors experienced when running sfc.exe /scannow in Windows 10 version 1511 have reached the web every once in a while since the company rolled out the update in November last year, but it has never seemed to be a widespread issue.
Fix already on its way
And yet, according to the software giant itself, it turns out that there’s indeed a problem with this feature and users could be getting an error reading “Windows Resource Protection found corrupt files but was unable to fix some of them.” The cbs.log file shows opencl.dll as a corrupt file, but Microsoft says that it isn’t actually corrupt, and you can safely ignore the warning.
“When you install Windows, it installs a version of opencl.dll. However hardware drivers may also install their own version of opencl.dll, and if the driver version is different than the one installed by Windows, SFC may report this as file corruption and may not replace the file,” a company support engineer has
explained.
