New
#11
Hi,
Personally I don't keep track if it were up to me defender would not be there at all
I just do what others have done and fixed the sfc errors and that's all I can do ms will likely screw it up again sooner or later
According to a response to this article (at the bottom), 4.18.1908 has so far only been released to the Insider Fast Ring. Also, article claims even with the new antimalware platform, some DISM commands are still needed. Guess we'll be finding out eventually.
Microsoft Fixes Corrupted Windows Defender Files When Using SFC
Last edited by Crizal; 25 Aug 2019 at 11:15.
Does MS run sfc /scannow before releasing a major update to find such errors? I guess not.
I've got the 4.18.1908 on my fast ring PCs now, but it didn't show up until 8/24. Does indeed do away with the spurious SFC error routine. Question remains: when will this go into wider distribution, like 1903?
Who knows?
--Ed--
Several computers with the hash mismatch were recently fixed running restorehealth before a repeat scannow:
Code:1) Open administrative command prompt and type or copy and paste: 2) sfc /scannow 3) dism /online /cleanup-image /scanhealth 4) dism /online /cleanup-image /restorehealth 5) sfc /scannow
Hello all. According to this German blog (Google translation), the long-awaited Defender Antimalware Client Version 4.18.1908.7 which cures the sfc /scannow errors, has been released. As of this writing, I'm not finding it on Windows Update or the Microsoft Update Catalog (kb4052623). Patience needed I presume.
Google Translate
EDIT: Received new antimalware version 4.18.1908.7 on September 16th. Ran sfc /scannow, no integrity violations.
Last edited by Crizal; 16 Sep 2019 at 13:55.
Looks like I've got the new version across the board now, too. This little snippet of command line juju (must run in cmd.exe), does the trick:
HTH,
--Ed--
Does NOT apply to Windows 10 Enterprise, though: completely different versioning there (never had the sfc /scannow issue there, either). Just FYI.