sfc /scannow failing after this latest Defender Platfom update.

f14tomcat · 18 Jul 2019

sportsfan148 said:

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

Try3 said:

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

Same errors as before. The Powershell v1 Defender components. Still on .1906 Def Platform on my main 1903, but when I went to update my Slow Ring this morning for the .10006, I got the .1907 and a corrupted component store as before. Sfc/Dism/Sfc.... all fixed.

Least it's consistent with the fix. A PITA, though. Since the general opinion is the hash mismatches don't really hurt anything, next time I'll just leave it alone. Then I'll be with the other 800 million or 1 billion or whatever the number is now.

krzemien · 18 Jul 2019

Still very sloppy, to say the least.

Especially that hash mismatches - and with such key components like AV protection which forms part of an OS either (whether we like it or not) - really should not be swept under the carpet that lightly.

But what do I know.

EdTittel · 18 Jul 2019

Just reconfirmed that a new Defender Update (1.237.1331.0) caused the file corruption error in SFC /SCANNOW on my Insider Preview 19H2 Slow Ring Surface Pro 3. Only update applied was the Defender stuff and BAM! the error was back, and the same fix still worked. Get it together, MS, please! Updated my blog post accordingly (see concluding note): Recent Win10 Updates Bollix Defender Module Hashes - Windows Enterprise Desktop
--Ed--

sportsfan148 · 18 Jul 2019

Try3 said:

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

Im on Antimalware Client Version: 4.18.1907.4 now. My PC remained fixed too until windows update pushed this update yesterday. The errors that cant be repaired are exactly the same ones as we got before which came with the 4.18.1906.3 version you're on now. I don't know whether to fix it again or wait for Microsoft to do it. I thinks its the antimalware platform updates that are causing it not the Windows Defender definitions
Rick

f14tomcat · 18 Jul 2019

sportsfan148 said:

Im on Antimalware Client Version: 4.18.1907.4 now. My PC remained fixed too until windows update pushed this update yesterday. The errors that cant be repaired are exactly the same ones as we got before which came with the 4.18.1906.3 version you're on now. I don't know whether to fix it again or wait for Microsoft to do it. I thinks its the antimalware platform updates that are causing it not the Windows Defender definitions
Rick

You are correct, Rick. Bad hashes. MS says it doesn't affect the day-to-day running, so it's on a priority somewhat less than rewriting IE.

sportsfan148 · 19 Jul 2019

f14tomcat said:

You are correct, Rick. Bad hashes. MS says it doesn't affect the day-to-day running, so it's on a priority somewhat less than rewriting IE.

It'll come as a shock to many who don't know much about sfc scans and currently don't have a clue that the issue even exists. Most people seem to be blissfully unaware of it. And it'll cause a lot of confusion too if they suspect they have some other issue with their PC and are running an sfc scan to investigate. It doesn't sound as if they're going to be in too much of a rush to get this fixed

Crizal · 19 Jul 2019

sportsfan148 said:

Im on Antimalware Client Version: 4.18.1907.4 now. My PC remained fixed too until windows update pushed this update yesterday. The errors that cant be repaired are exactly the same ones as we got before which came with the 4.18.1906.3 version you're on now. I don't know whether to fix it again or wait for Microsoft to do it. I thinks its the antimalware platform updates that are causing it not the Windows Defender definitions
Rick

@sportsfan148 -- You were updated to Antimalware Client Version 4.18.1907.4 two days ago via Windows Update. I am still on version 4.18.1906.3 and WU is not finding the newer one. And, I checked the Microsoft Update Catalog for kb4052623, which is the Antimalware Client Version and the one showing there is the older one which I have. I don't want to speculate but I'm wondering if MS may have pulled the newer version …

sportsfan148 · 19 Jul 2019

Crizal said:

@sportsfan148 -- You were updated to Antimalware Client Version 4.18.1907.4 two days ago via Windows Update. I am still on version 4.18.1906.3 and WU is not finding the newer one. And, I checked the Microsoft Update Catalog for kb4052623, which is the Antimalware Client Version and the one showing there is the older one which I have. I don't want to speculate but I'm wondering if MS may have pulled the newer version …

it sounds as if that's possible if you're not seeing it

Crizal · 19 Jul 2019

sportsfan148 said:

it sounds as if that's possible if you're not seeing it

Thanks for responding. I just checked WU again, no updated Antimalware Client. MS Update Catalog still showing older version. At least Defender is updating definitions. Sure wish MS would sort out the sfc /scannow issue.

sportsfan148 · 19 Jul 2019

Crizal said:

Thanks for responding. I just checked WU again, no updated Antimalware Client. MS Update Catalog still showing older version. At least Defender is updating definitions. Sure wish MS would sort out the sfc /scannow issue.

Im getting definitions OK too. This time I haven't fixed the errors as yet after being updated to Antimalware Client Version 4.18.1907.4 two days ago. Did you get the errors too when Windows Update pushed 4.18.1906.3 onto your PC?