Windows Server 2025 windows: failed to install the following update with error 0x80073712: 2026-04 Security Update (KB5082063) (26100.32690).

MadUrantia 200 Reputation points

Can I have some help?

Windows Server 2025 Std, V 24H2, OS build: 26100.32522

The 2026-04 Security Update (KB5082063) (26100.32690) fails with the following error:

Installation failed: Windows failed to install the following update with error 0x80073712: 2026-04 Security Update (KB5082063) (26100.32690). I paused the updates.

In my search for information, I found this website: https://support.microsoft.com/en-us/topic/april-19-2026-kb5091157-os-build-26100-32698-out-of-band-13ab53cc-ccc8-4a00-89d2-823b58fa03ec

It states:

"[Windows update installation] Fixed: A small number of Windows Server 2025 devices might fail to install the April 14, 2026, Windows security update (KB5082063). When this issue occurs, affected devices might display one of the following error messages: “Install error: 0x800F0983” or “Some update files are missing or have problems. We’ll try to download the update again later. Error code: 0x80073712.”

This April-19-2026-kb5091157-os-build-26100-32698-out-of-band, refers os-build-26100-32698.

.... My Windows Server 2025 Standard, Version 24H2's OS Build is: 26100.32522.

  1. Should I install the this april-19-2026-kb5091157-os-build-26100-32698-out-of-band?

The server is in production. What should I do to overcome the installation error: Windows failed to install the following update with error 0x80073712: 2026-04 Security Update (KB5082063) (26100.32690).

Thanks in advance

0 comments No comments
Sign in to comment

3 answers

  1. Domic Vo 24,370 Reputation points • Independent Advisor

    Hello MadUrantia,

    The error code 0x80073712 indicates that the update payload is corrupted or missing components, which aligns with Microsoft’s own acknowledgment in the KB5091157 article. Since your server is on build 26100.32522 and the failed update (KB5082063) targets 26100.32690, the recommended resolution is to apply the out‑of‑band update KB5091157, which brings the system to 26100.32698 and explicitly fixes this installation failure. Microsoft has confirmed that this patch addresses both 0x80073712 and 0x800F0983 errors.

    Given that this is a production server, the safest approach is to manually download KB5091157 from the Microsoft Update Catalog and apply it during a maintenance window. Before installation, run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow to ensure component store integrity, as corruption in WinSxS often triggers 0x80073712. Once KB5091157 is installed, the April security baseline will be satisfied and subsequent cumulative updates should apply normally. If the out‑of‑band patch also fails, you’ll need to review CBS.log under C:\Windows\Logs\CBS\ for detailed error traces and consider a repair install, but in most cases KB5091157 resolves this issue directly.

    👁 User's image

    If the above response helps answer your question, please hit "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    Domic V.

    1. MadUrantia 200 Reputation points

      Hello Domic

      Believe me. I'm not evaluating your response at all.

      But why are there so many methods to install KB5091157?

      Microsoft proposes other methods in this link: https://support.microsoft.com/en-gb/topic/april-19-2026-kb5091157-os-build-26100-32698-out-of-band-13ab53cc-ccc8-4a00-89d2-823b58fa03ec#id0ejbf=catalog ---- How to get this update / Catalog

      In these referenced methods, in your opinion, should I also run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow before installation?

      It's precisely because the server is in production that I'm really confused.

      Thanks

    Sign in to comment
  2. Domic Vo 24,370 Reputation points • Independent Advisor

    Hi MadUrantia,

    Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

    Domic V.

    1. MadUrantia 200 Reputation points

      Because the server in question is in production, it requires some restraint from me.

      That's why I posted my first comment to your response. These forums are intended to help/clarify/provide solutions, if possible, to questions raised. Why didn't you respond to my first comment?

      Best Regards

    Sign in to comment

  3. AI answer

    Installing the April 19, 2026 out-of-band (OOB) update KB5091157 is the correct way to address this issue on Windows Server 2025.

    KB5091157 is specifically documented as fixing two problems introduced by the April 2026 security update KB5082063 on Windows Server 2025:

    1. Domain controllers may restart repeatedly after installing KB5082063.
    2. A limited number of Windows Server 2025 devices might fail to install KB5082063 (with errors including 0x80073712).

    The Windows message center notes that for Windows Server 2025, the OOB update KB5091157 “addresses both the installation failure issue and the domain controller restart issue.”

    KB5091157 is a cumulative update that brings the OS to build 26100.32698. It is designed to be installed on systems currently on earlier builds (such as 26100.32522) and to replace/cover the problematic April security update KB5082063. Installing KB5091157 on the production server is therefore the supported remediation path.

    Recommended steps for the production server:

    1. Keep KB5082063 paused/blocked for now (do not keep retrying it).
    2. Download and install the out-of-band update KB5091157 for Windows Server 2025 from the Microsoft Update Catalog or via Windows Update, following the guidance in its KB article.
    3. After KB5091157 is successfully installed and the server is on OS build 26100.32698, resume normal Windows Update and allow future updates to install.

    This sequence both resolves the 0x80073712 installation failure and ensures the server has the April 2026 security fixes without the known issues from KB5082063.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer