Registry state mismatch after KB5121003 installation

Question

Hello Microsoft Support Team,

I am reaching out regarding an observed behavior with the installation of KB5121003 on Windows 11 25H2.

After deploying KB5121003, the system build version correctly updated to 26200.9168 (confirmed via winver). However, in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages, the package entry for Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9168.1.19 remains in state 96 (Install Pending).

Key points:

• Winver shows build 26200.9168, indicating KB5121003 is installed.
• Windows Update history also lists KB5121003 as successfully installed.
• DISM /Get-Packages shows the package present, but uninstall attempts fail with error 0x800f0905.
• Registry state remains at 60 instead of transitioning to 70 (Installed).

https://learn.microsoft.com/en-us/archive/blogs/tip_of_the_day/tip-of-the-day-cbs-servicing-states-chart-refresher#:~:text=80-,Install%20Pending,-0x60

Request: Could you please confirm if this registry behavior is expected for cumulative rollups, or if there is a servicing stack issue preventing the state transition? When the registry state will be changed to 70 ?

Thank you,

Answer 1

Hi Haritha,

There have been many issues reported with

this update. If it is listed under Windows Update,

Update History, Uninstall Update I would

uninstall it to see if it solves your issue.

Answer 2

Hello Haritha Duraisamy,

Thank you for providing the detailed information.

To check whether there is an actual component-store problem, please restart the device fully, then run the following command from an elevated Command Prompt: DISM /Online /Cleanup-Image /ScanHealth

You can also review C:\Windows\Logs\CBS\CBS.log for errors recorded around the installation or uninstall attempt. If ScanHealth reports no corruption and Windows Update does not continue to request a restart or repeatedly offer the same update, I would avoid manually changing the CBS registry value, as doing so could damage the servicing state.

Since your question concerns the intended internal CBS state transition, you may submit the diagnostic details through the https://aka.ms/feedbackhub or contact Microsoft Support for further investigation. It would be helpful to include the DISM output, relevant CBS.log entries, the package name, and screenshots of winver and Windows Update history.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. My role is limited to providing technical guidance on reported issues, requests, or ideas.

I know this isn't the news you were hoping for, but I wanted to make sure you got the most accurate information about your situation. Thank you so much for your understanding.

---

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.