KB5100998 Shows Installed but CBS State Remains Install Pending (CurrentState = 60)

Question

Hi Microsoft Support Team,

We are encountering an issue on a few Windows systems while installing KB5100998 and would appreciate your assistance in identifying the root cause and recommended resolution.

Issue Description

After deploying KB5100998, Windows Update indicated that a reboot was required. Once the system was restarted:

• Windows Update shows KB5100998 as successfully installed.
• However, the Event Viewer records the following error:

  Windows Update could not be installed because of error 2359302

• Additionally, the following CBS package registry entry remains in the Install Pending state:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9340.4
  

CurrentState = 60

According to the Microsoft CBS servicing states documentation: https://learn.microsoft.com/en-us/archive/blogs/tip_of_the_day/tip-of-the-day-cbs-servicing-states-chart-refresher

A CurrentState value of 60 indicates Install Pending.

Observed Behavior

This results in an inconsistent state:

• Windows Update reports the update as Installed.
• Manual installation of KB5100998 reports that the update is already installed.
• The CBS package registry still indicates Install Pending (CurrentState = 60).
• Event Viewer logs error 2359302.

This behaviour has been observed only on a subset of systems; other systems install the same update without issue.

During our testing, we observed that if we remove the affected CBS package using DISM and then deploy KB5100998 again, the installation completes successfully and the CurrentState value for the package transitions from 60 (Install Pending) to the expected installed state (70).

This indicates that the package can be installed successfully after the existing CBS package is removed and reinstalled. We would like to understand:

Our Questions

1. What could cause this mismatch between Windows Update, CBS package state, and the Event Viewer?
2. Under what circumstances can a package remain in CurrentState = 60 (Install Pending) while Windows reports the update as installed?
3. Is this a known servicing issue for .NET Framework updates?
4. What additional logs or diagnostics would you recommend collecting to determine the root cause?
5. Is there a Microsoft-recommended workaround or repair procedure to transition the package to the correct installed state?
6. What causes the CBS package state to become inconsistent on only a subset of machines?
7. Why does removing the package with DISM and reinstalling the update resolve the issue?
8. Is this a known CBS servicing issue, and is there a Microsoft-recommended workaround that avoids manually removing the package?

Additional Information:

We have observed this issue only with this month's .NET Framework cumulative updates. Previous months' .NET updates did not exhibit this behavior.

So far, we have identified approximately 25 affected machines across 25H2 OS environments. On these systems, Windows Update reports the update as Installed, while the CBS package remains in CurrentState = 60 (Install Pending), resulting in inconsistent servicing state.

We would like to know whether Microsoft is aware of any issue affecting this month's .NET updates and whether there is a recommended root cause analysis or permanent resolution for this behavior.

Thank you for your support.

Kind regards,
<PII removed>

Answer 1

Hello ZOHO CORPORATION PRIVATE LIMITED,

Welcome to Microsoft Q&A forum.

Currently, I don't see any reports about this issue on any article or in another thread (not as I know of). However, as you said, if the issue is already observed in 25 computers, you should report it directly to the Engineering team using the Feedback Hub apps.

Regarding your questions.

1. As you described, I suspect that it could be whether the CBS package complete partially or inconsistency between content metadata.
2. There are 2 possibilities in this, pending restart process failed (This should leave pending.xml, reboot.xml and sessions.xml in C:\Windows\WinSxS), missing CBS commit (can be observe in CBS log) or incorrect servicing stack interaction.
3. I'll say that I'd collect the CBS logs and the Windows update logs next. Also, I'll try to run DISM scan and restore to make sure.
4. The reasons that only 25 computers are affected prove that the update payload itself is probably not the cause. This could cause by already existing CBS difference or leftover servicing or suspended .NET packages remnants.
5. DISM removal and reinstall can removes the stale CBS registration and force it to rebuild dependency, which combine with the new package metadata could help with the installation.

---

If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.