I did exactly the same as you I think.
In your example..for me the when I ran the second sfc (used after the DISM repair) sfc found errors but said it had repaired them. Is that what you got too?
And when I ran sfc for the third time as you did I got the standard Windows Resource Protection did not find any integrity violations which meant that everything was repaired and fine again
Good day.
Yes. That's it.
The last sfc is just a safeguard to ensure there are no integrity violations.
Thanks for confirming that the results I saw are correct. I thought that the results I got at each step of the DISM/SFC repair were perfectly normal and what is expected to happen. I just wasn't 100% sure as Im not an expert on the internal workings of DISM and the System File Checker
Conclusively confirmed to myself that it's a Defender Update issue this morning: see the concluding note in my recent blog post. Recent Win10 Updates Bollix Defender Module Hashes - Windows Enterprise Desktop.
HTH,
--Ed--
Ed,
I agree with what you have written in your blog but I was surpised to see that you did not mention that the fault appears when a WD update takes you past
Antimalware client version 4.18.1905.4
because I think that would enable your readers to fully assess their own status & prospects.
All the best,
Denis
@sportsfan148:
I *know* it's something to do with Windows Defender. Haven't yet figured out if it's the Defender Updates or the Antimalware Platform Updates. How did you make this determination? Curious to understand, so please explain. Thanks!
--Ed--
Ed,
Nobody has reported running the updates in a manner that would distinguish between the two. I updated my platform by running the update from the WD UI and that, as normal, combined platform & definition updates.My platform version went from 4.18.1905.4 to 4.18.1906.3So I cannot distinguish between the two changes.
My definitions went from 1.297.653.0 to 1.297.830.0
- The only chance would be by installing KB4052623 Update for WD platform on its own by downloading it from the MS update catalog and nobody has posted a report of doing that.
- The update itself would have to be done offline in case KB4052623 initiated a definition update call.
- Even then the definition state would have to be checked before and after to make sure nothing had muddied the waters.
Denis
Quote
