KB5099538 update is failing with error 0x800F0988

Chris Bailey 0 Reputation points
2026-07-26T22:16:34.6833333+00:00

Problem description

A production server running Windows Server 2019 Standard, Desktop Experience, x64, en-US cannot install cumulative update KB5099538. The server is currently on build 17763.1697. The update fails through both Windows Update and the standalone Microsoft Update Catalog MSU.

The repeated installation error is:

0x800F0988 - PSFX_E_INVALID_DELTA_COMBINATION

CBS logs consistently identify the same failure while staging the update. The failing file is:

Microsoft.IdentityServer.Service.Resources.dll

Representative CBS failure:

Failed to pre-stage package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.9020.1.30 File: Microsoft.IdentityServer.Service.Resources.dll HRESULT: 0x800F0988 - PSFX_E_INVALID_DELTA_COMBINATION Failure source: Stage

The AD FS role is not installed. The failing file exists only in the Windows component store. The server has the current servicing stack version 17763.9015.1.3, and KB5005112 is already installed.

Troubleshooting completed

Attempted installation through Windows Update. Installation failed with Event ID 20 and error 0x800F0988.

Downloaded the standalone KB5099538 MSU from the Microsoft Update Catalog and installed it with WUSA using /quiet /norestart. It failed with the same 0x800F0988 error.

Reset the Windows Update cache by stopping wuauserv, BITS, and cryptsvc; renaming SoftwareDistribution and catroot2; and restarting the services.

Ran DISM /Online /Cleanup-Image /ScanHealth. No component-store corruption was detected.

Ran DISM /Online /Cleanup-Image /RestoreHealth. The operation completed successfully.

Ran sfc /scannow. Windows Resource Protection did not find any integrity violations.

Mounted a Microsoft Windows Server 2019 Evaluation ISO and ran DISM RestoreHealth using F:\sources\install.wim, index 2, with /LimitAccess. The operation completed successfully.

Rebooted the server and retried KB5099538. The update failed again with the same error.

Verified that no reboot was pending and no packages were listed as Install Pending, Uninstall Pending, or Staged.

Verified the server is not using WSUS.

Searched public Windows Update directly. Only the Microsoft Defender intelligence update KB2267602 was offered.

Verified that KB5005112 is installed and that the current servicing stack is Package_for_ServicingStack_9015, version 17763.9015.1.3.

Verified that AD FS, Identity Federation Support, and Windows Identity Foundation are not installed.

Reviewed archived CBS logs and confirmed repeated failure on Microsoft.IdentityServer.Service.Resources.dll.

Did not manually replace, delete, or modify files in WinSxS.

Assistance requested

Any thoughts to go foreward.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

2 answers

Sort by: Most helpful
  1. SamT 6 Reputation points
    2026-08-02T03:50:12.14+00:00

    @Chris Bailey

    Hello Chris,

    This behavior 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 all of the usual steps 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 support methodology.

    It has been my experience that sometimes a future Windows CU may install successfully in which case you will eventually get the July 2026 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 it eventually stopped taking any CUs. The only solution was to retire that (physical) server.

    I posted this because A) I have a server that has never had any issues until now - KB5099538 keeps rolling back. B) You are not the only person reporting issues with the July 2026 CU C) Others may be wasting time with MS support refusing to examine the root issue with a CU but instead looking for ways to blame your server. Your server may have never had any issue before but as of the July 2026 CU the server has magically become "corrupted" as Microsoft likes to assert.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments

  2. Brian Huynh 3,650 Reputation points Microsoft External Staff Moderator
    2026-07-28T01:28:18.72+00:00

    Hello, thank you for posting in the Microsoft Q&A community.

    The error code 0x800f0988 translates to PSFX_E_MATCHING_COMPONENT_NOT_FOUND. This generally happens when Windows Update attempts to apply a patch but cannot find the specific servicing component or base files required in the Windows Component Store (WinSxS). This is typically caused by component store corruption, incomplete previous updates, or heavily fragmented update caches.

    To resolve this, our most ffective approach is to clean up the Component Store and repair the Windows image. Please open an elevated Command Prompt by searching for cmd, right-clicking Command Prompt, and selecting Run as administrator. Execute the following commands one by one, allowing each to complete before moving to the next:

    DISM /Online /Cleanup-Image /StartComponentCleanup
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    

    Once the repair tools finish, we should reset the Windows Update cache to clear out any corrupted download files that might be interfering. In the same administrative Command Prompt, run the following commands to stop the update services, rename the cache folders, and restart the services:

    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
    

    After performing these steps, reboot your system and attempt to check for updates again.

    If the update mechanism still fails, you can bypass the Windows Update channel as a reliable workaround. You can manually download the standalone MSU file for KB5099538 directly from the Microsoft Update Catalog website. Search for "KB5099538", download the version matching your operating system architecture, and install it manually. Alternatively, if the Component Store is severely damaged, performing a repair install (In-Place Upgrade) using your Windows installation media will cleanly rebuild the Component Store while preserving your files, apps, and settings.

    I will follow up on this thread to ensure your issue is resolved. If this information helps clarify the behavior, please consider clicking "Accept Answer" so that other community members can benefit from it.

    For official Microsoft documentation, you can refer to: https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting-guideline https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image

    Was this answer helpful?

    0 comments No comments

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.