Windows Resource Protection found corrupt files but was unable to fix


  1. Posts : 268
    Windows 10 Pro 64-bit
       #1

    Windows Resource Protection found corrupt files but was unable to fix


    When shutting down, after the drive light has stopped, the power button continues to blink requiring a forced off holding down the power button. Although possibly coincidence, when the laptop is started and later shutdown while on battery vs. commercial power, the machine shuts down properly.

    I ran sfc /scannow and have attached both the command prompt (admin) result screen and CBS.log.

    Chkdsk had no problems.

    I ran DISM /Online /Cleanup-Image /RestoreHealth and have attached the log.

    I cold booted and ran scannow again which continues to show corrupt files.

    The machine did shutdown with no problem (commercial power) after I ran DISM but that could be coincident.

    Should I pursue trying to fix the remaining corrupt files (if there's a reasonable fix other than reinstalling) or see if over the next few days if the shut down problem is resolved and if so leave well enough alone?

    Mark
    Windows Resource Protection found corrupt files but was unable to fix Attached Files
      My Computer


  2. Posts : 25,097
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #2

    markg2 said:
    Should I pursue trying to fix the remaining corrupt files (if there's a reasonable fix other than reinstalling) or see if over the next few days if the shut down problem is resolved and if so leave well enough alone?

    All your problems reported by SFC are for Avast.

    TenForums SFC Tutorial Option Five : To View Only the "SFC" Scan Results from the CBS.LOG


    Code:
    2019-09-19 06:13:49, Info                  CSI    0000024b [SR] Repairing 6 components
    2019-09-19 06:13:49, Info                  CSI    0000024c [SR] Beginning Verify and Repair transaction
    2019-09-19 06:13:49, Info                  CSI    0000024d [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.25325.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2019-09-19 06:13:49, Info                  CSI    0000024e [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.25325.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2019-09-19 06:13:49, Info                  CSI    0000024f [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2019-09-19 06:13:49, Info                  CSI    00000250 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2019-09-19 06:13:49, Info                  CSI    00000251 [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2019-09-19 06:13:49, Info                  CSI    00000252 [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193eb
    bca}, type [l:12]'win32-policy', manifest is damaged (false)
    I find it surprising that SFC is even trying to repair Avast. Just goes to show how deeply Avast gets its claws into the system, it has convinced Windows that it is a system component!

    DISM certainly won't be able to repair this one, so you are stuck with the problem of how (or if) to repair Avast. Just reinstalling it may not be sufficient. You may well have to use Avast's own AvastClear utility to completely remove it first.

    Avast Uninstall Utility | Download aswClear for Avast Removal

    Personally I would stop at that point and switch to using Defender , but if you insist on reinstalling it that would probably fix the SFC errors.
      My Computers


  3. Posts : 39,997
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    Bree posted the Avast finding already.

    1) Uninstall Avast using the applicable uninstall tool
    Avast Uninstall Utility | Download aswClear for Avast Removal

    2) Perform an in place upgrade repair
    Repair Install Windows 10 with an In-place Upgrade
      My Computer


  4. Posts : 25,097
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #4

    zbook said:
    2) Perform an in place upgrade repair
    Repair Install Windows 10 with an In-place Upgrade
    That is a very good suggestion. See the tutorial, it reinstalls Windows while keeping all your files and installed apps
      My Computers


  5. Posts : 268
    Windows 10 Pro 64-bit
    Thread Starter
       #5

    Thanks--

    I had accidentally ended up with Avast a long time ago and thought I'd gotten rid of it (BTW, I've used Norton since DOS).

    I'll use the uninstall as suggested and if that doesn't fix all I'll do the in place install which I've been avoiding for months.

    Mark
      My Computer


  6. Posts : 25,097
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #6

    markg2 said:
    ... the in place install which I've been avoiding for months.
    It's actually a completely painless experience. You'd be hard pressed to see any difference after an in-place repair upgrade (except that everything should now work )
      My Computers


 

  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 08:25.
Find Us




Windows 10 Forums