Microsoft Defender Anti-Malware/Platform Update Kit for Windows 10 (Updated: July 9th, 2021)

... absolutely

 

It would be nice if you could mention the original links / sources in OP, how are you authoring these cabs and if it can be automated via a diy script.
The integration script can be provided right at OP in a code block and/or attached as zip for more transparency.
And using google drive links is less accessible and more volatile than for example a github, but still better than mediafire & co

People are naturally circumspect (or at least they should be) when it comes to stuff touching the core defense mechanisms of windows.
And because I and probably others don't feel like checking each file for having a valid digital signature,
I present a 3rd-party verify script:

Code:

@(set `" <#=")& echo off & title Defender Update Kit Verification Tool v1.2
set "0=%~f0"&set 1=%*& powershell -nop -c iex ([io.file]::ReadAllText($env:0)) &exit/b || #>)

$messages = @{
  WARN_DEFENDER_CABS_MISSING  = " Place this script in the same folder as Defender Update cabs ";
  WARN_DIGITAL_SIGNATURES_ER  = " Digital Signatures ERROR! ";
  WARN_DIGITAL_SIGNATURES_OK  = " Digital Signatures OK! "
}

cd -Lit(split-path $env:0)
$x86   = gci defender-dism-x86*.cab   | sort creationtime | select-object -last 1
$x64   = gci defender-dism-x64*.cab   | sort creationtime | select-object -last 1
$arm64 = gci defender-dism-arm64*.cab | sort creationtime | select-object -last 1

if ($null -eq $x86 -and $null -eq $x64 -and $null -eq $arm64) {
  write-host -fore black -back yellow $messages.WARN_DEFENDER_CABS_MISSING; choice /c EX1T; exit 1
}

$root = "defender-dism";  ri $root -recurse -force -ea 0|out-null; ni $root -item directory -force -ea 0|out-null
if ($x86) {ni "$root\x86"   -item directory -force -ea 0|out-null; expand -R $x86.Name -F:* "$root\x86"}
if ($x64) {ni "$root\x64"   -item directory -force -ea 0|out-null; expand -R $x64.Name -F:* "$root\x64"}
if ($arm) {ni "$root\arm64" -item directory -force -ea 0|out-null; expand -R $arm64.Name -F:* "$root\arm64"}

$invalid = @()
gci $root\*.* -exclude *.json,*.mof,*.txt,*.xml -file -recurse | foreach-object {
  $sig = Get-AuthenticodeSignature $_
  if ($sig.status -eq 0) {write-output $sig} else {$invalid += $_ | select-object LastWriteTime,Length,FullName}
}
write-host
if ($invalid.length -eq 0) {
  write-host -fore yellow -back darkgreen $messages.WARN_DIGITAL_SIGNATURES_OK
} else {
  write-host -fore yellow -back darkred $messages.WARN_DIGITAL_SIGNATURES_ER
  write-output $invalid
  write-host -fore yellow -back darkred $messages.WARN_DIGITAL_SIGNATURES_ER
}
write-host
choice /c EX1T
#,# AveYo and steven4554

Save as defender_update_kit_verify.bat in the same folder as Defender Update Kit cabs
It will extract cabs in a defender-dism folder, then run Get-AuthenticodeSignature powershell cmdlet on all sensitive files.
Hope it helps someone.

[update] 2021.05.12: arm64 support from steven4554; show details for files failing verification

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I re-installed enterprise twice and pro once more and it never showed up again

 

I am glad i made a screenshot, else nobody would have believed me i regret not using wumt to be able to fetch you the ddl

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

When it is updated, it is always better to look for it on MS sites and not elsewhere

 

And those are certainly just these two pages

 

MS pages, not packing and repacking