sfc /scannow failing after this latest Defender Platfom update.

Page 7 of 7 FirstFirst ... 567

  1. Posts : 22
    W10 Pro 1909
       #61

    I'm still on 1809, and I've repaired this twice. I think I'll have to let it go pro tem until a fix is provided (whenever that may be).

    I think that, in common with others, my major complaint is that MS have introduced a lot of "pseudo-errors" into an important, critical error-checking and repair component, which has the effect of possibly cloaking other "real" errors; unless of course I spend time investigating the CBS logfile.

    With other problems such as the Event Viewer custom error, I'm drawn to conclude that nothing much has changed with 10 and it's as buggy and uncoordinated as was ever the case.
      My Computer


  2. Posts : 80
    Win10 x64
       #62

    I periodically run SFC just to be sure I haven't mucked things up. So today I found un-repairable errors in CBS.log. Figuring user error was involved I re-imaged to a date where the log was "clean". Oddly though SFC again failed on the reimage. Again I rolled back another 2 weeks, and again SFC found un-repairable items. Then I found this thread and Microsoft's "Don't Worry, Be Happy" thread for this. Good grief Charlie Brown.

    After reimaging back to my current most image I'm off to checkout DISM repair... What a pain this is. A bad CBS report that I must wade through to see if there are issues apart from this WD nonsense.

    Win10x64-1903
      My Computer


  3. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #63

    Telos said:
    I periodically run SFC just to be sure I haven't mucked things up. So today I found un-repairable errors in CBS.log. Figuring user error was involved I re-imaged to a date where the log was "clean". Oddly though SFC again failed on the reimage. Again I rolled back another 2 weeks, and again SFC found un-repairable items. Then I found this thread and Microsoft's "Don't Worry, Be Happy" thread for this. Good grief Charlie Brown.

    After reimaging back to my current most image I'm off to checkout DISM repair... What a pain this is. A bad CBS report that I must wade through to see if there are issues apart from this WD nonsense.

    Win10x64-1903
    Attachment 243111

    Run this bat to extract only the SR lines from the entire CBS log. No need to wade thru all that.
      My Computers


  4. Posts : 80
    Win10 x64
       #64

    f14tomcat said:
    Run this bat to extract only the SR lines from the entire CBS log. No need to wade thru all that.
    Thank you for this. All is clean (for now).
      My Computer


  5. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #65

    Telos said:
    Thank you for this. All is clean (for now).
    You're welcome.
      My Computers


  6. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #66

    Telos said:
    I periodically run SFC just to be sure I haven't mucked things up
    SFC does not check anything that you have any access to. It only checks non-configurable system files.

    So nothing you muck up can be covered by an SFC scan.


    [see below]

    Denis
    Last edited by Try3; 15 Aug 2019 at 13:18.
      My Computer


  7. Posts : 915
    Windows 10 Pro 64bit 22H2 19045.3324
    Thread Starter
       #67

    Try3 said:
    SFC does not check anything that you have any access to. It only checks non-configurable system files. So nothing you muck up can be covered by an SFC scan.

    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.


    sfc  /scannow failing after this latest Defender Platfom update.-windowsadmintools.jpg
    Last edited by Farvatten; 14 Aug 2019 at 20:07.
      My Computers


  8. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #68

    Farvatten said:
    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.
    What did the CBS.log "cannot repair member file" entry say?

    Denis
      My Computer


  9. Posts : 915
    Windows 10 Pro 64bit 22H2 19045.3324
    Thread Starter
       #69

    Try3 said:

    These from when I first noticed it in 1607.

    Here's the one I got after changing the icon on the 'Computer Management' shortcut:

    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

    Here's the one I got after changing the icon on the 'Print Management' shortcut:

    Code:
    2016-11-09 21:11:06, Info                  CSI    000026ab [SR] Beginning Verify and Repair transaction
    2016-11-09 21:11:08, Info                  CSI    000026ad [SR] Cannot repair member file [l:20]'Print Management.lnk' of Microsoft-Windows-Printing-ClassInstallerAndPrintUI-PMCPPC, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-11-09 21:11:09, Info                  CSI    000026f7 [SR] Cannot repair member file [l:20]'Print Management.lnk' of Microsoft-Windows-Printing-ClassInstallerAndPrintUI-PMCPPC, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-11-09 21:11:09, Info                  CSI    000026f8 [SR] This component was referenced by [l:117]'Microsoft-Windows-Printing-PremiumTools-Package~31bf3856ad364e35~amd64~~10.0.14393.0.Printing-PremiumTools-Collection'
    2016-11-09 21:11:09, Info                  CSI    000026fb [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Print Management.lnk; source file in store is also corrupted
    2016-11-09 21:11:09, Info                  CSI    0000271f [SR] Verify complete
      My Computers


  10. Posts : 16,781
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #70

    Well, I've learnt something then.

    SFC used to include several inappropriate files [configurable files such as tcpmon.ini] and they seemed to have fixed that years ago in Win7. Their fix was obviousy either incomplete or ignored when they were updating the SFC list for WIn10.

    Code:
    2019-08-15 17:34:49, Info                  CSI    00000072 [SR] Cannot repair member file [l:23]'Computer Management.lnk' of Microsoft-Windows-ComputerManagementSnapin, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-08-15 17:34:54, Info                  CSI    00000075 [SR] Cannot repair member file [l:23]'Computer Management.lnk' of Microsoft-Windows-ComputerManagementSnapin, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-08-15 17:45:16, Info                  CSI    00000327 [SR] Cannot repair member file [l:23]'Computer Management.lnk' of Microsoft-Windows-ComputerManagementSnapin, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-08-15 17:45:16, Info                  CSI    00000329 [SR] Cannot repair member file [l:23]'Computer Management.lnk' of Microsoft-Windows-ComputerManagementSnapin, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    Denis
    Last edited by Try3; 15 Aug 2019 at 11:56.
      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 06:05.
Find Us




Windows 10 Forums