This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
On Jan 24, 2023, W.U. downloaded and updated Windows security with this KB5007651 (Version 1.0.2301.24001).
After this update the security icon on the system tray showed a yellow warning triangle, and then the icon completely disappeared after a reboot.
No way to get the icon back on the System Tray. 🤷♂️
I can still open security if I search for it in settings, but there is no apparent reason for the shortcut on the system tray to be missing.
It looks like starting with Build 25272 the windows security updates are messed up and out of sync with the currently installed windows Build.
I could reproduce the same issue restoring a backup of Build 25281 and then going through W.U. checking for updates, the same scenario repeated again.
Right after the update shows yellow warning on security icon:
Everything green here, but Firewall & network protection is missing, that may be the reason for the yellow warning.
Missing Security icon from System Tray after a reboot:
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 2%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPO%3C/text%3E%3C/svg%3E)
>Check the update history on the 3 that did not have the issue and see if they ever got any kb5007651
No, I didn't find it any of those 3 devices.
>I upgraded a laptop from 19045.2546 to 25284.1000 and it did not get any of the KB5007651
I restore old 25227 and two updates W.U. find immediately was KB5007651 and build 25281.
>Here are 2 machines showing a different behavior, see the inconsistency and different details below.
On my case this happen only one out of four devices. Have you tried to restore some older dev build and update to 25284? I will test that later today to see which defender app version W.U. load with 25284.
>Is this another of their silly A/B tests?
Maybe they test next defender versions on random devices.
Yes, I restored 3 different backups, 2 out of 3 had the problem.
Check the update history on the 3 that did not have the issue and see if they ever got any kb5007651 previously. Since they list those together with all the defender updates, 50 total, you may not find any in the history.
They started downloading those kb5007651 back in July/August 2022.
1.0.2109.27002 (This was the old one for 21H2 back in Sept 2021)
The ones below were for 22H2.
1.0.2207.20002
1.0.2208.16003
1.0.2209.20001
1.0.2301.7001
1.0.2301.24001
I upgraded a laptop from 19045.2546 to 25284.1000 and it did not get any of the KB5007651 Security updates.
And, as I expected, this one shows just the 1000.25284.1000.0 for the Microsoft.SecHealthUI and not 1000.25285.1000.0 🤷♂️
Evidently 25285 security is compatible with Build 25284, but not with Build 25281.
The question is why did W.U. download and install it on build 25281 and create the bug that we experienced on Jan 24, 2023?
>Here are 2 machines showing a different behavior, see the inconsistency and different details below.
On my case this happen only one out of four devices. Have you tried to restore some older dev build and update to 25284? I will test that later today to see which defender app version W.U. load with 25284.
>Is this another of their silly A/B tests?
Maybe they test next defender versions on random devices.
Hi Pauli.
I don't understand the continuous inconsistency of MS Security update process.
Here are two machines both updated to Build 25284.1000 from previous Dev builds, yet the Security updates are quite different even though now the bug that we saw with 25281 is no longer happening. 😉
The Security Icon is now present on System tray and Firewall & network protection are no longer missing in either one of these 2 machines.
Here are 2 machines showing a different behavior, see the inconsistency and different details below.
I wish MS could explain what is causing the different Security update process.
Is this another of their silly A/B tests? 😎
DEV Build 25284 on machine B:
DEV Build 25284 on machine C:
Never got any one of those kb5007651 that were received on machine B. 🤷♂️🤷♂️
The result here is that the security application version is the one supplied directly by the 25284 upgrades.
There is no Windows Security Service Version update applied by kb5007651 which were never offered by W.U. on this second machine.
Both machines now show the same security dashboard, nothing missing. 👍
Build 25284 fix that issue. Defender icon is System tray and Firewall and network protection is back.
Yes, I just confirmed that.
Looks like those kb5007651 updates are out of sync with the windows build numbers.
We now are 25284.1000 but the Security version is 1000.25285.0.1000 and was downloaded while we were still at 25281, it does not make any sense. 🤷♂️
Why those kb5007651 updates on some machines and not others? Clearly something screwed up in the logic of those updates.
Edition Windows 11 Pro Insider Preview
Version 22H2
Installed on 1/25/2023
OS build 25284.1000
Experience Windows Feature Experience Pack 1000.25284.1000.0