(solved) Errors on sfc /verifyonly

Discussion in 'Windows 10' started by a123179, Aug 16, 2016.

  1. a123179

    a123179 MDL Novice

    Aug 7, 2014
    43
    1
    0
    #1 a123179, Aug 16, 2016
    Last edited: Aug 16, 2016
    I'm still on v1511, after a clean install, and I did a "sfc /verifyonly" and it founds errors; is this serious?
    Before upgrading to AU I want to run sfc /scannow, but first how can I see what kind of errors I have?
    The log (windir\Logs\CBS\CBS.log) is very long, as it is also on a error-free pc.
    I also did a scandisk from Explorer without errors.
     
  2. LatinMcG

    LatinMcG Bios Borker

    Feb 27, 2011
    5,434
    1,486
    180
    run mediacreationtool to reupgrade and it should fix and also take u to AU
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,860
    21,199
    340
    Run this in an elevated cmd: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt

    It will result in a txt file on your desktop with the info about the found errors.
     
  4. a123179

    a123179 MDL Novice

    Aug 7, 2014
    43
    1
    0
    #4 a123179, Aug 16, 2016
    Last edited: Aug 16, 2016
    (OP)
    Thank you, it was much more easy to find the problem: c:\windows\syswow64\opencl.dll

    I was thinking about repair only this file and re-run again sfc /verifyonly to check if everything was fine, but:
    sfc /scanfile=c:\windows\syswow64\opencl.dll
    gives an error, which translated in english is something like: "Windows Resource Protection: can't execute this"
    By the way what that "SR" in the log file stands for?


    I'll keep this in mind, thank you.
     
  5. endbase

    endbase MDL Guru

    Aug 12, 2012
    3,914
    1,212
    120
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    16,860
    21,199
    340
    The opencl.dll error is a known error, it always occured when checking the filesystem on 1511 but normally it gets repaired by sfc /scannow
     
  7. a123179

    a123179 MDL Novice

    Aug 7, 2014
    43
    1
    0
    I actually already read about that, but wanted to be sure the eroor was only caused by this opencl.ddl.
    I suppose this can be marked as solved, thank you all.