sfc /scannow failing after this latest Defender Platfom update.

sportsfan148 said:

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?

Yes, I did get the errors when I got Antimalware Client Version 4.18.1906.3. I did the sfc/dism/sfc thing with a final sfc showing no problems. That worked. From what I've been reading, it appears the errors come back with the newer Antimalware version. Like I said earlier, maybe they pulled it because I can't find it on WU or the Update Catalog. I checked with 5 other people and they're still on the version I'm on and they can't find the newer one either. Oh well -- guess we'll have to wait and see.

f14tomcat said:

Here's one to throw in the pot. This morning, I did an in-place repair 1903. Prior to, it was .1907. After, it's .1906. Still had the SFC errors and did the usual sfc/dism/sfc to clear up. Still on .1906.

Sure looking more and more like 1907 was pulled -- unless it shows up again on your system without it being in the Update Catalog. Never a dull moment with MS.

Crizal said:

Sure looking more and more like 1907 was pulled -- unless it shows up again on your system without it being in the Update Catalog. Never a dull moment with MS.

If its been pulled. What are users like myself supposed to do who had it pushed onto their PC's two days ago?

sportsfan148 said:

If its been pulled. What are users like myself supposed to do who had it pushed onto their PC's two days ago?

I suspect you can either wait it out and see if MS releases some type of fix for the sfc /scannow issue, or, if they release a corrected Antimalware version -- or -- do an in-place 1903 repair like f14tomcat did. I'd be inclined to wait since MS says Defender works properly despite the sfc /scannow issue.

Try3 said:

You could RevertPlatform - look under the heading How to roll back this update in KB4052623 Update for WD platform
- You need to check the path of your latest version

Code:

"%programdata%\microsoft\windows defender\platform\<version>\mpcmdrun.exe" -revertplatform

which I think means for you, from what you have written,

Code:

"%programdata%\microsoft\windows defender\platform\4.18.1901.7-0\mpcmdrun.exe" -revertplatform

but I have never run this procedure myself and have never seen any threads in which people have referred to having done so.

Or you could just ignore the problem.

Denis

Hi Denis. I wouldn't want to run the risk of totally messing up my PC.. Ive only clean installed to Windows 10 1903 recently.

Crizal said:

I suspect you can either wait it out and see if MS releases some type of fix for the sfc /scannow issue, or, if they release a corrected Antimalware version -- or -- do an in-place 1903 repair like f14tomcat did. I'd be inclined to wait since MS says Defender works properly despite the sfc /scannow issue.

Im hoping not to have to do an in place 1903 repair

sportsfan148 said:

Im hoping not to have to do an in place 1903 repair

Understandable given you recently did a clean install. I'd sit tight and see if MS issues a fix.

Crizal said:

Understandable given you recently did a clean install. I'd sit tight and see if MS issues a fix.

f14tomcat said the in place repair rolled him back to Antimalware version1906.03 and the errors were still there (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. So like you said it looks like the best option is to wait for a fix from Microsoft as they have already said that Windows Defender works perfectly despite the sfc /scannow issue.