SFC Scan Finding Corrupt Files Post Update

Discussion in 'Microsoft Surface Book' started by ABswl13, Nov 20, 2015.

  1. ABswl13

    ABswl13 Member

    Joined:
    Nov 8, 2015
    Messages:
    43
    Likes Received:
    3
    Trophy Points:
    8
    My Device:
    Surface Book
    Since updating my Surface Book (i7, 256gb) with Microsoft's 11/18 updates, I've noticed that when I do an SFC scan, I get notified that it found corrupt files but was unable to repair them. I did a complete reset and reinstalled everything, including the most recent firmware update, and when I did another SFC scan, I once again received the same message that it found corrupt files but was unable to repair them.

    Is anyone else having this problem? Is there something else I can try to fix this?

    Thanks for your suggestions/comments.
     
  2. GreyFox7

    GreyFox7 Super Moderator Staff Member

    Joined:
    Jul 27, 2014
    Messages:
    6,335
    Likes Received:
    1,279
    Trophy Points:
    113
    Run dism /online /cleanup-image /restorehealth
    Then run SFC /Scannow
     
    leeshor likes this.
  3. ABswl13

    ABswl13 Member

    Joined:
    Nov 8, 2015
    Messages:
    43
    Likes Received:
    3
    Trophy Points:
    8
    My Device:
    Surface Book
    Thanks for the suggestion. I tried that and received the following error"

    Error: 0x800f081f

    The source files could not be found.

    Does that mean anything to you? Is there something else I should try?
     
  4. giliav

    giliav New Member

    Joined:
    Nov 18, 2015
    Messages:
    26
    Likes Received:
    4
    Trophy Points:
    3
    My Device:
    Surface Book
    I'm getting the same. Perhaps it's normal on TH2 release?
     
  5. Wayne Orwig

    Wayne Orwig Active Member

    Joined:
    Mar 18, 2013
    Messages:
    332
    Likes Received:
    43
    Trophy Points:
    28
    I was getting that. Plus the 'source file not found' when I ran DISM. Plus I had a problem with one some software I had installed.
    I did a full reset/restore, whatever it is call. I'm just now getting all of the updates back in.
    I assume SFC will give me the same error once I'm fully back. Bummer.
     
  6. tatornator12

    tatornator12 Member

    Joined:
    Oct 26, 2015
    Messages:
    58
    Likes Received:
    1
    Trophy Points:
    8
    My Device:
    Surface Book
    I also just ran sfc/scannow out of curiosity and am getting corrupt files that can't be fixed. When I try to run DISM, it says the option is unknown, error: 87.
     
  7. GreyFox7

    GreyFox7 Super Moderator Staff Member

    Joined:
    Jul 27, 2014
    Messages:
    6,335
    Likes Received:
    1,279
    Trophy Points:
    113
    I don't have a SP4 anymore but I ran it on both of the two I had. IDK why it wont run now. maybe they don't want that. ;)
     
  8. olimjj

    olimjj Active Member

    Joined:
    Mar 27, 2013
    Messages:
    550
    Likes Received:
    113
    Trophy Points:
    43
    Location:
    Where no man has gone before.
    My Device:
    SPro3
    Not trying to be picky, but to be more precise, the reply statement is "found corrupt files but was unable to fix some of them"
    This elevated (Admin) command prompt scan has been giving me the this same response on all 3 of my Surface Pro's, 1,2,3 for some time now. I am not sure that the algorithm used still applies to date, or that Microsoft even supports its use in this regard. If you are not having a specific system related issue, I would not use it to open a Pandora's box of alerts to worry about. I have done just that, basically ignore it, if my machine was behaving to my satisfaction, and to look elseware for a solution if it was not.
     
  9. Wayne Orwig

    Wayne Orwig Active Member

    Joined:
    Mar 18, 2013
    Messages:
    332
    Likes Received:
    43
    Trophy Points:
    28
    I have used it in the past to fix issues. So I would like for it to be working properly.
     
  10. CrownedMartyr

    CrownedMartyr New Member

    Joined:
    Nov 24, 2015
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro4
    I'm experiencing the exact same thing with both the SFC and DISM commands. Have you tried to identify which file is corrupted? Instructions here: https://support.microsoft.com/en-us/kb/929833

    Mine seems to only reference the opencl.dll file (see attached). I spoke with Microsoft support and for what it's worth, they said not to worry about it.
     

    Attached Files:

  11. Sprayingmango

    Sprayingmango New Member

    Joined:
    May 16, 2016
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    Surface Book
    Can anyone detail how to do the DISM repair? Also, my new surface book will not update firmware on some devices in my device manager. Some controllers and the UEFI have exclaimation points near them and refuse to update themselves.
     
  12. Niterider4

    Niterider4 Active Member

    Joined:
    Oct 29, 2015
    Messages:
    173
    Likes Received:
    54
    Trophy Points:
    28
    My Device:
    Surface Book
    I have read elsewhere that the sfc/scannow issue is related to there being more than one version of opencl.dll. The version on the SB is fine, but sfc expects to see a different version, so it throws an error. The sources I read said that it is not a concern.
     

Share This Page

Search tags for this page

corrupted files found on surface

,

corrupted files on surface book

,

microsoft surface pro 3 fixing corrupt system files

,

sfc scan showing errors on new surface book

,

surface 3 corrupted files

,

surface book sfc corruption

,

surface book sfc scannow

,

surface pro 4 failing sfc scan after it has been reset