Is not that a definitions update? it's difficult to keep up with Defender / Security updates, it's constant
No that's what I assume is the latest version of the Windows Security Center. But I agree it is constantly updating week by week.
The point is that I integrated the latest .cab Released: April 17th, 2025 Next Update: April 25th, 2025 Defender: 5.4.2504.3 Engine: 1.1.25030.1 Platform: 4.18.25030.2 Version: 1.427.305.0 And after that, these three updates are showing: Windows Malicious Software Removal Tool x64 - v5.132 (KB890830) Update for Windows Security platform - KB5007651 (Version 10.0.27777.1008) Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.427.312.0) - Current Channel (Broad)
Integration doesn't stop regular required updates. Intelligence updates are the logic for catching virus's, they are constantly updated with new threats. Malicious software removal tool is a scanner that when updated will scan on install, gets updated every few months or so.
Nevermind, just saw that 1.427.312.0 > 1.427.305.0 My fault, I wasn't reading versions right (lack of sleep maybe). I thought it was just the opposite scenario. For the KB5007651 I think the easiest way will be to force update during first boot, as I don't know how to integrate the MUI part of it.
Why do you even use MRT, it is pointless. Code: reg add "HKLM\Software\Policies\Microsoft\MRT" /v "DontOfferThroughWUAU" /t REG_DWORD /d "1" /f
Nah, that policy will be detected by some security tools as tampering; it's easier to run it with a /q from SetupComplete.cmd and call it a day. Now I've got the problem with (KB5007651) securityhealthsetup_*.exe, executes and "installs" (or at least, exits without error) but when you open "Windows Security", version is still the old one. ...just copies itself to System32\SecurityHealth, with SYSTEM permissions but doesn't get installed. Tried both using unattend.xml and SetupComplete.cmd, no luck.
I run them using SYSTEM privileges, via SetupComplete.cmd in first place, on a second run I tried to run it via unattend.xml Looks like that installer (securityhealthsetup*) doesn't love OOBE env. (However MRT installs without problems that way)