sfc /scannow failing after this latest Defender Platfom update.

Try3 · 12 Jul 2019

KRZ,

I am not quite sure from your responses whether or not SFC now succeeds on your computer.

My SFC kept failing despite using the suggestions that others had made but has just succeeeded on all three of my computers by using Bastet's variant method -

1 Restart the computer
2 SFC /ScanNow
[no further reboots/restarts - just continue in the same session]
3 dism.exe /Online /Cleanup-image /Restorehealth
[no further reboots/restarts - just continue in the same session]
4 SFC /ScanNow [This fixes the failures & further, unnecessary, SFC runs just report no problems]

Denis

krzemien · 12 Jul 2019

Yeah, my enquiry was more general: why (if) should I run it in the first place?

SFC and/or DISM in fix mode generates a lot of unnecessary junk under C:\Windows\WinSxS\Temp (which ultimately gets deleted with the maintenance run or similar) - hence my reluctance to run them in the first place. That's all.

Farvatten · 12 Jul 2019

Try3 said:

Bastet's variant method -

1 Restart the computer
2 SFC /ScanNow
[no further reboots/restarts - just continue in the same session]
3 dism.exe /Online /Cleanup-image /Restorehealth
[no further reboots/restarts - just continue in the same session]
4 SFC /ScanNow [This fixes the failures & further, unnecessary, SFC runs just report no problems]

This is consistent with my early successes having restarts before and after CU KB4507453 18362.239

Machine 1:

- no restart

sfc /scannow
dism /Online /Cleanup-image /Restorehealth
sfc /scannow

- restart ( after CU .239 )

Machine 2:

sfc /scannow
- restart ( after CU .239 )

sfc /scannow
dism /Online /Cleanup-image /Restorehealth
sfc /scannow

Farvatten · 17 Jul 2019

catspyjamas said:

https://support.microsoft.com/en-us/...s-as-corrupted

MS have acknowledged the issue and advise just ignoring it. Looks like they will fix it in "future releases of Windows".

I'm marking this solved

krzemien · 17 Jul 2019

Still:

This is a known issue

and

you can safely ignore the SFC error messages

have both nice ring to it...

(I have moved to 1903 myself last weekend and fixed it on the go as well nevertheless)

EdTittel · 17 Jul 2019

Just FYI, I've seen it on 1903 (18362.239), 19H2 Insider Preview (18362.1005), and 20H1 Insider Preview (18936.1000) on all such machines running Windows Defender. I'm in the same camp as the Bleeping Computer person, who speculates that recent Windows Defender updates are the culprits. So I said in one of my blog posts for today, in fact: Recent Win10 Updates Bollix Defender Module Hashes - Windows Enterprise Desktop.
HTH,
--Ed--

Compumind · 17 Jul 2019

EdTittel said:

Recent Win10 Updates Bollix Defender Module Hashes - Windows Enterprise Desktop

Perfect! Thanks.

Try3 · 17 Jul 2019

Ed,

About "speculates that recent Windows Defender updates are the culprits" - they were definitely the culprits.

I had run SFC successfully then updated just WD [from 4.18.1905.4 to 4.18.1906.3] then ran SFC again and the fault was present.

See also SFC incorrectly flags WD PowerShell module files as corrupted - MSSupport

Denis

sportsfan148 · 18 Jul 2019

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 · 18 Jul 2019

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