Windows server 2025 Std -Windows Security platform- KB5007651(Versão 10.0.29429.1000),

Question

Hello

this is the fourth time that Windows Server 2025 Std has prompted me to install the Windows Security Platform - KB5007651 (Version 10.0.29429.1000).

The last time I installed it was on November 26, 2025. What's happening? Windows reports that it was installed correctly, but then reappears...

Thanks in adavenced

Urantia

Answer 1

The screenshot you provided is the "smoking gun" we needed.

Your caution is completely justified, on a production server, you should never run commands you aren't comfortable with.

Here is the good news: You do not need to install anything.

Look closely at the numbers from your PowerShell output in the image versus the update that is nagging you:

Update Requesting Install: Version 10.0.29429.1000

Your Installed Version (Image 1): Version 1000.29429.1000.0

They are identical. You have successfully proven that the security platform is already installed and active on your server.

This confirms my previous theory: This is a "Ghost" Update. The actual software (the security platform) updated successfully on November 26th. However, the "inventory list" (the Windows Update database) failed to tick the box that says "Done."

Every time the server checks for updates, it looks at its list, sees the box isn't ticked, and tries to offer it to you again. When it tries to install, it realizes the files are already there, and gets confused or reports "success" instantly without actually doing anything, but fails to update the list.

Since this is a production server and you want to be cautious, you should stop trying to install it. Continuing to try to install it might actually corrupt the existing valid installation.

You have two options:

Option A: The "Do Nothing" Approach (Safest) Since you have verified via PowerShell that version .29429 is running, you can simply ignore this prompt. It is a cosmetic bug in the UI, not a security hole. Eventually, Microsoft will release a newer version (e.g., .29500), and that new update will likely overwrite this error and clear the notification.

Option B: Hide the Update (Cleanest) If the red warning bothers you or your monitoring tools, you should "hide" this specific update so Windows stops checking for it.

Download the "Show or hide updates" troubleshooter package from Microsoft (often called wushowhide.diagcab).

Run it on the server.

Click Hide updates.

Select the KB5007651 update from the list.

This forces Windows to stop looking for this specific version, stopping the loop.

My recommendation: As a System Admin, since the Get-AppPackage command confirms you have the correct version, you are safe. If you don't have the wushowhide tool handy, just leave it alone. The error is annoying, but it is not affecting your server's security or stability.

Hope you are clear and have found something useful in this answer. If it is, kindly accept answer so that other people sharing the same problem would benefit too. Thank you, have a nice weekend!

VP

Answer 2

It seems that you are experiencing an issue where the Windows Security Platform update KB5007651 is repeatedly prompting for installation on your Windows Server 2025 Standard, even though it reports that the installation was successful. This can happen due to various reasons, such as:

1. Corrupted Update Files: Sometimes, the update files may become corrupted, causing the system to think that the update has not been installed correctly.
2. Pending Restart: If there are pending restarts required after an update, it might lead to the system prompting for the same update again.
3. Update Conflicts: Other updates or system configurations might conflict with the installation of this specific update.
4. Windows Update Service Issues: Problems with the Windows Update service itself can lead to repeated prompts for updates.

To resolve this issue, you can try the following steps:

• Run the Windows Update Troubleshooter to identify and fix issues automatically.
• Check for any pending restarts and complete them.
• Manually download and install the update from the Microsoft Update Catalog.
• If the problem persists, consider resetting the Windows Update components.

If these steps do not resolve the issue, you may want to consult Microsoft's support for further assistance.

---

References:

• Windows Server 2025 known issues and notifications

Answer 3

Hi Urantia,

To explain your case, the repeated installation loop of KB5007651, specifically the Windows Security Platform, on Windows Server 2025 is a distinct issue from standard cumulative update failures. This behavior is typically caused by a synchronization gap between the installed binary version of the SecurityHealthService and the detection rules cached in the Windows Update agent. Unlike standard OS patches, this update modifies the UWP-based interface (Microsoft.SecHealthUI) and the underlying platform simultaneously. If the Appx registration for the UI component fails silently or doesn't update the version registry key despite the binaries being laid down, the Windows Update agent (WUA) will continually flag the update as "Required" because the IsInstalled check returns false.

The suggestion to download this from the Microsoft Update Catalog is rarely effective here because platform updates like KB5007651 are frequently distributed via the UUP (Unified Update Platform) pipeline and are not always available as standalone .msu installers. Instead, you need to force the system to acknowledge the installed components. Open an elevated PowerShell console and run Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage. If that command is not recognized, or to be more thorough, you can re-register the manifest directly by locating the latest version folder in C:\Windows\System32\SecurityHealth and running: Add-AppxPackage -Register -DisableDevelopmentMode "C:\Windows\System32\SecurityHealth\<VersionNumber>\Microsoft.SecHealthUI_8wekyb3d8bbwe.appx".

Once you have refreshed the package registration, you must clear the corruption from the update history database to break the loop. Stop the wuauserv service and rename the folder C:\Windows\SoftwareDistribution\DataStore to DataStore.old. You do not need to delete the Download folder, as this is a metadata parsing error, not a file corruption issue. Restart the service and check for updates; this forces WUA to re-scan the actual file versions. If the update still appears despite the file version of C:\Windows\System32\SecurityHealth\SecurityHealthService.exe matching 10.0.29429.1000, the most pragmatic solution is to use the "Show or Hide Updates" troubleshooter (wushowhide.diagcab) to mask this specific GUID, as it is a cosmetic reporting error that will likely be superseded by the next platform revision (e.g., .1001 or higher).

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer then. Should you have more questions, feel free to leave a message. Have a nice day!

VPHAN

Answer 4

Hi Urantia,

How was your issue? Has it been resolved yet? If everything is okay, don't forget to accept the answer as it helps other people sharing the same problem as yours. Should you need further assistance, feel free to leave a message.

VP