System File Check, Defender and Windows 10 1903

Microsoft is rolling out an update to fix Windows 10 SFC feature
August 18, 2019
https://www.windowslatest.com/2019/...-out-an-update-to-fix-windows-10-sfc-feature/

 

Yes, it doesn't stay repaired. Latest:

Spoiler: sfc1

dism hangs at 100% for a couple of minutes then says it completed successfully. Repeat sfc says it successfully repaired some files. Here is the "corruption" noted in the CBS log at C:\Windows\Logs\CBS

Spoiler: cbs log

So, I need that update.

 

So it is others besides me who have this problem. It was driving me crazy, nothing seemed to work to repair it. I also came to the conclusion that it had something to do with defender, but the inability to repair also comes up after "cleaning", even with Windows own program.
It also came up after reverting to a good backup, a backup that was checked before it was saved so i knew it was 100% ok.

This goes deeper than the obvious.

First Sandbox problems with related app guard problems, and now this. I think they are related in some way and that MS has done it again, released something to soon that they have not tested enough. It is incredible how they can shot themselfs in the foot, year after year, over and over. Dont the learn ANYTHING from their mistakes.

Now i am off to test the 3 DISM`s. Before i only did one.

 

OK, so it's the same client version as yours, stapp. Yeesh, I couldn't divine how to get that version #, most online tips are for older Windows 10. I also had to click the three bars at the top left of the "Security at a glance" screen, which then opens a sub-screen with the Settings at the bottom left. Microsoft is making Windows Security a bit convoluted ,as usual.

 

Same, almost. I got 2312.0 in the 2 last. Windows version is .239.

 

Triple DISM and sfc fixed it, it also updated automaticly to Windows version .295. I could not even do it manually before. I could even clean without problems.

This was a VERY good and helpful thread.

 

Here's what I did.

1. Turn on WD periodic scanning since I use third party AV.
2. Forced a definition update.
3. Ran DISM /Online /Cleanup-Image /RestoreHealth. After it reached 100% sat there for quite a while before successfully completing.
4. Turn off WD periodic scanning.
5. Ran sfc /scannow. It stated it found corrupt files and successfully repaired them.

So it appears SFC is again working properly. I guess I will have to see what files were repaired. Hopefully, just WD crap.

-EDIT- Yes. Files appear to be all WD Powershell related. Also, really don't know if the DISM bit is required:

 

Just a question here about DISM in some comments above ... surely it is not necessary to run a 'triple' DISM?

I thought ScanHealth 'includes' CleckHealth, and RestoreHealth would include ScanHealth? Each takes longer of course.

So just necessary to run RestoreHealth?

 

I probably ran it like 5 times in my life, never had problems, never really found it useful to me. Restoring a clean uncorrupted backup is way faster.

 

But does not fix the problem. I did that, and when checking that 100% fully ok image with sfc after restoration, it showed to be corrupt. W.defender and/or W.updates corrupts it, very fast.

 

For me, restore health and sfc did not fix it. Triple DISM and then sfc did.

 

As per sig I have four Win10 v1903 build 18362.295 instances on 3 machines (two recently clean installed on one laptop). All had sfc/ scannow corrupt files!

Only one instance is WD only (just clean installed), all others have 3rd party AVs (EAM x 2, 360 Total Security on old netbook).

Windows Update in every case up to date.

On the WD only instance, sfc /scannow could not fix the error, but after a DISM RestoreHealth, sfc was clean.

On all other instances, sfc either fixed the problem or a DISM RestoreHealth was required, after which sfc was clean (also with repeat tests).
(I must add that there have been quite a few occasions where I have had to perform one or both fixes over the years ).

Hopefully stays that way, for now! Didn't bother to look at CBS logs.

Edit: Subsequently temporarily set WD Periodic Scanning to On on 3rd party AV instances and checked for updates.
Apart from Security Intelligence updates (KB2267602), WD AV Anti-Malware Platform update KB4052623 on one (3rd party AV) instance only (so far) to v4.18.1907.4.

 

No. It applies to everyone that runs SFC and wishes it to show the correct completion status.

If this fix is not applied, SFC will always show it couldn't repair some files.

 

Well, sfc is good today..

Spoiler: sfc

Yes, that's the same client version I have now, paulderdash. Haven't rec. any relevant update yet, but according to post 28, it should be rolled out very shortly, right? Also, the article implies that it's not really corruption, but a hash mismatch. The thing is, if I'm running Windows Defender and not aware of this non-issue, I might be inclined to take action when none is needed, like a reset.

 

After having run the DISM commands when this thread started I get the errors again at this point. I'm also still not getting the Defender update on the PC that is using it. I guess I'll wait out the update and see.