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 No comments

77 answers

Sort by: Newest
  1. Anonymous
    2023-01-28T19:03:20+00:00

    Anyway, you show that you already had the problem on 1/11/2023 with Build 25267, which shows security version 1000.25276.0.1000 🤐

    Upvote Pauli's FBH report and add your comments.

    Good observation, I didn't notice that before. I upvoted and commented yesterday.

    I deleted the folders and reinstall 25267 without network and updates paused, everything was fine until I went online and deja vu all over again, still updates paused. 😒

    This backup is not good to me anymore, going to RP for the time being until they fix the resolution bug at which point I will start a fresh Dev build.

    Thanks!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-01-28T18:38:19+00:00

    Are you saying that both the 7001 and 24001 are coming is as soon as you connect to the internet.

    I thought you had the updates suspended?

    Hi fg,

    I was wrong, on a newly restored 25267 I have 7001 & KB5007651 from 1/11/23, this is with network disconnected and updates paused.

    A few minutes later with network connection, 24001 shows up even with updates paused.

    Notice the new KB5007651 doesn't show in history yet and icon with yellow mark.

    Another difference with what I see, I don't get 24001 while updates are suspended, only after I resume. 🤷‍♂️

    Anyway, you show that you already had the problem on 1/11/2023 with Build 25267, which shows security version 1000.25276.0.1000 🤐

    Still unclear how MS picked your machine and many other ones to install those KB5007651 updates.

    One of my Dev boxes is never getting any of those KB5007651, but the different behavior is still a mystery. 🤬

    Upvote Pauli's FBH report and add your comments.

    The whole logic of these updates is screwed up. They are repeating the same fiasco they had last year with 21H2 and 22H2 Builds. 🤷‍♂️

    https://aka.ms/AAjdwnc

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-01-28T17:46:23+00:00

    Are you saying that both the 7001 and 24001 are coming is as soon as you connect to the internet.

    I thought you had the updates suspended?

    Hi fg,

    I was wrong, on a newly restored 25267 I have 7001 & KB5007651 from 1/11/23, this is with network disconnected and updates paused.

    Image

    Image

    A few minutes later with network connection, 24001 shows up even with updates paused.

    Notice the new KB5007651 doesn't show in history yet and icon with yellow mark.

    Image

    Image

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-01-28T11:07:35+00:00

    Hello Sibro,

    The trick worked, I fooled W.U. and here is the result, got 25284 instead of 25285 and W.U. is no longer trying to update it. 😂

    Too much work though, we need a proper fix from MS. 🤐🤐🤐

    They need to make sure the security updates are compatible with the Windows build where they get installed.

    I think it would be a little easier trick for the case Pauli described for 22621.1105 or .1194, he still has the folder 1.0.2207.20002-0 which is the one good for build 22621.

    Just renaming the folder would do the trick to fool W.U. 😎

    Image

    Image

    Image

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-01-28T10:27:26+00:00

    Hi Sibro,

    I compared the features ids of the 2 machines and found a few differences, but none of those affected the behavior of W.U.

    I cleaned up the two kb5007651 2301.7001 and 2301.24001 and reinstalled the security version 1000.25284.1000.0

    But as soon as I resumed the windows update this one came down and installed again. 😜🤷‍♂️

    Still unclear what causes W.U. to behave differently on the 2 machines, maybe they just have a list of the ones they experiment with.

    I have another trick to try to fool W.U.

    It worked last year, maybe it is still worth trying fooling W.U. to think that the 24001 is already installed. I'll give it a try later. 😎

    Was this answer helpful?

    0 comments No comments