New
#21
I think that what has been posted so far indicates that both Josey & TC
1 happen to have Windows faults at the same time [which would be a bit of a coincidence], or
2 are both Insiders & there is a bug with their current build, or
3 are both served by the same MS server and it is that which has a fault.
As a further test or, with luck, a workaround I suggest running WD updates based on its MpCmdRun component until the fault is fixed.
WDUpdate.bat
NotesCode:set GetLatestVersionPath="dir "C:\ProgramData\Microsoft\Windows Defender\Platform" /ad /od /b" FOR /F "tokens=*" %%i IN (' %GetLatestVersionPath% ') Do Set LatestVersionPath=%%i "C:\ProgramData\Microsoft\Windows Defender\Platform\%LatestVersionPath%\MpCmdRun.exe" -SignatureUpdate
:: It searches for the latest subfolder [i.e. the latest version] in %ProgramData%\Microsoft\Windows Defender\Platform
:: It processes all subfolders in sequence so that last one to be set is the latest one
If that does not work then I suggest using the links I posted to the full WD definitions file. If you are able to download that then it would only fail to update if WD has such a serious bug that it was completely incapable of updating.
Denis