Still having install issues with KB5087539 on Windows Server 2025

BrianO 0 Reputation points

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]

  1. Hi,

    Since the normal Windows Update reset did not help, I would focus on CBS.log and DISM.log first. They usually show more useful details than the update error message.

    I would also check whether any packages are stuck in a staged or pending state:

    DISM /Online /Get-Packages /Format:Table

    If you have one server where the update works and one where it fails, comparing CBS.log, DISM.log, installed language packs/FoD packages and build state may help narrow it down.

Sign in to comment

2 answers

  1. Brian Huynh 3,305 Reputation points • Microsoft External Staff • Moderator

    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:

    1. McMeekin, Robert I. (IT Director) 10 Reputation points

      I'm running into similar issues with this update. Getting to 93% and then it fails. I started a post here as well incase either of us find the solution.

      Issues Installing Security Update KB5087539

    2. BrianO 0 Reputation points

      oldCBS.log Here is the CBS log. Sorry it took so long to get back to you. I hope this helps. Thanks

    3. BrianO 0 Reputation points

      So I ran through your step by step instructions above and it failed again. Here is the DISM Packages log you wanted. DISMGetPkgs.txt

    4. BrianO 0 Reputation points

      Given the errors, I'm wondering if it is failing because Defender Anti-Virus is not installed. If that is a requirement, then Microsoft should install it. Keeping in mind that Defender Anti-Virus was not compatible with 2025 when it was released. Cumulative updates should include prerequisites.

    5. Brian Huynh 3,305 Reputation points • Microsoft External Staff • Moderator

      Thank you for providing the DISM output. Based on the package list you shared, I performed a deep-dive analysis and found a couple of significant issues in the Windows Component Store that are causing the 0x800f0982 (PSFX_E_MATCHING_COMPONENT_NOT_FOUND) error.

      First, your system is running Build 26100, and several feature packages are stuck in a Staged state rather than being fully installed. The Remote Access and SSTP API packages were unpacked, but their installation was interrupted. Staged packages that never finalize often block new Cumulative Updates.

      Second, there is a version mismatch between your 64-bit (amd64) and 32-bit (wow64) Features on Demand (FoD). When the Windows Update engine attempts to apply a new patch, it checks for a matching baseline across all architectures. Because your WoW64 components are out of sync, the engine aborts the installation because the required matching components are "missing."

      To isolate this and attempt to clear the stuck components, please open an elevated Command Prompt and run the following commands to forcefully remove the pending Staged packages:

      
DISM /Online /Remove-Package /PackageName:Microsoft-OneCore-RasSstp-Api-Package~31bf3856ad364e35~amd64~~10.0.26100.1

DISM /Online /Remove-Package /PackageName:Microsoft-Windows-Networking-RemoteAccess-PowerShell-Base-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1

DISM /Online /Remove-Package /PackageName:Microsoft-Windows-Networking-RemoteAccess-PowerShell-Base-Package~31bf3856ad364e35~amd64~~10.0.26100.1150

      After these complete, restart your machine and attempt the update again.

      You can review the official Microsoft troubleshooting guidelines and repair strategies for Windows Update issues here: https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/windows-update-issues-troubleshooting-guidelines

    Sign in to comment
  2. Hesham Raza 0 Reputation points

    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.

    1. Andy Herron 0 Reputation points

      Would you describe the process for "Install the latest Servicing Stack Update manually from the Microsoft Update Catalog"? Or is that the "DISM /Online /Cleanup-Image /RestoreHealth" and "sfc /scannow" commands? I'm seeing this same behavior that BrianO reported (and I too installed Windows Server 2025 from DVD) and getting the same 0x800f0982 status code on applying the update to a server running Win Server 2025 bare metal. Mine is not an older Dell but instead a current Asus motherboard that is up to date on BIOS and firmware. Note it's also happening to a VM I have running Win Server 2025.

    2. BrianO 0 Reputation points

      Sorry for the delay. Here is the CBS.log file. The server BIOS, iDrac and everything else is all up to the latest versions. There are several errors in this file. Mostly having to do with Defender. Please let me know if this helps. ThanksCBS.log

    Sign in to comment
Sign in to answer

Your answer