Unable to Install KB5099538 and KB5094123 on Windows Server 2019 (Build 17763)

Question

I am running Windows Server 2019 (build 17763) and have been unable to install the following cumulative updates:

June 2026 Cumulative Update (KB5094123)

July 2026 Cumulative Update (KB5099538)

Both updates fail to install, whether attempted via Windows Update or manual .msu installation from the Update Catalog.

Troubleshooting already performed:

Ran SFC and DISM scans (no integrity violations found).

Reset Windows Update components (SoftwareDistribution and Catroot2).

Attempted manual installation using wusa.exe.

Verified Servicing Stack Updates installed via DISM. The latest SSU present is:

Package_for_ServicingStack_9015~31bf3856ad364e35~amd64~~17763.9015.1.3 (June 2026).

Problem:

KB5099538 requires a newer SSU (build 9130 or later), but the July SSU is not available in the Update Catalog under the expected KB number. As a result, both KB5094123 and KB5099538 fail to apply.

Request:

Please provide:

The correct KB number and download link for the Servicing Stack Update that supersedes build 9015 (June 2026).

Guidance on whether KB5099538 can be installed directly after applying the newer SSU, or if I should skip to the August 2026 cumulative update.

Thank you for your assistance.

Best regards,

Faruk

Answer 1

@Faruk Gokcek

Hello Faruk,

This is the usual nonsense from Microsoft and it has been a problem for the last 10+ years.

i.e. Some updates on particular systems will not install and they roll back during the reboot. Contact MS support and they go through their standard process of blaming you and wasting your time with running different utilities until you give up and go away - I've been doing Windows Server support for over 30 years, and I can tell you that they are experts at this methodology.

It has been my experience that sometimes a future Windows CU may install successfully so you will of course eventually get these fixes, but that is not a good solution for a production system.

I had one particular server in a lab environment that would only take the latest monthly CU once every few months but eventually stopped taking the CU. The only solution was to retire that (physical) server.

I posted this because A) I have another server that has never had an issue until now - KB5099538 keeps rolling back. B) Others may be wasting time with MS support refusing to examine the root issue but instead looking for ways to blame you.

Answer 2

This exact failure mode (months of CUs failing 0x800f0986 while DISM/SFC report clean) is usually a corrupt file in the WinSxS delta chain - a piece DISM never deep-verifies. You can pinpoint the exact corrupt file by replaying the hydration math with msdelta.dll and often reconstruct the correct replacement from files already on disk, no donor or reinstall needed. I hit this on a production Server 2019 / SQL host (root cause: the stored RTM base of driversipolicy.p7b was truncated to 1,395 bytes) and published the method + PowerShell toolkit here: https://github.com/<YOUR-USERNAME>/winsxs-hydration-repair . Start with Collect-CbsEvidence.ps1 -> hydration_failures.txt names the failing component and file, then Test-ComponentDeltaChain.ps1 gives a verdict. Do not run DISM /ResetBase while broken - it destroys the reverse deltas the recovery needs.

Answer 3

Hi Faruk,

Please install the latest cumulative update again and let it fail. Then, share a zipped copy of the following folder on OneDrive or GoFile.io.

C:\Windows\Logs\CBS

Answer 4

Hello Faruk,

Based on Microsoft's July 2026 release information, KB5099538 (OS Build 17763.9020) is the latest July 2026 cumulative update for Windows Server 2019 and already includes the fixes from KB5094123. If you can install KB5099538 successfully, there is no need to install KB5094123 first.

What concerns me is the statement that KB5099538 requires an SSU build 17763.9130. I cannot find any Microsoft publication indicating that a standalone SSU with build 9130 exists for Server 2019. In fact, for Windows Server 2019, Servicing Stack Updates have been delivered as part of the cumulative update package for some time, rather than as separately published SSUs.

Since both the June and July LCU fail, I suspect the issue is not a missing SSU but rather a servicing stack/component store problem or another prerequisite failure. I would recommend reviewing:

CBS.log

C:\Windows\Logs\CBS\CBS.log

WindowsUpdate.log

Get-WindowsUpdateLog

and checking the exact installation error returned by:

dism /online /get-packages | findstr 17763

At this point, I would not spend more time searching for an SSU 9130 package, as there is no evidence that Microsoft has released such a standalone SSU for Server 2019. The next step should be identifying the actual installation error code from CBS.log, which will reveal whether the failure is due to servicing corruption, a pending package state, or another prerequisite issue.