MS Posts Support Note About Defender SFC /Scannow Errors

Page 1 of 3 123 LastLast
  1. EdTittel's Avatar
    Posts : 3,480
    Windows 10
       #1

    MS Posts Support Note About Defender SFC /Scannow Errors


    See this note for Microsoft's explanation of the Defender PowerShell script issue that leads SFC /scannow to return hash value mismatch errors for those files: System File Checker (SFC) incorrectly flags Windows Defender PowerShell module files as corrupted. According to this document, one needs version 4.18.1908 of the Antimalware platform to avoid this error.

    My only problem now is that some of my 1903 PCs are running version 4.18.1907. The following folders appear in C:/ProgramData/Microsoft/Windows Defender/Platform (the highest numbered item defines the current antimalware platform version, as per Ways to check your current Defender Antimalware Platform Version)

    MS Posts Support Note About Defender SFC /Scannow Errors-image.png

    Checking for updates refreshes the Security Intelligence updates just fine, but the engine number stays unchanged. Thus, I have questions:

    1. Why do some of my Win10 1903 PCs run older Antimalware platforms?
    2. Is there any way I can find and force an install of the 4.18.1908 version?

    Alas, I can't seem to find a link on the MS site to do this. Looks like another case of waiting for MS to find the famous "round tuit" (get around to it, that is). Sigh.
    --Ed--
      My ComputersSystem Spec

  2. Farvatten's Avatar
    Posts : 157
    Windows 10 Pro 64bit 1903 18362.356
       #2

    EdTittel said: View Post
    According to this document, one needs version 4.18.1908 of the Antimalware platform to avoid this error.
    Great find Ed!

    I'm encouraged that MS has updated what had previously been it's open ended announcement:

    ...Windows Defender version 4.18.1906.3 and later versions.

    to this:

    ...Windows Defender version 4.18.1906.3 and later versions up to version 4.8.1908.


    Both my machines, like yours, are still on 4.18.1907.4-0. Unfortunately, I too have never found a way to force the latest Defender platform updates, instead having to wait, eventually my machines getting them within hours usually between 3 and 4 weeks of the last one.

    Again as always, thanks for having your ear so close to the ground on this one. ;o) .
      My ComputersSystem Spec

  3. EdTittel's Avatar
    Posts : 3,480
    Windows 10
    Thread Starter
       #3

    @Farvatten: you're welcome. Glad MS has finally acknowledged the well-known issue, and its equally well-known workaround. Now, if they would just issue that newer Antimalware platform, all would be well . . . Just for grins let me check the version on my Fast Ring Insider Preview PC: it's same release, so it hasn't made it into Preview circulation, even. Stay tuned.
    --Ed--
      My ComputersSystem Spec

  4. Crizal's Avatar
    Posts : 222
    Windows 10 Home 64bit
       #4

    Nice to get some new information on this. Many thanks @EdTittel for finding it. Earlier MS documents said a fix would be in "future releases of Windows". I just checked the Microsoft Update Catalog for KB4052623 which is the Antimalware Platform version and it's still showing 4.18.1907.4 which I'm also on. I guess we wait for Windows Update.
      My ComputerSystem Spec

  5. Farvatten's Avatar
    Posts : 157
    Windows 10 Pro 64bit 1903 18362.356
       #5

    @EdTittle

    I am curious about their wording however...

    It does not say the problem occurs only with Windows Defender version 4.18.1906.3 and later versions up to but not including version 4.8.1908. And reading the statement it says the problem of hash corruption is fixed 'After this update is applied...'

    Naturally pessimistic with any MS statements, I'm wondering if it will take another cycle AFTER this one to see the fix?

    Unfortunately from experience I've found I can be overly skeptical with these things, and yet often a good thing , being pleasantly surprised when my dire predictions come up short.
      My ComputersSystem Spec

  6. Bree's Avatar
    Posts : 12,449
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #6

    EdTittel said: View Post
    See this note for Microsoft's explanation of the Defender PowerShell script issue that leads SFC /scannow to return hash value mismatch errors for those files .... According to this document, one needs version 4.18.1908 of the Antimalware platform to avoid this error.
    I've seen that document many times before, but until now it had no 'Resolution' section. That must be a very new addition, the note at the bottom say "Last Updated: 17 Aug 2019". That date being a Saturday, I suspect we'll have to wait until the working week starts in Redmond before 4.18.1908 get put up on the update servers.
      My ComputersSystem Spec


  7. Pejole2165's Avatar
    Posts : 124
    Windows 10 1903
       #7

    And yet if you run SFC /scannow from an elevated command console it reports no error's yet Autoruns can see that certain defender files are unsigned. I assume that is the issue?
    MS Posts Support Note About Defender SFC /Scannow Errors-desk01.png
    MS Posts Support Note About Defender SFC /Scannow Errors-desk02.png
      My ComputerSystem Spec

  8. shockwaveriderz's Avatar
    Posts : 58
    Windows 10 Pro 1903 18362.267
       #8

    I'm at 18362.295 on my 3 PC's and they all have that 4.18.1908 folder and when sfc /scannow is run, there is no error conditions thrown up.
      My ComputersSystem Spec

  9. Compumind's Avatar
    Posts : 1,306
    Windows 10 Pro x64, Various Linux Builds, Internet Security Specialty.
       #9

    Very useful.

    Thanks, Ed!
      My ComputerSystem Spec


  10. Posts : 1
    windows 10
       #10

    Ηow did you get the release 4.18.1908 ?
      My ComputerSystem Spec


 
Page 1 of 3 123 LastLast

Related Threads
Solved sfc /scannow failing after this latest Defender Platfom update. in AntiVirus, Firewalls and System Security
Anyone else seeing this after last night's Defender Platform update that went from 4.18.1905.4-0 to 4.18.1906.3-0? I'm getting it on both my platforms. Both machines are on the latest 1903 207 build. Perhaps some Powershell Defender module...
Solved SFC /scannow - Defender corruption? in Performance & Maintenance
A run today of sfc /scannow reported errors, with this message:. "Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at...
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: - Could not reproject corrupted file...
Windows Defender Nag Note in AntiVirus, Firewalls and System Security
Every day I get this message: ..."Virus Protection is turned off. Tap or click to turn on Windows Defender Antivirus"... . When I click on the message, I get sent to the "Security at a Glance" page. Everything has Green check marks. Also...
Shawn posted this great article on how to put contact information in the "Windows Defender Security Center": Add Support Contact Information to Windows Defender Security Center But it mine seems to be broken: 180841 The email address and...
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:21.
Find Us