sfc /scannow found corrupt files after fresh win10 install


  1. Posts : 4
    10 PRO x64
       #1

    sfc /scannow found corrupt files after fresh win10 install


    I started scan with admin priv.

    Windows Resource Protection found corrupt files but was unable to fix some of them.

    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.
    CBS.log - mega.nz
      My Computer

  2. sportsfan148's Avatar
    Posts : 977
    Windows 10 Home 202H
       #2

    If the errors are related to the Defender Platform..dont worry about them. Microsoft are aware of the issue and you can ignore it. Or if you wish to fix it just Run DISM /Online /Cleanup-Image /RestoreHealth from an administrator Command Prompt. Restart your PC . Then Run sfc /scannow again from the command prompt (admin) and the corruption will be fixed.
      My Computer

  3. AndreTen's Avatar
    Posts : 24,097
    Windows 10 (Pro and Insider Pro)
       #3

    Could be the bug MS fixed few days ago. It's about Windows defender, which was preventing update od the system files.
    Check if your WD was updated (at least version 4.8.1908). And try sfc gain

    According to Wilders Security forum, and Bleeping Computer DISM commands have to be run


    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth
      My Computers


  4. Posts : 4
    10 PRO x64
    Thread Starter
       #4

    in .log it says about power shell and onedrive.lnk , so i can ignore and hope to microsoft fix this..
    thx!!
      My Computer

  5. AndreTen's Avatar
    Posts : 24,097
    Windows 10 (Pro and Insider Pro)
       #5

    Try the procedure described above (we both posted pretty much the same solution, sportsfan fast faster by seconds )

    Here is support article from Microsoft
      My Computers


  6. Posts : 4
    10 PRO x64
    Thread Starter
       #6

    you have .log , this scan was the first, you can search for „corrupt” and will find files
    this is not a real problem, and i don't care, but is not normally to get this after win installation....
    to use dism is not very ok/static
      My Computer

  7. Farvatten's Avatar
    Posts : 686
    Windows 10 Pro 64bit 21H1 19043.1081
       #7

    Levin97 said:
    in .log it says about power shell and onedrive.lnk , so i can ignore and hope to microsoft fix this.. thx!!
    Your sfc /scannow problem with the Onedrive.lnk, which appears to have been fixed here in the CBS.log, is independent of this ongoing Powershell hash corruption due to the Defender Platform updates that started almost 2 months ago. ( see link )

    Code:
    2019-08-21 19:57:10, Info                  CSI    00000299 [SR]  Repairing corrupted file  \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start  Menu\Programs\\OneDrive.lnk from store
    2019-08-21 19:57:10, Info                  CSI    0000029b [SR] Repair complete

    sfc /scannow failing after this latest Defender Platfom update.


    Worth noting, I've seen corruption from Microsoft's *.lnk's after innocently changing the icons to their installed shortcuts, mine however were not fixed by the sfc /scannow.

    Farvatten said:
    Denis, unfortunately this has not been my experience. I've seen sfc /scannow corruption that it could not repair from something as innocent as changing the icon on one of these "Windows Administrative Tool" shortcuts and as recently as the 1903 Feature Update.

    Thankfully I was able to quickly fix it by copying the original version back from Macrium. With my sfc /scannow's normally taking only 5 minutes, it just makes sense to run it before any image is made.


    Attachment 243266
    Code:
    2016-11-09 21:08:32, Info                  CSI    0000147a [SR]  Beginning Verify and Repair transaction2016-11-09 21:08:34, Info                   CSI    0000147c [SR] Cannot repair member file [l:23]'Computer  Management.lnk' of Microsoft-Windows-ComputerManagementSnapin, version  10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the  store, hash mismatch
    2016-11-09 21:08:37, Info                  CSI    000014c1 [SR] Cannot  repair member file [l:23]'Computer Management.lnk' of  Microsoft-Windows-ComputerManagementSnapin, version 10.0.14393.0, arch  amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-11-09 21:08:37, Info                  CSI    000014c2 [SR] This  component was referenced by  [l:165]'Microsoft-Windows-Client-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-Package-AutoMerged-admin-Deployment'
    2016-11-09 21:08:37, Info                  CSI    000014c5 [SR] Could  not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start  Menu\Programs\Administrative Tools\Computer Management.lnk; source file  in store is also corrupted
    2016-11-09 21:08:38, Info                  CSI    000014ea [SR] Verify complete
      My Computers


  8. Posts : 165
    Windows 10 Pro 64-bit
       #8

    I had the exact same problem in each of my Windows 10 fresh installations, whether it was 1809, 1903. Every time after a fresh installation SFC /Scannow found corruptions, but it managed to repair the corruptions on all of these cases. And after that there were no longer any integrity violations.

    This is weird because when I previously had Windows 8.1 never did SFC /Scannow find any corruptions. In fact even when I had problems with Windows 8.1 after 4 years, SFC failed to find integrity violation.

    Sometimes when you have real problems SFC reports as no integrity violation, next time you feel you don't have any problems and this system reports that it has problems, lol.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:56.
Find Us




Windows 10 Forums