sfc /scannow failing after this latest Defender Platfom update.

Crizal · 19 Jul 2019

sportsfan148 said:

f14tomcat said the repair in place repair rolled him back to Animalware version1906.03 and it had the errors too (He said the errors were there and he had to fix them). I could run the DISM fix on 1907.04 and it would repair it. The only reason I haven't done that is because it would only be a temporary fix as I saw when I fixed 1906.03 originally

Correct. You do have the option to just ignore the errors until MS resolves the issue as the errors don't seem to hurt anything. Unless, of course, you need to run sfc /scannow for some reason. Then you'd need to run the fix first.

sportsfan148 · 19 Jul 2019

Crizal said:

Correct. You do have the option to just ignore the errors until MS resolves the issue as the errors don't seem to hurt anything. Unless, of course, you need to run sfc /scannow for some reason. Then you'd need to run the fix first.

Exactly my thinking mate. I routinely run an sfc /scannow on a weekly basis before creating a system restore point. It looks like I'll have to hold off on that routine for a while..or alternatively, I could just fix the errors with DISM first

Crizal · 19 Jul 2019

sportsfan148 said:

Exactly my thinking mate. I routinely run an sfc /scannow on a weekly basis before creating a system restore point. It looks like I'll have to hold off on that routine for a while..or alternatively, I could just fix the errors with DISM first

Just as long as we don't have to run the fix every time a new Antimalware Client Version is released.

sportsfan148 · 19 Jul 2019

Crizal said:

Just as long as we don't have to run the fix every time a new Antimalware Client Version is released.

That thought has crossed my mind as well..and it could possibly be what ends up happening!!

Crizal · 19 Jul 2019

sportsfan148 said:

That thought has crossed my mind as well..and it could possibly be what ends up happening!!

Crizal · 26 Jul 2019

@sportsfan148 -- This morning, Windows Update installed Defender Antimalware Client Version 4.18.1907.4, the version you and several others received last week and was then pulled because of the sfc /scannow errors. It's also now on the Microsoft Update Catalog under KB4052623 with a July 25th release date. This re-release does not fix the sfc error issue, at least on my machine. DISM clears it up. Here we go again.

f14tomcat · 26 Jul 2019

Crizal said:

@sportsfan148 -- This morning, Windows Update installed Defender Antimalware Client Version 4.18.1907.04, the version you and several others received last week and was then pulled because of the sfc /scannow errors. It's also now on the Microsoft Update Catalog under KB4052623 with a July 25th release date. This re-release does not fix the sfc error issue, at least on my machine. DISM clears it up. Here we go again.

Just finished going thru all that, again...... I'm inclined to believe it doesn't really hurt anything, but it's ugly. And, if you intentionally want to do all the DISM cleanup to clean the component store, normal maintenance, the /Resetbase element will croak and throw up if there are SFC errors. So, benign, unless you try to clean. Then, not so benign.

Crizal · 26 Jul 2019

f14tomcat said:

Just finished going thru all that, again...... I'm inclined to believe it doesn't really hurt anything, but it's ugly. And, if you intentionally want to do all the DISM cleanup to clean the component store, normal maintenance, the /Resetbase element will croak and throw up if there are SFC errors. So, benign, unless you try to clean. Then, not so benign.

Totally agree with you.

Farvatten · 26 Jul 2019

It's worth noting that you need to be connected during the Dism /Online /Cleanup-Image /RestoreHealth phase of this cleanup.

Bree said:

One of my machines has just got the 4.18.1907.4 platform through windows update and, as expected, SFC reports defender powershell errors.

Running Dism /Online /Cleanup-Image /RestoreHealth while disconnected from the internet reports 'The source files could not be found' so yes, internet connection is required. Attached are the logs, I have only run DISM while disconnected, I've not yet connected and run DISM to perform the repairs.

Discussion found at the end here:

Many unrepairable corrupted Defender files found by sfc /scannow

Crizal · 26 Jul 2019

@Farvatten -- thanks for the link. I've been reading that thread and its included links. Worthwhile to repeat here -- Microsoft admits the problem but indicates it will continue until a future Windows release. Try3 provided this link: https://support.microsoft.com/en-us/...s-as-corrupted No one should expect a quick fix.