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

Page 3 of 7 FirstFirst 12345 ... LastLast
  1. Try3's Avatar
    Posts : 2,305
    Windows 10 Home x64 and Pro x86
       #21

    KRZ,

    I am not quite sure from your responses whether or not SFC now succeeds on your computer.

    My SFC kept failing despite using the suggestions that others had made but has just succeeeded on all three of my computers by using Bastet's variant method -

    1 Restart the computer
    2 SFC /ScanNow
    [no further reboots/restarts - just continue in the same session]
    3 dism.exe /Online /Cleanup-image /Restorehealth
    [no further reboots/restarts - just continue in the same session]
    4 SFC /ScanNow [This fixes the failures & further, unnecessary, SFC runs just report no problems]

    Denis
      My ComputerSystem Spec

  2.    #22

    Yeah, my enquiry was more general: why (if) should I run it in the first place?

    SFC and/or DISM in fix mode generates a lot of unnecessary junk under C:\Windows\WinSxS\Temp (which ultimately gets deleted with the maintenance run or similar) - hence my reluctance to run them in the first place. That's all.
      My ComputersSystem Spec

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

    Try3 said: View Post
    Bastet's variant method -

    1 Restart the computer
    2 SFC /ScanNow
    [no further reboots/restarts - just continue in the same session]
    3 dism.exe /Online /Cleanup-image /Restorehealth
    [no further reboots/restarts - just continue in the same session]
    4 SFC /ScanNow [This fixes the failures & further, unnecessary, SFC runs just report no problems]

    This is consistent with my early successes having restarts before and after CU KB4507453 18362.239

    Machine 1:

    - no restart

    sfc /scannow
    dism /Online /Cleanup-image /Restorehealth
    sfc /scannow

    - restart ( after CU .239 )


    Machine 2:

    sfc /scannow
    - restart ( after CU .239 )

    sfc /scannow
    dism /Online /Cleanup-image /Restorehealth
    sfc /scannow
      My ComputersSystem Spec

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

    catspyjamas said: View Post
    https://support.microsoft.com/en-us/...s-as-corrupted

    MS have acknowledged the issue and advise just ignoring it. Looks like they will fix it in "future releases of Windows".
    I'm marking this solved
      My ComputersSystem Spec

  5.    #25

    Still:

    This is a known issue


    and

    you can safely ignore the SFC error messages

    have both nice ring to it...

    (I have moved to 1903 myself last weekend and fixed it on the go as well nevertheless)
      My ComputersSystem Spec

  6.    #26

    Just FYI, I've seen it on 1903 (18362.239), 19H2 Insider Preview (18362.1005), and 20H1 Insider Preview (18936.1000) on all such machines running Windows Defender. I'm in the same camp as the Bleeping Computer person, who speculates that recent Windows Defender updates are the culprits. So I said in one of my blog posts for today, in fact: Recent Win10 Updates Bollix Defender Module Hashes - Windows Enterprise Desktop.
    HTH,
    --Ed--
      My ComputersSystem Spec


  7. Compumind's Avatar
    Posts : 1,196
    Windows 10 Pro x64, Various Linux Builds, Internet Security Specialty.
       #27
      My ComputerSystem Spec

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

    Ed,

    About "speculates that recent Windows Defender updates are the culprits" - they were definitely the culprits.

    I had run SFC successfully then updated just WD [from 4.18.1905.4 to 4.18.1906.3] then ran SFC again and the fault was present.

    See also SFC incorrectly flags WD PowerShell module files as corrupted - MSSupport

    Denis
      My ComputerSystem Spec

  9.    #29

    After having fixed the issue myself a few days ago with an...
    sfc
    dism
    sfc (found and repaired errors)-
    sfc (windows resource protection found no integrity violations)
    ...the corruption is back again. Last night windows update pushed a new antimalware update. I ran sfc /verifonly immediately after it had installed. Sfc again found errors it couldn't fix. I don't know what to do now. Leave it alone or repair again
      My ComputerSystem Spec

  10. Try3's Avatar
    Posts : 2,305
    Windows 10 Home x64 and Pro x86
       #30

    sportsfan,

    What Antimalware Client Version are you on now? [WD, Settings, About]

    Mine is still v4.18.1906.3 and SFC remains fixed.

    What are the irreparable / irrepairable / unrepairable errors?

    Denis
      My ComputerSystem Spec


 
Page 3 of 7 FirstFirst 12345 ... LastLast

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 23:50.
Find Us