Build 25281, Windows Security Icon/Shortcut missing from System Tray after KB5007651 Platform update Version 1.0.2301.24001.

Anonymous
2023-01-25T04:29:38+00:00

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:

Windows Insider program | Windows Insider preview | Security, privacy, and accounts

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.

0 comments

77 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-28T04:32:21+00:00

    I didn't have this problem before.

    I restored 25267 last backup from 1/11/23 to check Safe Mode and now I'm facing the same issue. 🤷‍♂️

    I don't have KB5007651 installed or at least doesn't show in Update history.

    Image

    Image

    @Sibro.o,

    I had also one case where it did not show on install history, but it was installed as soon as I went online.

    This is the same mistake that MS made last year with 21H2 and 22H2, they were downloading security updates incompatible with the Windows Build currently on the machine. Pauli O has a machine that shows KB5007651 updates from 2109 all the way up to 2301.24001.

    The old ones are not in the History also because they go together with all the defender updates, and they only keep the history for the last 50. But I got also a case last week with 2301 that did not show in the history, yet it was installed.

    If I remove them, the latest one gets reinstalled as soon as I check for updates.

    Yet I have a third 25284 machine that never got any KB5007651 and that folder has only the ones installed by the 25248 upgrades.

    I checked for updates several times and never got any of those KB5007651 at all.

    Could not figure out why the different behavior. May be another A/B testing B.S. who knows?

    Looks like the Security guys never read the FBH reports. 🤐🤐🤷‍♂️

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-01-25T06:24:56+00:00

    @Sibro.o,

    Removing the 2 folders added by updates kb5007651 and deleting the SecurityHealthSetup.exe, will leave only the stuff installed by Build 25281.

    Double click on the first .appx reinstalls the correct version for 25281 and solves the problems.

    Image

    Edit:

    After cleaning up and reinstalling the correct version.

    Unfortunately, the update gets downloaded and installed again, and I don't know how to prevent that. 🤷‍♂️

    Image

    Image

    Image

    Firewall & network protection is back:

    The update gets reinstalled, and we are back with the bug. 🤬🤬

    Image

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-01-25T06:23:23+00:00

    This VM is a clean install of 25281

    So bottom line is only builds that have been updated are affected correct?

    Not necessarily, I have one without the problem and it was updated to 25281 from previous builds, but never got any of these kb5007651 (1.0.2301.xxxxx) security updates.

    I have no idea why I got the updates on 2 machines, but not the third one. It does not make any sense. 🤷‍♂️

    I went through the same silly issues with 22621 and 22623 back in Sept/Oct 2022.

    Now they are screwing up the Dev Builds too.

    Could be some other A/B testing inconsistency. 🤷‍♂️

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-01-25T06:02:07+00:00

    Hi Sibro,

    That 25281 is also what I get on one of my machines and that is fine.

    The problems started on the ones that had kb5007651 installed previously starting with Build 25272. CK had the same issues.

    Image

    See the dates of the update 1.0.2301.7001-0 and the second today, version 1.0.2301.24001-0.

    Those are the ones that mess everything up. They are not just antimalware platforms they also update the Microsoft.SecHelthUI.

    The 1st one was for version 25276, the second one id for 25285.

    They should not be downloaded on 25281.

    They made the same mess before, months ago, with 22621 Builds. 🤣😜🤷‍♂️

    If I delete the extra stuff in SecurityHealth folder and reinstall the version 25281 the problems go away.

    Image

    See here what that update installs, 1000.25285.1000.0. 🤣🤣🤷‍♂️

    Image

    One machine without those kb5007651 updates gets 1000.25281.1000.0 and no issues.

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-01-25T05:24:48+00:00

    The problem started back with Build 25272 when it updated security with KB5007651 (Version 1.0.2301.7001) which changed the security version to 25276.

    Now KB5007651 (Version 1.0.2301.24001) is bringing the security version to 25285 and clearly it is no longer compatible with Windows Build 25281.

    It is the same mess that they created months ago with Build 22621.

    https://aka.ms/AAjcnfy

    Same issue on a second machine after this KB5007651 (Version 1.0.2301.24001). 😜🤷‍♂️

    Image

    Was this answer helpful?

    0 comments