Windows 10: 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)





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--

:)

 

sfc /scannow error

Problem is not with windows update. It is with defender malware update.
Please do
DISM /Online /Cleanup-Image /AnalyzeComponentStore
DISM /Online /Cleanup-Image /StartComponentCleanup
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After above steps, reboot laptop and do sfc /scannow.

 

sfc /scannow errors


Important thing to remember is that the SFC / SCANNOW cannot always fix all errors at once. It is quite often required to run SFC /SCANNOW several times.

I have often had a situation that only a third, fourth or fifth run has finally reported "No more errors".

This is how it should be done:

• SFC / SCANNOW
• If SFC reports not all errors were fixed, reboot and run it again
• SFC / SCANNOW
• If SFC again reports not all errors were fixed, reboot and run it again
• And so on

Screenshot from the TenForums SFC tutorial:

 

SFC /SCANNOW Errors After Update


I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with Error: 0x800f081f "The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature."
4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."

Please advise:

1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?