New Defender Antimalware Client Version

sportsfan148 said:

Windows Update has just downloaded the new Antimalware update. I checked Defender settings and it has been updated. So straight away I ran sfc /verifyonly. CBS log errors again! Ive looked at them and they are the same Windows Defender Powershell issues as before. I didn't reboot my PC before running sfc /verifyonly. Also, in my case I hadn't fixed the errors previously. I have just waited for Microsoft to release this antimalware update fix. I wonder if either of these things might be the problem? Should I have used DISM to fix the problem before the Antimalware engine got updated to this new version?

f14tomcat said:

Probably....yes. I doubt an update to the platform would fix any existing goofs. I had run an SFC prior and after, and both were clean.

I agree with @f14tomcat. After the previous Antimalware update, I did the sfc /scannow and DISM stuff (which corrected integrity violations). Before getting the new update, I repeated sfc /scannow and DISM and everything was fine. After installation of new update, I repeated sfc /scannow and DISM and all remained good. You probably read the following link to MS on this issue and the new update is not supposed to flag the files that gave SFC issues.

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

f14tomcat said:

Probably....yes. I doubt an update to the platform would fix any existing goofs. I had run an SFC prior and after, and both were clean.

Thanks...I'll fix it with DISM. Hopefully then there will be no further issues with the Windows Defender Powershell hash mismatches again

- - - Updated - - -

Crizal said:

I agree with @f14tomcat. After the previous Antimalware update, I did the sfc /scannow and DISM stuff (which corrected integrity violations). Before getting the new update, I repeated sfc /scannow and DISM and everything was fine. After installation of new update, I repeated sfc /scannow and DISM and all remained good. You probably read the following link to MS on this issue and the new update is not supposed to flag the files that gave SFC issues.

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

Yeah..my understanding was that Microsoft were saying there was no need to do anything and there would be a fix coming through an antimalware update. That's why I didn't do a DISM, SFC. I just left it alone

sportsfan148 said:

Thanks...I'll fix it with DISM. Hopefully then there will be no further issues with the Windows Defender Powershell hash mismatches again

- - - Updated - - -



Yeah..my understanding was that Microsoft were saying there was no need to do anything and there would be a fix coming through an antimalware update. That's why I didn't do a DISM, SFC. I just left it alone

You raise a very valid point. The MS document states the files creating the SFC issue are not flagged after the new update is installed. Therefore, even if one did not run DISM, SFC should not show integrity violations after the update went in. On the other hand, the way MS wrote the document, they refer to DISM after explaining the resolution. Kind of ambiguous and confusing because that could lead some to think they need to run DISM after installing the update. Now, if that's the case, then the next antimalware update should not have any issues with SFC. Fingers crossed.

Drako9 said:

i tried the first 3 before

as for the suggested, i couldnt find the "periodic scanning"
also i dont use any other antivirus
and as for kb2267602, that one i managed to install for some reason
its just the kb4052623 that wont go

EDIT: I GIVE UP, i just dont undestand how the heck windows work, after restarting my computer for like the 17th time, it just said it didnt had any new updates, and my windows defender is already at "Versão do Cliente Antimalware: 4.18.1908.7" wtf

i am happy but wtf windows, at last try to explain me how you work

also thx alot Crizal for trying to help me

Hi there.
I am responsible for three Windows Server installations. Two Server 2016 and one 2019. On all three this new Win Defender 4.18.1908.7 refuse to install. On Win 10 client, no problems, but on Servers - NO!

<< Installation Failure: Windows failed to install the following update with error 0x80070643: Update for Windows Defender Antivirus antimalware platform - KB4052623 (Version 4.18.1908.7). >>

No third party antivirus and previous defender updates located in "new" path C:\ProgramData\... have worked.
It seems like the directory C:\ProgramData\Microsoft\Windows Defender\platform\4.18.1908.7-0\ is created with the wrong permissions. Any clues anybody?

f14tomcat said:

I caught that MS double-speak, also. Guess it's open to interpretation, but my take on it is "not flagged" by this platform update means "we won't break things with this one, sorry. We promise not to touch those components again.". Never explicitly said "And we cleaned up the mess we made.". So, still think that if SFC /scannow is showing the errors after the update, just fix it with the DISM Broom, and all will be fine going forward.

Absolutely correct. Interpretation is the key because I read "not flagged" as meaning the files would be "ignored". Nothing said about files being repaired by the update. The user has to do that with DISM. And yes, after fixing, the issue should be resolved.

Try3 said:

If that was from trying to install the KB update note that you can also get the update simply by using the update facility within WD - when you tell it to update definitions it will also update the WD version if a new one if available.

Denis

Thanks but that give the exact same error. Definitions installations is no problem though - not other updates either so it is something special with this update not working on Servers.