Many unrepairable corrupted Defender files found by sfc /scannow

Page 1 of 3 123 LastLast

  1. Posts : 533
    Windows 10 Pro x64 Version 21H2
       #1

    Many unrepairable corrupted Defender files found by sfc /scannow


    Anyone else noticed a lot of Defender files being corrupted after doing an sfc /scannow prompt? Here are just some of the corrupted lines found in the CBS log file:

    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted
    - Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted
    - Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted
    - [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted

    Beneath each line it says that the hashes for the concerning file member doesn't match.


    I have Windows 10 Pro 1809 x64
    Anyone else noticed these corruptions after an sfc /scannow prompt?
      My Computer


  2. Posts : 819
    10
       #2

    No, but I'll share similar in a new thread
      My Computer


  3. Posts : 16,949
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #3

    Yes, lots of us have had this problem. See my consolidated ditty on SFC errors [WD update problem] - TenForums

    Denis
      My Computer


  4. Posts : 533
    Windows 10 Pro x64 Version 21H2
    Thread Starter
       #4

    Try3 said:
    Yes, lots of us have had this problem. See my consolidated ditty on SFC errors [WD update problem] - TenForums

    Denis
    The Microsoft article describing this issue is stating the following:

    Future releases of Windows will use the updated files in the Windows image. After that, SFC will no longer flag the files.

    Does this mean we actually have to wait for anothor big feature update of Windows until this is fixed?
      My Computer


  5. Posts : 16,949
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #5

    Does this mean we actually have to wait for anothor big feature update of Windows until this is fixed?
    There is no way of telling how long MS will take.

    I have just finished revising that post of mine that I linked you to before. It now contains the comment that you can safely leave the problem if it is purely related to the Windows defender powershell components
    [listed in that post of mine] and then explains how you can easily fix it for yourself.

    Denis
      My Computer


  6. Posts : 4,594
    Windows 10 Pro
       #6

    I posted the command to run as Admin in Command Prompt in this thread, it will fix it. Reply #4

    SFC Reports Corruption Issues on all 4 of my PCs (after recent update)
      My Computers


  7. Posts : 9,790
    Mac OS Catalina
       #7

    JohnnyGui said:
    The Microsoft article describing this issue is stating the following:

    Future releases of Windows will use the updated files in the Windows image. After that, SFC will no longer flag the files.

    Does this mean we actually have to wait for anothor big feature update of Windows until this is fixed?
    Yes, as 10 goes through its growth changes, features will break and get fixed as MS tries to get it right.
      My Computer


  8. Posts : 7,904
    Windows 11 Pro 64 bit
       #8

    This is a known problem due to poor MS software QA.

    Run:
    Dism /Online /Cleanup-Image /RestoreHealth
    sfc /scannow (run twice - once to fix errors and again to check all is clear)
      My Computers


  9. Posts : 2,734
    Windows 10
       #9

    Yes, same here, for the first time in 6 years SFC /scannow has actually detected problems.
    I have used that SFC several times alternating with the DISM command line stuff. Also going to Windows updates.

    That seems to clear it.
      My Computer


  10. Posts : 533
    Windows 10 Pro x64 Version 21H2
    Thread Starter
       #10

    bro67 said:
    Yes, as 10 goes through its growth changes, features will break and get fixed as MS tries to get it right.
    Windows Update is offering a new update for the WD platform, KB4052623. Does this solve the issue for you guys?
      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 10:43.
Find Us




Windows 10 Forums