Share via

Windows Update Blocked: Servicing Stack Package Cannot Be Removed

Sank M 0 Reputation points
2026-03-30T12:50:32.7966667+00:00

Hello,

I have servers on which it's impossible to install the latest KB updates.

When checking the installed KB updates, I see a sort of servicing stack, and I'm experiencing this issue on two servers. That made impossible for me to see the installation date of some KBs , and therefore, impossible to install new ones.

Furthermore, it's impossible to uninstall this maintenance pack.

Have you ever encountered this problem? Do you have any suggestions other than the suggested wuaserv cleanup procedure on this link ?

I've tried that, but it doesn't work.

Do you have any other suggestions?

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Nguyen Tran 14,595 Reputation points Independent Advisor
    2026-03-30T13:32:21.55+00:00

    Hi Sank M,

    The error you’re seeing is fairly common when the servicing stack update (SSU) becomes corrupted or mismatched with the cumulative update you’re trying to apply. Since SSUs are designed to be permanent, they cannot be uninstalled, which is why you’re blocked from removing it.

    The first step I recommend is checking that your servers are fully aligned with the latest servicing stack update for Windows Server. Sometimes the SSU needs to be installed manually before cumulative updates can succeed. You can download the latest SSU directly from the Microsoft Update Catalog and apply it offline.

    If that doesn’t resolve the issue, another option is to perform a component store repair using a known good source. Mount a Windows Server ISO that matches your current build and run: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess (replace D: with the mounted ISO drive). This forces DISM to use the local image instead of Windows Update.

    If the servicing stack is too damaged, the most reliable fix is an in-place upgrade repair using the latest installation media. This reinstalls the OS components while keeping your roles and data intact, and it usually clears out stubborn SSU issues.

    In short, you can’t remove the servicing stack, but you can repair or refresh it using the Update Catalog or ISO source. I hope the response provided some helpful insight. If it clarified the issue for you, please consider marking it as Accept Answer so others with the same issue can find the solution. Feel free to leave a comment if you need further information.

    Jason.

    0 comments
  2. Q&A Assist
    2026-03-30T12:51:06.4366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Servicing stack updates (SSUs) are special updates that update the Windows servicing stack itself. By design, they:

    • Are required before many cumulative/security updates can be installed.
    • Replace previous SSUs.
    • Cannot be uninstalled once installed.

    For Windows 8.1 / Windows Server 2012 R2, for example, the July 12, 2016 servicing stack update explicitly states that it:

    • Requires the April 2014 update rollup (KB2919355) as a prerequisite.
    • Replaces a previous SSU (KB3021910).
    • Cannot be removed after installation.

    Similarly, for Windows Server 2012, newer SSUs (such as KB5011571, KB5014027, KB5044412, KB5055667) update core servicing components (PkgMgr.exe, msdelta.dll, drvstore.dll, etc.) and are also non-removable. This is expected behavior and is not itself an error.

    If new updates cannot be installed:

    1. Ensure required SSUs are installed
      • For each OS version, verify that the appropriate SSU listed for that OS is installed (for example, KB2919442 for Windows 8.1/2012 R2 when seeing the Windows Modules Installer error, or the later SSUs such as KB5011571 / KB5014027 / KB5044412 / KB5055667 for Windows Server 2012).
      • If an SSU is missing, install it first (via Windows Update or the Microsoft Download Center entry for that KB).
    2. Check for the Windows Modules Installer / servicing stack requirement
      • If seeing an error like “The Windows Modules Installer must be updated before you can install this package” when installing .msu packages, install the servicing stack update appropriate for the OS (for Windows 8.1/2012 R2 this is KB2919442). This resolves cases where the servicing stack is too old to process newer updates.
    3. Do not attempt to remove the servicing stack package
      • SSUs are intentionally non-removable. The documentation explicitly states that after installing a servicing stack update, it cannot be uninstalled to revert to an earlier version.
      • The presence of an SSU entry without an uninstall option and without a normal “Installed on” date is normal and not the cause of update failure by itself.
    4. If updates still fail after SSU verification
      • Since the SSU cannot be removed and the wuaserv cleanup did not help, the next supported step (based on similar update-failure cases) is an in-place repair/reinstallation of the current Windows version to repair the servicing stack and component store while keeping data and apps. This has been used successfully in other update-failure scenarios where CBS logs show servicing/component metadata issues and standard tools (SFC, DISM, cleanup) do not resolve the problem.

    In summary: the servicing stack package being non-removable and showing differently in the update list is expected. Focus on ensuring the correct, latest SSU for the OS is installed (and any prerequisite rollups like KB2919355/KB2919442), and if update failures persist despite that and standard cleanup, proceed to an in-place repair of the OS to restore the servicing infrastructure.

    References:

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