Issue with Windows 11 24H2 update deployment using DISM

Question

Issue with Windows 11 24H2 update deployment using DISM

Haritha Duraisamy 0

Hi team,
My machine is running Windows 11 24H2, and I’ve encountered an issue while deploying the cumulative update. The update was failing with error code 0x8024001C (2146498504).

I referred to the article on 0x8024001Cand found that the issue was resolved after deploying the checkpoint cumulative update KB5043080. I also reviewed the Microsoft support article for the update [for example : August 12, 2025—KB5063878 (OS Build 26100.4946)], which mentions using the DISM method for installation.

I followed the DISM method described in the article: I downloaded both the checkpoint and the cumulative update, placed them in the same folder, and ran the DISM command. This worked, and the update installed successfully.

However, I’m now facing three issues:

The update installed via DISM does not appear in the Windows Update history.
The update installed via DISM does not provide an uninstall option in the Control Panel
The registry entries for previous updates under the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\ have been wiped, leaving only the checkpoint and the latest cumulative update entries.

Could you please advise on these issues?

0 comments

2 answers

Your answer

Answer 1

Haritha Duraisamy 0

Hi Emmanuel Santana,

To answer your questions:

1. Yes, the deployment was performed on a running system (not offline).
2. No, we did not use an offline image such as a mounted WIM.
3. No cleanup commands were executed after applying the update.

User's image

Currently, we've successfully deployed the September update [KB5065426] using the DISM method. The deployment completed without any errors, but the same three issues still persist.

And uninstall option is availble in control panel but uanble to uninstall it (screenshot attached below). [In previous thread, i mentioned as "The update installed via DISM does not provide an uninstall option in the Control Panel" instead of unable to uninstall the update]

User's image

For comparison, we tested the same DISM deployment method on a Windows 11 23H2 system. The update installed successfully, able to uninstalled the update without issue, and the registry retained information from the previous update. However, the update history was still not maintained.

Let me know if further details are needed.

Emmanuel Santana 40,110 Reputation points Independent Advisor

2025-09-11T14:11:10.7433333+00:00
This is indeed a curious case, but I believe it confirms what I mentioned in my previous reply. Beginning with Windows 11 version 24H2, DISM installs packages, particularly cumulative updates, directly into the image and may require prerequisite “checkpoint” updates. This change in the update mechanism is likely why the update cannot be uninstalled in this version.

Run this in Command Prompt:

dism /online /get-packages /format:table

Then identify the name for KB5065426 and run:

dism /online /get-packageinfo /packagename:<packagename>

Look for the line:

Uninstallable : False

If it shows False, that would confirm why the Control Panel uninstall fails, the update isn’t flagged as removable once installed via DISM.
Haritha Duraisamy 0 Reputation points

2025-09-12T06:31:31.86+00:00

Hi Emmanuel Santana,

Thank you for the guidance. I ran the DISM command you referenced:

dism /online /get-packageinfo /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.6584.1.20

The output completed successfully, but I did not find the keyword "Uninstallable" mentioned anywhere in the results.

Could you please clarify if there’s another way to determine the uninstall status, or if this result confirms that the update cannot be removed?
Emmanuel Santana 40,110 Reputation points Independent Advisor

2025-09-13T18:04:18.9533333+00:00
Thanks for running the command and sharing the results. That gives us a clearer picture.

From what I’ve gathered, the absence of the Uninstallable field in the DISM output typically means the update isn’t registered with rollback capability. This often happens with cumulative updates on Windows 11 24H2, especially when installed via DISM or when the update includes a Servicing Stack Update (SSU).

Just to confirm, was the update you applied (KB5065426) a combined LCU and SSU package? That could explain why rollback is blocked, as SSUs are designed to be non-removable once installed.

Here’s something else you can try:

1. Run the following in an elevated Command Prompt:

dism /online /cleanup-image /analyzecomponentstore

This will show whether the update is marked as permanent, superseded, or reclaimable. It helps confirm if rollback is still theoretically possible.

Use:
dism /online /get-packages /format:table
and then:
dism /online /get-packageinfo /packagename:<your-package-name>
again, to see if anything changed after reboot or cleanup.

These steps will help confirm whether the update is considered fully committed and non-removable. If rollback is essential in your environment, we may need to look at alternate deployment strategies like using wusa.exe or testing on an offline image.
Haritha Duraisamy 0 Reputation points

2025-09-15T12:58:50.24+00:00

Hi Emmanuel Santana,

I have attached the requested screenshots.

From my understanding, when using the DISM method, the update history trace will not generated and the uninstall function does not work the same way as with wusa.exe.

As mentioned earlier, I used DISM specifically to avoid the 0x8024001C (2146498504) error, and the deployment was successful with this approach.

Could you please confirm my understanding if this is the expected behaviour of DISM?
Emmanuel Santana 40,110 Reputation points Independent Advisor

2025-09-15T17:33:07.1366667+00:00
Hi Haritha. Thanks for confirming all the details and sharing those screenshots.

You're absolutely right in your understanding. Based on current documentation and reports as of September 2025, when cumulative updates are installed using the DISM method on a live Windows 11 24H2 system, it’s expected that:

The update may not appear in the Windows Update history

The uninstall option might be shown but won’t work, especially if the update includes a Servicing Stack Update (SSU)

The Uninstallable field may be missing in DISM /get-packageinfo, which typically means rollback isn’t supported

Registry entries under Component Based Servicing may only retain the most recent packages, especially if checkpoint updates are involved

This happens because DISM bypasses the Windows Update agent, which normally handles rollback metadata and update logging.

Just to confirm, do you know if the package you deployed was a combined LCU and SSU? Microsoft notes that uninstall will not work in those cases, and that might explain everything you're seeing.

Like I recommended before, if rollback is something you’ll need to retain in future deployments, using wusa.exe or letting the update go through Windows Update would offer better uninstall support.

Answer 2

Hi Haritha. You're right, when using DISM to install cumulative updates, some things behave differently compared to a normal Windows Update installation.

DISM applies the update directly to the system image, so the update may not appear in the Windows Update history, can't be uninstalled via Control Panel, and might affect how previous updates are listed in the registry.

Just to understand your setup better, was this DISM deployment done on a running system, or did you service an offline image (like a mounted WIM)? And did you run any cleanup commands after applying the update?

You can try the following quick checks:

Open PowerShell and run:

   Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

This confirms whether the system registered the update.

In Command Prompt (Admin), run:
```
   dism /online /get-packages /format:table
```
This gives you a direct list of installed packages and their states.

These will help confirm that the update was applied correctly even if it doesn't appear in the usual places. Let me know what results you get, especially from the DISM package list, so I can guide you further.