SFC unable to fix problem

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 31,868
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #11

    lffoar said:
    The only update available is KB5034441 which will not install for whatever reason.
    That is a well known problem. It will not install if your recovery partition is too small. The fix is to make your recovery partition a little larger. See this thread for more details...

    After 3 months since KB5034441 was released, it still won't install
      My Computers


  2. Posts : 886
    Windows 10 Home. 19045.4291 WinVersion 22H2
    Thread Starter
       #12

    Bree said:
    That is a well known problem. It will not install if your recovery partition is too small. The fix is to make your recovery partition a little larger. See this thread for more details...

    After 3 months since KB5034441 was released, it still won't install
    Txs Bree, used the script supplied by Pentagon on page 2 of the forum link you supplied and KB5034441 installed OK.
    One problem solved
      My Computers


  3. Posts : 23,462
    Win 10 Home ♦♦♦19045.4412 (x64) [22H2]
       #13

    @lffoar


    I used REVO Uninstaller (free) to uninstall OneDrive, and did it's "scan for leftovers" and deleted everything it found.

    BEFORE deleting any Apps, I did this tutorial, first...

    Turn On or Off Automatic Updates for Apps in Windows 10 Store


    I haven't had any Apps mysteriously, come back.



    I think what's happening, is that in the wee hours of the night, MS is trying to update a mostly uninstalled OneDrive.
    This is probably causing some file corruption, which SFC is picking up.

    Because OneDrive is "mostly" uninstalled... SFC can't fix it.

    I suggest you go to the MS store and re-install OneDrive, then uninstall it with REVO, making sure you do the "scan for leftovers", and delete everything it finds.

    Then try running SFC again.


    I used REVO to uninstall OneDrive on both Win 10 and Win 11.
    My SFC scans, come up clean. The very rare times, when it finds errors... it can fix them.

    I also followed the tutorial to block Automatic App Updates.
    Last edited by Ghot; 2 Weeks Ago at 20:53.
      My Computer


  4. Posts : 41,534
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    The scans reported residual Avast entries.


    1) As Ghot commented please use Revo uninstaller.


    2) Reboot


    3) Post a new Tuneup plus


    4) Run the V2 log collector and post a share link using drop box or google drive:

    BSOD - Posting Instructions



    5) Post an image or share link disk management:

    How to Post a Screenshot of Disk Management



    6) Run Disk Partition information > post a share link using drop box or google drive

    https://www.tenforums.com/attachment...iskparinfo.bat

    Batch files for use in BSOD debugging
    Batch files for use in BSOD debugging



    Code:
    2024-05-04 09:38:12, Info                  CSI    0000027d [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:38:12, Info                  CSI    0000027e [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:09, Info                  CSI    000003be [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:09, Info                  CSI    000003bf [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:29, Info                  CSI    00000457 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:29, Info                  CSI    00000458 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:33, Info                  CSI    0000047c [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:33, Info                  CSI    0000047d [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    00000483 [SR] Verifying 16 components
    2024-05-04 09:39:34, Info                  CSI    00000486 [SR] Repairing 8 components
    2024-05-04 09:39:34, Info                  CSI    00000488 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    00000489 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048a [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048b [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048c [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048d [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048e [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048f [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
      My Computer


  5. Posts : 886
    Windows 10 Home. 19045.4291 WinVersion 22H2
    Thread Starter
       #15

    Ghot said:
    @lffoar


    I used REVO Uninstaller (free) to uninstall OneDrive, and did it's "scan for leftovers" and deleted everything it found.

    BEFORE deleting any Apps, I did this tutorial, first...

    Turn On or Off Automatic Updates for Apps in Windows 10 Store


    I haven't had any Apps mysteriously, come back.



    I think what's happening, is that in the wee hours of the night, MS is trying to update a mostly uninstalled OneDrive.
    This is probably causing some file corruption, which SFC is picking up.

    Because OneDrive is "mostly" uninstalled... SFC can't fix it.

    I suggest you go to the MS store and re-install OneDrive, then uninstall it with REVO, making sure you do the "scan for leftovers", and delete everything it finds.

    Then try running SFC again.


    I used REVO to uninstall OneDrive on both Win 10 and Win 11.
    My SFC scans, come up clean. The very rare times, when it finds errors... it can fix them.

    I also followed the tutorial to block Automatic App Updates.
    Thanks Mike. I have Revo installed and if I had uninstalled onedrive previously I would have used it if it was listed there. I just reinstalled onedrive but strangely it is not showing in Revo. Anyway, I did another SFC (3 times) and included the new tuneup script.
    SFC unable to fix problem Attached Files
      My Computers


  6. Posts : 41,534
    windows 10 professional version 1607 build 14393.969 64 bit
       #16

    After completing the steps in post #14 create a new folder on the desktop.

    Download to the desktop:

    Download Windows 10 ISO File

    https://www.microsoft.com/en-us/soft...load/windows10
      My Computer


  7. Posts : 2,170
    Windows 11 Pro (latest update ... forever anal)
       #17

    zbook said:
    The scans reported residual Avast entries.
    Of course there are residual entries

    I'm sorry but I just have to say this, I don't know why users insist on recommending and/or using home-brand removal software from reputational problematic software. Of course there'll be leftovers, it's not in their disreputable self-interests for a completely clean removal.
      My Computers


  8. Posts : 23,462
    Win 10 Home ♦♦♦19045.4412 (x64) [22H2]
       #18

    @lffoar


    Did you look on the Windows Apps tab, in REVO?
    It was there back when I uninstalled it. Maybe MS changed something?


    SFC unable to fix problem-00000-revo-junk-removal.png
      My Computer


  9. Posts : 17,012
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #19

    Try3 said:
    The SFC tutorial tells you the Dism command to run [in the notes at the end of Option 3] and also tells you to connect to the internet before running it.
    SFC - TenForumsTutorials
    I don't know if you were online or not at the time.

    And Option 5 tells you how to extract the relevant results to post here if you have any remaining problems.
    Iffoar,

    Please respond.


    Denis
      My Computer


  10. Posts : 886
    Windows 10 Home. 19045.4291 WinVersion 22H2
    Thread Starter
       #20

    Try3 said:
    Iffoar,

    Please respond.


    Denis
    Thanks and yes I was online Denis and have posted results prior

    - - - Updated - - -

    Ghot said:
    @lffoar


    Did you look on the Windows Apps tab, in REVO?
    It was there back when I uninstalled it. Maybe MS changed something?


    SFC unable to fix problem-00000-revo-junk-removal.png
    Yep, found it the windows pane. Thanks mike

    - - - Updated - - -

    zbook said:
    The scans reported residual Avast entries.


    1) As Ghot commented please use Revo uninstaller.


    2) Reboot


    3) Post a new Tuneup plus


    4) Run the V2 log collector and post a share link using drop box or google drive:

    BSOD - Posting Instructions



    5) Post an image or share link disk management:

    How to Post a Screenshot of Disk Management



    6) Run Disk Partition information > post a share link using drop box or google drive

    https://www.tenforums.com/attachment...iskparinfo.bat

    Batch files for use in BSOD debugging
    Batch files for use in BSOD debugging



    Code:
    2024-05-04 09:38:12, Info                  CSI    0000027d [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:38:12, Info                  CSI    0000027e [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:09, Info                  CSI    000003be [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:09, Info                  CSI    000003bf [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:29, Info                  CSI    00000457 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:29, Info                  CSI    00000458 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:33, Info                  CSI    0000047c [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:33, Info                  CSI    0000047d [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    00000483 [SR] Verifying 16 components
    2024-05-04 09:39:34, Info                  CSI    00000486 [SR] Repairing 8 components
    2024-05-04 09:39:34, Info                  CSI    00000488 [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    00000489 [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048a [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048b [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch amd64, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048c [SR] Cannot verify component files for Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048d [SR] Cannot verify component files for Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048e [SR] Cannot verify component files for Policy.14.0.Avast.VC140.MFC, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    2024-05-04 09:39:34, Info                  CSI    0000048f [SR] Cannot verify component files for Policy.14.0.Avast.VC140.CRT, version 14.0.28127.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:12]'win32-policy', manifest is damaged (false)
    Not sure if I've done it right but here goes. I can find no trace of avast anywhere on the computer, have used revo, anything and the avast tool and a search supplies no result.
    Included the files requested.....I think
    Attached Thumbnails Attached Thumbnails SFC unable to fix problem-capture.jpg  
    SFC unable to fix problem Attached Files
      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 14:02.
Find Us




Windows 10 Forums