Windows Update Unsuccessful

KB5089549 is the May 2026 “B” security update for Windows 11 version 25H2 (OS build 26200.8457). When this update fails repeatedly, the underlying issue is almost always with the local Windows Update client or its configuration, not with System Center Operations Manager itself.

Use these steps on the affected machine:

1. Confirm OS version and target build
   • On the machine, check Settings → System → About and confirm it is running Windows 11, version 25H2.
   • KB5089549 targets build 26200.8457 for that version, as listed in the Windows 11 release history. If the OS is a different version, this update will not apply.
2. Check the local Windows Update client
   • On the machine, open Settings → Windows Update and select Check for updates.
   • If KB5089549 appears and fails there as well, note the error code shown. That code will indicate whether the problem is missing prerequisites, corruption, or a source issue (for example, WSUS vs. Microsoft Update).
3. Verify update source and policy (especially if using WSUS/Update Manager)
   • If the machine is managed by WSUS or Azure Update Manager, ensure the update is actually approved and available from that source. Update Manager only installs updates that the Windows Update client can see when Check for updates is used locally.
   • If Group Policy forces a WSUS server or blocks Microsoft Update, deployments can fail. Check that Group Policy and WSUS configuration align with the intended behavior.
4. Retry deployment from the update management tool
   • If using Azure Update Manager or another tool to orchestrate patching, re-run an assessment and then a deployment for this machine.
   • Remember that updates installed via Update Manager’s WUA APIs will not appear in the Settings app’s Windows Update history, so use the management tool’s logs or Azure Resource Graph data to confirm success.
5. If failures persist
   • Use the error code from the local Windows Update attempt and correlate it with the logs in the update management solution (for example, Update Manager’s installation results in Azure Resource Graph) to determine whether the issue is source-related (WSUS/Microsoft Update), policy-related (Group Policy), or local corruption.

For SCOM specifically, there is no SCOM-side configuration required for this particular KB; SCOM simply reports the OS state. Focus troubleshooting on the Windows Update client, update source (WSUS/Microsoft Update/Azure Update Manager), and Group Policy.

References:

• Windows 11 release information
• How Update Manager works
• Configure Windows Update settings for Azure Update Manager