Still having install issues with KB5087539 on Windows Server 2025

BrianO 0 Reputation points
2026-05-14T07:08:37.0933333+00:00

So to be clear, I install Windows Server 2025 from a DVD, not an ISO from the Internet. I can't imagine that makes a difference, but there it is. `I have been trying to update several Dell servers that are a few years old, but still supported. Server 2025 installs perfectly fine. No issues, no missing device drivers, system files all pass the checks. However ,upon trying Windows Update the first time, I get three updates. They are: Malicious Software Removal Tool (KB890830), .Net Framework Security Update (KB5087051) and whatever the latest all inclusive security update of the month is available. The last one caused constant reboots and retries. The new one, KB5087539, is almost as bad. It won't install successfully. It just keeps retrying the download and install. Yes, I've tried the old trick of stopping WU services and renaming the old WU folders before trying again. I've been through all the usual checks, tricks and hotfixes, used DISM to install, but it still won't install. This is the kind of junk that causes people to move to Linux. So after all that background, my question is: When are you going to fix this? I am attaching a DISM log in hopes it helps you guys in some way. I have installed only two pieces of software, but again, I doubt this has anything to do with it. I have installed your EDGE browser and Dell's OMSA software, neither of which were running during the update. [PII removed]

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Brian Huynh 3,650 Reputation points Microsoft External Staff Moderator
    2026-05-15T02:00:51.3933333+00:00

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

    Based on the logs you shared, The DISM package manager is failing with the error code 0x800f0982 across multiple processes, including CMsuPackage::ProcessMsu and CPackageManagerCLIHandler::ExecuteCmdLine. This error translates to PSFX_E_MATCHING_COMPONENT_NOT_FOUND. This specific error means that the Windows Update engine cannot find a required component in the Windows Component Store (WinSxS) to apply the update payload. The root causes for this are typically corrupted Language Pack configurations, a corrupted servicing stack, or residual files from incomplete previous updates that are blocking the current installation.

    To isolate the issue, please first verify the integrity of the Component Store and attempt to repair any missing links. Open Command Prompt as an Administrator and run the following commands sequentially to clean up and restore the system image:

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

    Once the scans are complete, restart your machine and attempt to install the update via Settings > Windows Update.

    If the standard repair fails to resolve the error, you should clear the Windows Update cache and restarting the update services to force Windows to rebuild the update database. In your Command Prompt, execute these commands:

    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

    Additionally, if you have recently added or removed any display languages, please navigate to Settings > Time & language > Language & region and ensure there are no pending language pack installations. You can then try downloading the standalone MSU package for your specific KB update directly from the Microsoft Update Catalog to bypass the built-in update agent.

    If the installation continues to fail, I will need a bit more data to pinpoint the exact missing component. Please share the most recent error entries from C:\Windows\Logs\CBS\CBS.log specifically around the timestamp of the failure. Additionally, running the command below will help us see if there are any partially installed packages stuck in the system:

    DISM /Online /Get-Packages /Format:Table

    I will follow up on this thread to ensure that you regain access to your licenses. If this helps, please consider clicking "Accept answers" to help others with the same issues.

    Official Microsoft documentation: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/repair-a-windows-image

    Was this answer helpful?

    1 person found this answer helpful.
  2. Hesham Raza 0 Reputation points
    2026-05-14T07:15:16.6533333+00:00

    KB5087539 appears to be failing during the servicing phase, not during download. Since Server 2025 is newly installed, the issue is likely tied to the servicing stack or component store corruption on certain older Dell hardware platforms.

    Try the following in order:

    Install the latest Servicing Stack Update manually from the Microsoft Update Catalog

    Run:

    DISM /Online /Cleanup-Image /RestoreHealth

    sfc /scannow

    Clear pending updates:

    dism /online /cleanup-image /startcomponentcleanup

    Reboot twice.

    Attempt manual installation of the .msu package instead of Windows Update.

    Also verify BIOS and firmware are current through Dell Support because older firmware has caused CBS servicing failures on recent cumulative updates.

    Was 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.