sfc /scannow failing after this latest Defender Platfom update. Solved

Page 7 of 7 FirstFirst ... 567
  1.    #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 ComputerSystem Spec

  2.    #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 ComputerSystem Spec

  3. f14tomcat's Avatar
    Posts : 42,537
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #63

    Telos said: View Post
    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
    CBS_SR_TO_TEXT.zip

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

  4.    #64

    f14tomcat said: View Post
    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 ComputerSystem Spec

  5. f14tomcat's Avatar
    Posts : 42,537
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #65

    Telos said: View Post
    Thank you for this. All is clean (for now).
    You're welcome.
      My ComputersSystem Spec

  6. Try3's Avatar
    Posts : 2,304
    Windows 10 Home x64 and Pro x86
       #66

    Telos said: View Post
    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; 1 Week Ago at 13:18.
      My ComputerSystem Spec


  7. Farvatten's Avatar
    Posts : 129
    Windows 10 Pro 64bit 1903 18362.295
    Thread Starter
       #67

    Try3 said: View Post
    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.


    Click image for larger version. 

Name:	WindowsAdminTools.jpg 
Views:	5 
Size:	118.4 KB 
ID:	243266
    Last edited by Farvatten; 1 Week Ago at 20:07.
      My ComputersSystem Spec

  8. Try3's Avatar
    Posts : 2,304
    Windows 10 Home x64 and Pro x86
       #68

    Farvatten said: View Post
    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 ComputerSystem Spec

  9. Farvatten's Avatar
    Posts : 129
    Windows 10 Pro 64bit 1903 18362.295
    Thread Starter
       #69

    Try3 said: View Post

    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 ComputersSystem Spec

  10. Try3's Avatar
    Posts : 2,304
    Windows 10 Home x64 and Pro x86
       #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; 1 Week Ago at 11:56.
      My ComputerSystem Spec


 
Page 7 of 7 FirstFirst ... 567

Related Threads
Hi all! Every time Windows 10 Home decides it is time for a forced upgrade of my OS (currently on the 1709 version) I have the same nightmare. The upgrade eventually fails with the message that some windows component is not compatible. After a lot...
Normally have Defender icon set to show on the Taskbar and it usually shows green unless there is a problem. Since I installed build 17074, it starts after a reboot and then just goes away. The icon is showing in the Taskbar for 3-5 seconds and...
Up until today I always got the latest Defender definitions via Windows Update. Today however, WU told me my PC was "Up to date", but checking Microsoft Malware Protection Center told me my definitons were from yesterday. I tried updating through...
Quicken was crashing on startup and nothing seemed to be fixing it. I decided to uninstall and reinstall, and now I number of issues have come up. Quicken install kept closing on its splash screen, so I tried running sfc /scannow. It keeps failing...
Hi there This only seems a problem with IE11 - happened after latest update can somebody please test this link with IE11 to see if it's W10 that's a problem or the particular site or something on my machine From the BBC - Main / Home page...
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 11:04.
Find Us