Share via

Windows Update 2026-05 Preview Update (KB5089573) (26200.85424)

Morten Fly 25 Reputation points
2026-05-29T06:04:31.4766667+00:00

Windows 11 update - 2026-05 Preview update (KB5089573)

I received this update Tuesday (26-05-2026) but despite several restarts (10+), login as admin or user, it still says the computer needs a restart.

Is there anything I can do in order for Windows to implement and "accept" this update?

Windows Insider program | Windows Insider preview | Install, activate, and Windows update

Answer recommended by moderator

Morten Fly 25 Reputation points
2026-06-03T14:22:26.34+00:00

Hi Thomas

I have solved the issue using your solutions as inspiration :)

Steps:

  1. Log on computer as local admin
  2. Go to services.msc and stop, wait a few sec, start Windows Update service
  3. Used your solution starting with Reset Windows Update
  4. After a restart (again log on as local admin) I used an elevated CMD to run
    1. sfc /scannow
    2. DISM /Online /Cleanup-Image /RestoreHealth
    3. sfc /scannow
  5. Restart computer and log on as domain user (as usual)

There are currently no trace of KB5089573 and no pending updates or restarts.

Thanks a lot for your help!

Was this answer helpful?

2 people found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Thomas4-N 17,280 Reputation points Microsoft External Staff Moderator
    2026-05-29T11:01:18.7966667+00:00

    Hello Morten Fly,

    Thanks for reaching out. A bit of context that might be relevant first.

    • This one, KB5089573, is a preview/optional cumulative on the Release Preview channel, and there are a couple of things going on around it. Microsoft has mentioned that the Secure Boot 2023 certificate rollout is moving through the April and May 2026 cumulatives, and that can legitimately cause a few extra "needs restart" prompts while the firmware certificate handoff completes, though that's usually two or three rounds, not ten.
    • The release note for KB5089573 also lists a known issue where install fails at the reboot stage with error 0x800f0922 due to insufficient free space in the EFI System Partition.
    • So if you check Settings > Windows Update > Update history and look at the KB5089573 entry, it'd help to know whether there's an error code shown next to it, since that would point us at the right branch.

    In the meantime, the usual sequence for clearing a stuck "pending restart" state is:

    • Run the Windows Update troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update.
    • Reset Windows Update components from an elevated Command Prompt (clears any stuck servicing transaction):
    • net stop wuauserv && net stop cryptSvc && net stop bits && net stop msiserver
    • ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    • ren C:\Windows\System32\catroot2 catroot2.old
      • net start wuauserv && net start cryptSvc && net start bits && net start msiserver
      • Restart, then check Windows Update again.
      • If it's still pending, try dropping the stuck transaction with DISM /Online /Cleanup-Image /RevertPendingActions from an elevated prompt, then restart and retry.
    • If the error in history does turn out to be 0x800f0922, that's the ESP-space known issue, and that one isn't really fixable from inside Windows Update — safer to wait for the fix Microsoft is preparing than to manually resize the partition.

    One option worth keeping in mind, since this is a preview update rather than a mandatory one, is just skipping it and waiting for the June Patch Tuesday cumulative, which should supersede KB5089573 and may clear the pending state on its own once it installs. So if you'd rather not keep wrestling with this specific build, that's a reasonable path too.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

    Was this answer helpful?

    5 people found this answer helpful.

  2. Morten Fly 25 Reputation points
    2026-06-08T06:13:34.46+00:00

    Update:

    After 1-2 days the Microsoft Update tried to install KB5089573 again with the same result.

    Again I had to use the hotfix @Thomas4-N suggested and again it helped sorting it out.

    So in order to prevent it from asking for a restart that won't do anything I have now postponed all updates until mid June.

    Usually new updates are released the 2nd Tuesday each month (at least that's how Microsoft used to do it), so by doing this I hope a new update that will fix the issue will be available.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  3. AI answer

    2026-05-29T06:04:46.2233333+00:00

    For this symptom, Windows still thinks a restart is required to complete a previous installation.

    The supported steps are:

    1. Restart the device again. In many cases, a second or third restart is needed because another program or Windows update still has pending changes.
    2. If the message persists after multiple restarts, reinstall any programs or Windows updates that were recently installed. This can allow a failed installation to complete successfully.
    3. If the issue still occurs after several restarts and reinstalling recent updates, contact Microsoft Customer Service and Support so they can determine why Windows continues to report that a restart is required.

    Do not attempt to work around this by manually editing or deleting Windows Registry keys or values, as this can cause further issues, especially if the failed installation was a Windows update.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.