Windows 10 SFC /SCANNOW Error that I Don't Know How to Fix

Status
Not open for further replies.

mikeynavy1976

Distinguished
Feb 14, 2007
454
1
18,815
Right after installing Windows 10 I ran sfc /scannow and had 0 issues. Now I get an error related to opensc.dll. It is: Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" I thought this was an Nvidia File so why is sfc flagging it? I tried to make sure that both the version in system32 and SYSWOW64 are the same and they are. How can I either tell sfc to stop looking at it or fix it. Any help would be great.
 
Solution
It may not be the name of the file, but an inconsistency between the file in the system 32 folder
and the syswow64 folder.
Have a check both are of the same file size, windows may be doing a file size check as part of a verification.
Also check that the time and date stamp of each .dll file is the same.
It should be one or the other causing the problem.
It may not be the name of the file, but an inconsistency between the file in the system 32 folder
and the syswow64 folder.
Have a check both are of the same file size, windows may be doing a file size check as part of a verification.
Also check that the time and date stamp of each .dll file is the same.
It should be one or the other causing the problem.
 
Solution
Status
Not open for further replies.